fr500 Wrote:I've got a feature idea. Could you add launcher id tag to the launcher itself and a way to accept arguments? If you do so skis with support for custom shortcuts on the home menu could have a way to launch common used launchers from the home menu.

Example, in shade now you can create a home screen shorcut to the script (plugin.program.advanced.launcher) if there was the id. and an option to parse arguments you could create a shortcut to the script plugin.program.advanced.launcher("1") for example and that would launch the app with id=1. If no arguments are passed then the normal app view would show.

What do you think?

• Go into Advanced Launcher
  
• Select a launcher
  
• Go into launcher context menu and select "Add to Favorite" option
  
• Go into you skin sub menu option and select this Favorite as submenu.
  

Angelscry Wrote:Rectification : It is also working with roms. You just have to avoid to use special characters (like bracket) into launcher name or rom name to make it works.



Here is how it appear into the guisettings.xml file :

Code:

<setting type="string" name="skin.alaska.revisited.programbuttonname_3">The Legend of Zelda: Ocarina of Time</setting>
<setting type="string" name="skin.alaska.revisited.programbuttonimage_3">/media/emulation/nintendo64/roms/The Legend of Zelda - Ocarina of Time_thumb.jpg</setting>
<setting type="string" name="skin.alaska.revisited.programbuttonpath_3">RunPlugin(plugin://plugin.program.advanced.launcher/?Nintendo 64/The Legend of Zelda: Ocarina of Time,return)</setting>

So if your skin is able to start plugin from submenu using this command line :

Code:

RunPlugin(plugin://plugin.program.advanced.launcher/?[b]#launcher_name#[/b]/[b]#rom_name#[/b],return)

It may works...

srsobieraj Wrote:Hi Angelscry & ALA community,

Request/Suggestion/Thought:

"Run Before" & "Run After" inputs for Launchers & Roms.

I'd like to be able to run Xpadder with different configurations depending on the Emulator I'm using. I think the best way to do this would be to include a Run Before option for Launchers. I can simply type the command-line argument that I want to run before and after ALA launches the Emulator. I'd like to do something like this:

Code:

C:\Xpadder\xpadder.exe controller1.profile controller2.profile

<ALA executes emulator>

Taskkill /IM xpadder.exe /F

So I can pass arguments to the command line both before and after ALA runs the emulator.

The problem is that I would need to specify "Run Before" and "Run After" for each Rom, but still have a "default" value. I run a variety of Windows games on my computer and many require a different Xpadder layout.

This solution isn't perfect, but it would solve my problem. Has anyone encountered this problem and solved it? Can anyone help with a better solution? It's driving me nuts!

Would EventGhost be able to solve this problem? ie, use EventGhost to detect a certain application launch, then run Xpadder when it opens and kill it when it closes?

srsobieraj Wrote:Hi Angelscry & ALA community,

Request/Suggestion/Thought:

"Run Before" & "Run After" inputs for Launchers & Roms.

I'd like to be able to run Xpadder with different configurations depending on the Emulator I'm using. I think the best way to do this would be to include a Run Before option for Launchers. I can simply type the command-line argument that I want to run before and after ALA launches the Emulator. I'd like to do something like this:

Code:

C:\Xpadder\xpadder.exe controller1.profile controller2.profile

<ALA executes emulator>

Taskkill /IM xpadder.exe /F

So I can pass arguments to the command line both before and after ALA runs the emulator.

The problem is that I would need to specify "Run Before" and "Run After" for each Rom, but still have a "default" value. I run a variety of Windows games on my computer and many require a different Xpadder layout.

This solution isn't perfect, but it would solve my problem. Has anyone encountered this problem and solved it? Can anyone help with a better solution? It's driving me nuts!

Would EventGhost be able to solve this problem? ie, use EventGhost to detect a certain application launch, then run Xpadder when it opens and kill it when it closes?

Steveb Wrote:What type of game pad do you have?
With a logitech game pad I just use the logitech profile software..
Create a profile for each emu and select "Apply profiles to games automatically" in global profiler settings.

Quote:That's all. The script if simple (6 lines) and will do exactly what you want. Do you can next improve it. For example you can analyses the $CmdLine[0] command line argument and extract the rom filename from it and start xpadder.exe using related controller profile.

srsobieraj Wrote:I am using the Xbox 360 Wireless controller. It doesn't have a profiler app unfortunately.

I wasn't aware that AutoIt supported If or Switch statements. I will check it out more thoroughly, thank you for your suggestion. Once I have my controller(s) working, I will have a complete Home Theatre experience, and it's all thanks to this add-on!

srsobieraj Wrote:Hi Angelscry & ALA community,

Request/Suggestion/Thought:

"Run Before" & "Run After" inputs for Launchers & Roms.

I'd like to be able to run Xpadder with different configurations depending on the Emulator I'm using. I think the best way to do this would be to include a Run Before option for Launchers. I can simply type the command-line argument that I want to run before and after ALA launches the Emulator. I'd like to do something like this:

Code:

C:\Xpadder\xpadder.exe controller1.profile controller2.profile

<ALA executes emulator>

Taskkill /IM xpadder.exe /F

So I can pass arguments to the command line both before and after ALA runs the emulator.

The problem is that I would need to specify "Run Before" and "Run After" for each Rom, but still have a "default" value. I run a variety of Windows games on my computer and many require a different Xpadder layout.

This solution isn't perfect, but it would solve my problem. Has anyone encountered this problem and solved it? Can anyone help with a better solution? It's driving me nuts!

Would EventGhost be able to solve this problem? ie, use EventGhost to detect a certain application launch, then run Xpadder when it opens and kill it when it closes?

Quote:@echo off

REM launch third party tool
c:\path\to\tool\yourtool.exe


REM launch your app
cd c:\path\to\your\app

app.exe %1

REM wait a couple of seconds in case main process spawns another process
timeout 2

REM oset the following variable to the process that should be tracked
REM usually the same name as the program executable
REM you can find this looking at the Windows Task Manager

set process_1="app.exe"
set ignore_result=INFO:

REM check if the process is still running each interval. If not return to XBMC
REM interval is 3 seconds here
:1

set var=notrunning

for /f "usebackq" %%A in (`tasklist /nh /fi "imagename eq %process_1%"`) do if not %%A==%ignore_result% set var=running

timeout 3
if %var% == running goto :1

REM wait for another interval and then kill 3rd party tool

timeout 3
if %var% == notrunning taskkill /F /IM yourtool.exe


exit

• If you let these 2 paths empty, each time you will create a new stand alone launcher, you will be asked to indicate a thumbs and a fanarts folder.
  
• If you setup these 2 paths, each time you will create a new stand alone launcher, corresponding thumbs and a fanarts folders will be automatically assigned by this 2 paths.
  
• For file launchers, thumbs and fanarts folders will be always, by default, the same than the roms thumbs and fanarts folders.

• update french translation
  
• add title formating for title starting by "The", "A" and "An"
  
• add thumbs and fanarts default paths settings for launchers
  

Angelscry Wrote:Version 0.9.12 : This new option bring 2 new setting parameters : default paths folders for launchers thumbs and fanarts.

• If you let these 2 paths empty, each time you will create a new stand alone launcher, you will be asked to indicate a thumbs and a fanarts folder.
  
• If you setup these 2 paths, each time you will create a new stand alone launcher, corresponding thumbs and a fanarts folders will be automatically assigned by this 2 paths.
  
• For file launchers, thumbs and fanarts folders will be always, by default, the same than the roms thumbs and fanarts folders.

Changelog

• update french translation
  
• add title formating for title starting by "The", "A" and "An"
  
• add thumbs and fanarts default paths settings for launchers