Looks like I have to bite the bullet and redo the first page, and try to make it more understandable. I've been meaning to do it anyway to update it with the new functionality in the plugin.Livin wrote:... I'm a bit confused as to the way you intended it to be used. I could be using it wrong. Though I don't think there needs to be a huge how-to.
There is no first section as it depends on how you want to control XBMC, if you want to control with a remote, the "remote" section is best to start with.a) what sections/folders should be populated first
Yes I need to expand on how the direct actions work and not to map the same button to different actions at the same time.b) what sections/folders are populated, as needed and how these affects functionlaity
You seem to have understood how I intended.Something like this (again, this may be incorrect as I may not understand your design fully)...
This looks good.'Remote' is the main folder to use - Put all your general commands here first. Example: navigating menus, starting/stopping playback, etc.
Other folders are used based on their context in XBMC.
This is not so good.If there are buttons/commands you wish to remap based on specific context in order to control differently that the commands in the 'Remote' folder.
Example:
'Remote' folder "Arrow Up" moves the menu selection up one item. You can map "Arrow Up" inside 'Media Playing' folder to mean something different.
I guess the event stuff will need to wait a little longer, as I improve the instructions as I want people to know how to use my XBMC2 plugin.
jonib
