Hello. Is there a way to program a button to behave similarly to a keyboard modifier (meta) key; that is, to remap to a different profile while the button is held down, and restore the original profile on release? Basically, I'm looking to create modes/submodes.
I'm not using OSCulator for music production, I'm using it to support a more natural style of reading, note-taking and composition, using DevonThink, PDFpen and Dragon Dictate. My previous experience with customizing input devices comes from HazardScript in flight simulators etc. [ http://web.archive.org/web/200612020.../HazardScript/ ] See also [ http://web.archive.org/web/200510180...xdpprofile.asp ]. As you'll see, I'm used to thinking in terms of key-frobs and button states.
My current aim to get my Wiimote working like a handheld dictation controller, controlling the functionality of Dragon Dictate (so that I don't have to use its awkward voice commands or resort to the keyboard and mouse) as well as supporting the scrolling/highlighting/annotating I do with a Wacom pad. My problem is that I've run out of buttons on the wiimote. The obvious solution is to use the B button (trigger) as a "shift" key.
Is this possible? I'm used to working with events like this (from the XDProfile site):
The difference between the above and OSCulator (from what I can see) is that in this old scripting language, button press and release were two different hardware events. (The language called them 'frobbables.') So in Mode_1-a, ButtonB(press) would load Mode_1-b. And then in Mode_1-b, ButtonB(release) would load Mode_1-a. I see that OSCulator supports profile switching by event, but I don't see how to create one that would change profiles on B-button-press, and then revert on B-button-release.
I'm not using OSCulator for music production, I'm using it to support a more natural style of reading, note-taking and composition, using DevonThink, PDFpen and Dragon Dictate. My previous experience with customizing input devices comes from HazardScript in flight simulators etc. [ http://web.archive.org/web/200612020.../HazardScript/ ] See also [ http://web.archive.org/web/200510180...xdpprofile.asp ]. As you'll see, I'm used to thinking in terms of key-frobs and button states.
My current aim to get my Wiimote working like a handheld dictation controller, controlling the functionality of Dragon Dictate (so that I don't have to use its awkward voice commands or resort to the keyboard and mouse) as well as supporting the scrolling/highlighting/annotating I do with a Wacom pad. My problem is that I've run out of buttons on the wiimote. The obvious solution is to use the B button (trigger) as a "shift" key.
Is this possible? I'm used to working with events like this (from the XDProfile site):
The PROGRAM_MODES section lists each mode and the frobbables or axis that have script or chain assignments. Each mode you identify is marked by a "[modename]" tag, where modename is any original alphanumeric name that does not include any of [](){}<>#=^, including (space). There is a special mode identifier with the name DEFAULT. The DEFAULT mode is the mode that is loaded into the X-36/45 when the profile is loaded. All other modes must be loaded using a script containing the appropriate LOADMODE_ event as described in the SCRIPTLIST section above. Note that each mode of your profile should have at least one script with a LOADMODE_ event to allow you to transfer to another mode.After identifying a mode, you identify frobbable and axis assignments using the syntax "frobbable = scriptname" or "axis = chainname", where frobbable is any one of the pre-defined frobbables listed in table 3 below, scriptname is any one of the script names identified in the SCRIPTLIST section, axis is any one of the pre-defined axis names listed in table 4 below, and chainname is any one of the chain names identified in the AXIS_CHAINS section.
The difference between the above and OSCulator (from what I can see) is that in this old scripting language, button press and release were two different hardware events. (The language called them 'frobbables.') So in Mode_1-a, ButtonB(press) would load Mode_1-b. And then in Mode_1-b, ButtonB(release) would load Mode_1-a. I see that OSCulator supports profile switching by event, but I don't see how to create one that would change profiles on B-button-press, and then revert on B-button-release.
Comment