[kricker]

Is there a way to jump directly to a plugin from the main menu?
I've tried setting it up similar to how you run a python script from the main menu, but nothing would happen.

Code:

<onclick>XBMC.RunScript(Q:\plugins\programs\Launcher\default.py)</onclick>

[jmarshall]

plugin != script.

To run a plugin, using ActivateWindow(Programs,plugin://programs/Launcher) may do the trick.

[kricker]

I assume that first bit means a plugin does not equal a script. They all have a default.py, so that's the best assumption I could come up with for launching them.

I'll try your example thanks.

[kricker]

Code:

XBMC.ActivateWindow(Programs,plugin://programs/Launcher)

Crashed the win32 build. I'll test the xbox build later.

[jmarshall]

Well, nothing should cause a crash, ever. Please post a bug report on trac including the changed skin files, the plugin you used (a link to it is fine). Feel free to assign it to me.

Thanks,
Jonathan

[kricker]

Well, nothing should cause a crash, ever. Please post a bug report on trac including the changed skin files, the plugin you used (a link to it is fine). Feel free to assign it to me.

Thanks,
Jonathan

Okay will do. I'm looking into how to run the win32 version in debug mode. When I figure that out I'll post it.

[jmarshall]

Settings->System->Enable debug logging.

Ideally a reboot after that so I can see version info etc. in the log.

Cheers,
Jonathan

[kricker]

Settings->System->Enable debug logging.

Ideally a reboot after that so I can see version info etc. in the log.

Cheers,
Jonathan

Crap, okay. I set the logging to 3 in avanced settings hoping that was it. I posted the bug already. I'll do that now and edit the bug report.

[kricker]

Hmmm...I see no such option in Settings->System

[jmarshall]

Please use PM3 so that we can eliminate the skin variable from the equation.

Settings->System has "Enable debug logging" as the very first option.

[jmarshall]

Don't bother - found the reason.

The crash should be fixed at least. Not sure whether it'll run or not.

Cheers,
Jonathan

[kricker]

Thanks. I was going to try it with PM3 today. It was just too late last night to do anymore.

I did switch to PM3 to set the debug setting, but I still did not see it. I see it on my other PC with XBMC. I even copied over the PM3 skin from the one I do see it on, thinking my PM3 skin was corrupt.

Just curious, what was the fix?

[kricker]

I did a clean install, now I see the option.

[kricker]

I had to remove

Code:

<loglevel>1</loglevel>

from my advancedsettings.xml file for debug logging to show up in the GUI.

[jmarshall]

Ah - yeah, it will be removed if advancedsettings.xml has it (just like any other gui setting).

Note that while the crash is fixed, I have no idea whether the plugin URL I gave you suffices or not. It must be close, however, otherwise it wouldn't have crashed :p

Cheers,
Jonathan