Hello all,
I'm BRAND NEW to my recent 3DConnexion Spacemouse purchase. Been learning the ropes of creating some custom XML files for unsupported apps. I have the basics down (I think) but I'm having a disconnect on what the HIDMultiAxis_Rx and HIDMultiAxis_Ry ActionIDs on the spacemouse actually are. I see the references in the KeyboardWADSTemplate.xml file I've been basing things on but the only thing I can intuit is that the HIDMultiAxis_Rz ActionID is rotating the knob right and left.
Can someone clue me in as to what the x and y variants of this ActionID are?
Thanks!
-David
Newbie custom XML help
Moderator: Moderators
Re: Newbie custom XML help
We use the HID conventions.
Rotations are about the translation axes.
In HID convention, X&Y are like a 2D mouse (along the top of the desk). Z is the additional direction (up/down perpendicular to the table).
Rx is rotatation like a motorcycle throttle (pitch).
Ry is rotatation like opening a door (roll).
Rz is rotatation like opening a jar of peanut butter (yaw).
Rotations are about the translation axes.
In HID convention, X&Y are like a 2D mouse (along the top of the desk). Z is the additional direction (up/down perpendicular to the table).
Rx is rotatation like a motorcycle throttle (pitch).
Ry is rotatation like opening a door (roll).
Rz is rotatation like opening a jar of peanut butter (yaw).
Re: Newbie custom XML help
Thanks for the explanation. That helps me get my head around all of the axes the SpaceMouse offers.
Another question:
When I define a radial menu macro, in the app config xml I see a reference to the ActionID but not the keystroke content. Where is this action stored? Does it have it's own file somewhere else in the folder structure?
Thanks!
-David
Another question:
When I define a radial menu macro, in the app config xml I see a reference to the ActionID but not the keystroke content. Where is this action stored? Does it have it's own file somewhere else in the folder structure?
Thanks!
-David
Re: Newbie custom XML help
If you are assigning a predefined macro, it is probably defined in the localization files. Macros may be language-(kb layout)-specific.
The default file is en-us.xml.
If you make a new macro in the GUI, it will be stored in your app-specific file in AppData.
The default file is en-us.xml.
If you make a new macro in the GUI, it will be stored in your app-specific file in AppData.