|Under constuction NOT FINISHED!!!!!!!!!!!
These first four are really not that important, they do nothing but provide feedback
but xlobby plugin setup dialog.
public string GetName()
public string GetDescription()
public string GetPluginType()
public string GetStatus()
Now the next ones are where everything happens
public void ShowDialog()
"connectedToInternet", this will return "true" or "false"
"ir>", used for an IR plugin, see examples "buttonsize:<button id>", this will allow you to retrive the size of a button from a unique button id in the following format <x>:<y>:<width>:<height>. An example of using this would be "buttonid:mybutton", the results would be 10:20:50:40 Now the rest of the commands are taken straight from the eventmanager commands, that means ANY command you find in the event manager can be triggered from the SendCommand() function. Let me explain a bit how this works. Every command in xlobby has a group, for example "os", "xlobby", "category". Next a group has a list of commands like "execute", "back", "reset". In turn some of these commands have parameters, these parameters are represented in text boxes once you select a command. So what does this have todo with SendCommand(), very simple. Lets say you want to trigger the "category, next item" command, what you have to do is convert that command into a special format. For that command it would be "command:category:next item:". The format is as follows command:<group name>:<command name>
command:<group name>:<command name>:<parameter1>
command:<group name>:<command name>:<parameter1>:<parameter2>
command:<group name>:<command name>:<parameter1>:<parameter2>:<parameter3>
command:<group name>:<command name>:<parameter1>:<parameter2>:<parameter3>:<parameter4> get it? just say you are going to call a command with no parameters, a good example of this is a command with optional parameters. Lets say its a 3 parameter command, and the last 2 are optional, it would look something like this. command:<group name>:<command name>:<parameter1>:: Notice that when you have an parameter command and you leave it blank, you still need the preceding : even though the parameter is blank. This is the reason "command:category:next item:" ends with a ":" because I am not using the optional parameter to specify which category.