[lokipoki]

I have the .lnk and test.exe in the same folder though...

[dishwater63]

Not sure if I should post this here or on the Advanced Launcher forums, but hopefully somebody can point me in the right direction. Basically I can't get the Launcher to scrape any info for my ROMs. I can do it, one by one, but how do I get it to automatically scrape all the info? I played around with the settings for over an hour and aside from clicking on each individual ROM, I can't figure it out.

Thanks in advance to anybody who helps.

[Angelscry]

Not sure if I should post this here or on the Advanced Launcher forums, but hopefully somebody can point me in the right direction. Basically I can't get the Launcher to scrape any info for my ROMs. I can do it, one by one, but how do I get it to automatically scrape all the info? I played around with the settings for over an hour and aside from clicking on each individual ROM, I can't figure it out.

Thanks in advance to anybody who helps.

You need first to setup all the scraper (data, thumbs and fanarts) on automatic or semi-automatic mode. Then you need to delete from the launcher list items you want to re-scrap (or delete all the list if you want to rescrap all). Then make a new "Scan for New Item".

[Angelscry]

The code of my test.exe is just a test as the name implies:


When .lnk are activated the test.exe wont work. But when I deactivate the .lnk that it works. What do I need to do to get both working? Eventually the test.exe will include a loading screen so that when a game loads I wont see windows... I hope you understand what I mean/

Cheers.

When Advanced Launcher .lnk support is activated, .lnk files are started by explorer.exe. So in your case, lnk file are effectively started (by explorer.exe) but test.exe is not started. When Advanced Launcher .lnk support is desactivated, .lnk files are started by the application defined into the launcher. So in your case, test.exe is started, but not the .lnk files (because your test.exe executable have nothing inside its code to manage and start .lnk files).

Remember that .lnk files ARE NOT executables. .lnk files are shortcuts managed by explorer.exe to redirect to another executable fand start it.

To make you test.exe file working it must manage .lnk files paths as argument and be able to start these lnk. files. According to this page, the way to start .lnk files using autoit is :

Code:

Run(@ComSpec & " /c " & '"C:\Documents and Settings\All Users\Menu Démarrer\Programmes\Microsoft AntiSpyware\Uninstall Microsoft AntiSpyware.lnk"', "", @SW_HIDE)

So to work with Advanced Launcher, your script must be something like this :

Code:

Run(@ComSpec & " /c " & '"' & $CmdLine[1] & '"', "", @SW_HIDE)

And your launcher configuration must be like this :

Application : D:\HTPC\Games\PC\Test.exe
Arguments : "%rom%"
File Extension : lnk
.lnk support : OFF

Ok. I tried exactly that. But when select a game nothing happens

I have taken time to test it on my Windows system this morning and all the last information I have send you are working perfectly on my system. Are you sure you have compiled your autoit script correctly?

[OpFor Zulu 2]

I haven't noticed any mention of Future Pinball, I did not read all 500+ pages nor did I see any listing under Pinball in the Wiki, so, I thought I would just mention it. It works great under ALA, just remove the quotations around %rom% in the arguments line for it to load the .lnk files correctly.

Example for calling a specific table from the shortcut's target line:
"C:\Emulators\Future Pinball\Future Pinball.exe" /open "c:\emulators\Future Pinball\Tables\DEAD_HUNTERS.fpt" /play /exit

Enjoy

[Angelscry]

I haven't noticed any mention of Future Pinball, I did not read all 500+ pages nor did I see any listing under Pinball in the Wiki, so, I thought I would just mention it. It works great under ALA, just remove the quotations around %rom% in the arguments line for it to load the .lnk files correctly.

Example for calling a specific table from the shortcut's target line:
"C:\Emulators\Future Pinball\Future Pinball.exe" /open "c:\emulators\Future Pinball\Tables\DEAD_HUNTERS.fpt" /play /exit

Enjoy

Thank for the information.

If the command line is effectively "C:\Emulators\Future Pinball\Future Pinball.exe" /open "c:\emulators\Future Pinball\Tables\DEAD_HUNTERS.fpt" /play /exit, so it will be also possible to do it directly without using any lnk files by creating a files launcher :

Application : C:\Emulators\Future Pinball\Future Pinball.exe
Arguments : /open "%rom%" /play /exit
Items path : c:\emulators\Future Pinball\Tables\
Files extension : fpt

[n1md4]

Angelscry, I have tried so many ways, short of reinstalling, to get openbox permanently booted in the background to handle window management but to no avail.

Would it be possible to show me where in your code I could edit so that openbox was launched in the background automatically before and then closed after an application were launched?

[Angelscry]

Angelscry, I have tried so many ways, short of reinstalling, to get openbox permanently booted in the background to handle window management but to no avail.

If you want openbox permanently booted, this must be done at the operating system level (for example into the .xinitrc file) not at the Advanced Launcher level.

Would it be possible to show me where in your code I could edit so that openbox was launched in the background automatically before and then closed after an application were launched?

The code need to be modified at 2 differents place (one for standalone launcher and one for files launcher). Just found into the code (launcher_plugin.py) the lines checking the linux operating system :

Code:

...
elif (sys.platform.startswith('linux')):
...

Few lines below you may found these lines :

Code:

...
os.system("\"%s\" %s " % (launcher["application"], arguments))
...

and

Code:

...
os.system("\"%s\" %s " % (application, arguments))
...

Add your code to launch/close openbox before and after these 2 lines.

But in my opinion it will be far better to use a .sh to do that :

Code:

#!/bin/bash

openbox &
/usr/bin/your_app
killall -9 openbox

[dishwater63]

Thanks Angelscry, but now I got another issue. I let Advanced Launcher add and scrape one of my ROM collections and it seems that a lot of them are wrong. For instance, I have five entries for Mega Man 4, but of course I only have one zipped file of Mega Man 4. The other four entries are pointing to other games, such as "4 Nin Uchi Mahjong" and "Pachio-kun 4". Now, I know the number 4 is playing a role in the incorrect labeling, but how do I go about fixing the issue?

If it matters, I use the No-intro ROM sets. It is a standardized ROM naming convention.

[oilbag]

@. Angelscry,
I love both your World Channels and XBMC Tele Fr. Plugins. In the World Channels Plugin,countries category Israel,I24 News,Could you please give an option for I24 News in English also. I was also wondering if you could add GOOD LIFE TV ISRAEL and ISRAEL FOOD CHANNEL. Thank you very much.

[Angelscry]

Thanks Angelscry, but now I got another issue. I let Advanced Launcher add and scrape one of my ROM collections and it seems that a lot of them are wrong. For instance, I have five entries for Mega Man 4, but of course I only have one zipped file of Mega Man 4. The other four entries are pointing to other games, such as "4 Nin Uchi Mahjong" and "Pachio-kun 4". Now, I know the number 4 is playing a role in the incorrect labeling, but how do I go about fixing the issue?

If it matters, I use the No-intro ROM sets. It is a standardized ROM naming convention.

Scraping is based on roms filename, selected system platform and the selected online ressources. So bad scraping could be linked to several things :

• your file name (as so the query string) is not enough explicit for the search.
  
• you have selected the wrong platform system
  
• the scraper database do no have the game into it's database
  

In all these cases, you always have the possibility to change the query string, the system platform and the scrapers sources, and them manually rescrap them or delete them form the list and perform a new "scan for new item".

[n1md4]

Angelscry, I have tried so many ways, short of reinstalling, to get openbox permanently booted in the background to handle window management but to no avail.

If you want openbox permanently booted, this must be done at the operating system level (for example into the .xinitrc file) not at the Advanced Launcher level.

I tried this, but I get problems with OB and XBMC fighting for Xorg .. is what it feels like. I tried many variations to this as well, none of them worked.

But in my opinion it will be far better to use a .sh to do that :

Code:

#!/bin/bash

openbox &
/usr/bin/your_app
killall -9 openbox

I had considered this, but if I'm going to run an OB session every time I launch an external app, it may as well be hard-coded. Also, how are arguments passed using this method?

---

The code need to be modified at 2 differents place (one for standalone launcher and one for files launcher). Just found into the code (launcher_plugin.py) the lines checking the linux operating system :

Code:

...
elif (sys.platform.startswith('linux')):
...

Few lines below you may found these lines :

Code:

...
os.system("\"%s\" %s " % (launcher["application"], arguments))
...

and

Code:

...
os.system("\"%s\" %s " % (application, arguments))
...

Add your code to launch/close openbox before and after these 2 lines.

I've found where to edit, but I don't know enough of Python to edit it. Can you give me an example of opening and closing OB either side of one of these lines?

[styx06]

I had considered this, but if I'm going to run an OB session every time I launch an external app, it may as well be hard-coded. Also, how are arguments passed using this method?

See this guide for your anwer: http://dragly.org/2012/04/11/launching-a...untu-eden/

[Angelscry]

I tried this, but I get problems with OB and XBMC fighting for Xorg .. is what it feels like. I tried many variations to this as well, none of them worked.

The booting order is X > Openbox > XBMC. So Openbox had to be started from X (edit .xinitrc file to add openbox-session) and XBMC had to be started from Openbox (edit autostart file into openbox configuration to add xbmc). Do not start Openbox and XBMC both from .xinitrc.

I had considered this, but if I'm going to run an OB session every time I launch an external app, it may as well be hard-coded. Also, how are arguments passed using this method?

That's why starting Openbox during the boot sequence is a better choice. Arguments are passed as %1 for the first argument send by Advanced Launcher, %2 for the second argument, %3 for the third argument, etc... See previous styx06 post for more information.

I've found where to edit, but I don't know enough of Python to edit it. Can you give me an example of opening and closing OB either side of one of these lines?

No. This solution is the worth one, and I would not encourage/support you to use Advanced Launcher like that.

[n1md4]

Okay, I trust your judgement on this one, it's your add-on after all and will have another go using your suggestions.

Thanks very much for the help!