2 Minor Errors
1. If you go to Edit Joystick Command\Advanced\Assign Command (to any tilted option), the "Edit Commands" feature is missing in the contextual menu.
2. If the name of the command ends with > then the sign will be deleted. If you have two of them, the last one will be deleted.
For example, in order to create a command with the name -> then you should write ->>
Actually both of those are done intentionally...
Although all the other "assign command" popups contain a link to Edit Commands, it is not found on Advanced Joystick Command popup because it would have been a significant pain in the butt to add that there, and since the "advanced" window is really just a sub-window of the main Joystick Command window, it was decided that it should be easy enough to setup the commands from the prior screen and then return to Advanced afterward. Actually if you have NO COMMANDS at all and you go there, you will see a message explaining that you should create your commands first and then return there to assign them.
As for the > character... I'm not sure if you are aware of this, but that character is used a special character for "command grouping", so when Pinnacle see's that you've used the > character at the END of a command name... it's as if you had tried to create a group name without any command name itself... thus the grouping character is removed so that the command still has an actual name.
For instance, just about every "official profile" contains commands like these...
Movement > Move Left
Movement > Move Right
Movement > Move Forward
Movement > Move Backward
Movement > Jump
Movement > Crouch
Combat > Fire Weapon
Combat > Reload
Combat > Next Weapon
So when you name your commands like that, whatever appears BEFORE the ">" character is the group name, and whatever is AFTER the ">" is the command name (as would appear on the assignment menus). So in that case the popup menus would have 2 groups (one called "Movement" and one called "Combat") and each of those groups would branch off to display the text after the ">" character. So although technically speaking when you do this, the REAL command name is the whole thing "Combat > Fire Weapon", but the ONLY place you'll see the name altogether like that is on the Edit Commands window... everywhere else within the program the group name portion of the command name is trimmed off. This system can make organizing your commands really easy... and rather than have a button for "create new group" and then assigning commands to the group, this system was created so to create a group is as easy as naming the command with a ">" character. If you remove all references to "Movement > " for instance, then the group is essentially been deleted.
That said your example for a double >> character being allowed is sort of a bug because it should actually remove any > character that ends up at the end, thus I guess I need to put it through a loop to make sure that if there is more than one > that they are all removed. I suggest you rename you command now so it doesn't end in > or else you may lose the assignment after this double >> loop check is added in the next version.
Every day I learn a new thing about Pinnacle.
I was just wondering several days ago how many commands can I see on my screen without having any command hidden beyond one of its edges. The grouping features solves this.
Regarding the bug (>>), may I suggest to keep it as is if it is not causing any problems to the software. Having the > sign in the name of the command is useful sometimes.
Or, you can set Pinnacle to delete the > sign if it separated by a space from the command name or leave it in the command name if there is no space.
Well you actually can use a > character in the name... but the first occurance will cause a group formation, and if it's the only > in the name and it's the last character... then this could cause problems because Pinnacle will be expecting more text to follow the > character at the end.
For example, these are all valid formats for grouping...
My Group Name > My Command Name
My Group Name>My Command Name
My Group Name >My Command Name
My Group Name> My Command Name
See, so the spaces that surround the > character are trimmed anyway, so whether the user surrounds it with spaces or not, it should function the same.
This is also a valid command name with group...
My Group Name > My Command Name With > Character
In this case though your group is named "My Group Name" and your command is named "My Command Name With > Character" ... see so there is no double grouping making the second occurance of > completely valid, unless it is at the end like this...
My Group Name > My Command Name With an Ending >
My Command Name With an Ending >
Both these names are invalid... Pinnacle will not "bark" at you that this is wrong, it will just remove the trailing > character unless you have something behind it. Although technically Pinnacle could probably handle the first example, since there is still a valid group and command name, but the second example will appear to Pinnacle as a group with no command name... thus the > is removed and the group name becomes the command name so Pinnacle won't "hiccup" on anything it isn't expecting like that.
And you thought it all by yourself?