Space Navigator PE Driver Development Thread

[scotty562]

This doesn't really fit directly into the discussion but would it be possible to incorporate a feature into the tray icon?

I've noticed at night when I'm driving the leds drive me nuts. If the option to turn the leds on or off would be added that would save me and most likely some others the hassle of tearing them out of the unit itself. This isn't Earth shattering or anything but if it's an easy addition I'd really appreciate it.

[cherrybomb]

This doesn't really fit directly into the discussion but would it be possible to incorporate a feature into the tray icon?

I've noticed at night when I'm driving the leds drive me nuts. If the option to turn the leds on or off would be added that would save me and most likely some others the hassle of tearing them out of the unit itself. This isn't Earth shattering or anything but if it's an easy addition I'd really appreciate it.

The latest version available at sourceforge actually doesn't light up the LED's. It's a pretty easy thing to provide control over it. I've actually removed control over it due to the changes I'm making to the app to make it more "generic" for other HID's. :-)

[inh]

Im gonna go try that XML code now, thanks =]

As for the LEDs, add an option for them in the config file, so that way theyre only controlled if the user wants them to be

[inh]

Well, right off the bat the code didnt work, but after trying different things for awhile i got it. Apparently the app doesnt like "<axe threshold="10" sendCenter="false"/>" instead i had to set each axe to binary, and just leave the actions blank. Once i figured that out the volume section worked great =] Below is most of my config file. Hopefully it will help give others a better understanding of how to get it to do what they want.

<deviceContexts>
    <deviceContext name="SpaceNavigator" device="SpaceNavigator">
      <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 0 pan left/right -->
      <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 1 pan foreward/back -->
      <axe threshold="500" type="binary" posAction="RR Play/Pause" negAction=""/> <!-- axe 2 push/pull -->
      <axe threshold="200" type="binary" posAction="" negAction=""/> <!-- axe 3 tilt foreward/back -->      
      <axe threshold="400" type="binary" posAction="RR Prev" negAction="RR Next"/> <!-- axe 4 tilt left/right -->
	  <axe threshold="100" 
        type="linear"
        startPulse="1"
        endPulse="12"
        posAction="RR Volume Up"
        negAction="RR Volume Down" /> <!-- axe 5 Twist -->
	  <buttons>
        <button downAction="RR Volume Down"
          upAction="" />
        <button downAction="RR Volume Up"
          upAction="" />
      </buttons>
    </deviceContext>
  </deviceContexts>

  <contexts>
    <context name="Default"
      deviceContext="SpaceNavigator" />
  </contexts>

  <actions>
    <sendWindowMessage name="Context Up"
      type="CopyData"
      window="SpaceNavigatorDriver"
      message="CONTEXT;Up"/>
    <sendWindowMessage name="Context Down"
      type="CopyData"
      window="SpaceNavigatorDriver"
      message="CONTEXT;Down"/>
    <sendWindowMessage name="RR Volume Up"
      type="CopyData"
      window="RoadRunner"
      message="VOL+"/>
    <sendWindowMessage name="RR Volume Down"
      type="CopyData"
      window="RoadRunner"
      message="VOL-"/>
	  <sendWindowMessage name="RR Play/Pause"
      type="CopyData"
      window="RoadRunner"
      message="PLAY"/>
	  <sendWindowMessage name="RR Next"
      type="CopyData"
      window="RoadRunner"
      message="NEXT"/>
	  <sendWindowMessage name="RR Prev"
      type="CopyData"
      window="RoadRunner"
      message="PREV"/>
    <keyPress name="Copy">
      <key>17</key>
      <key>67</key>
    </keyPress>
    <keyPress name="Paste">
      <key>17</key>
      <key>86</key>
    </keyPress>
  </actions>

Also, I think I remember awhile back people wanted the spacenav to be able to do different things depending on the screen. I think something like kthis would work well:

<context name = "Audio.skin"
device context="Audio"/>
Where Audio.skin is the name of the skin file currently being displayed, and Audio is the set of commands for the device to perform, kinda like how I have SpaceNavigator as my default. Yea, the driver would have to query roadrunner each time the spacenav was moved, but i dont think it would be sluggish at all.

I'm not sure if theres a way to query roadrunner for the currently displayed skin, but i think there might. If not, it cant be that hard to implement. Hope this makes sense =]

Also, this would make it possible to control the LEDs, so that during the day, they can be on, and at night they can be off. Pretty sure theres a way to query roadrunner for whether or not it is using a day or night skin setting.

I know this all seems centered around roadrunner, because, well, its what I use, but if anyother frontends can communicate via windowmessages, then this system can work with them too =]

[cherrybomb]

Well, right off the bat the code didnt work, but after trying different things for awhile i got it. Apparently the app doesnt like "<axe threshold="10" sendCenter="false"/>" instead i had to set each axe to binary, and just leave the actions blank.

Arrgg.. Sorry about that. This is EXACTLY the reason that I need to build a config app, the configuration file is getting to complex for even me to remember. :-/ Glad you got it figured out though!

Also, I think I remember awhile back people wanted the spacenav to be able to do different things depending on the screen. I think something like kthis would work well:

<context name = "Audio.skin"
device context="Audio"/>
Where Audio.skin is the name of the skin file currently being displayed, and Audio is the set of commands for the device to perform, kinda like how I have SpaceNavigator as my default. Yea, the driver would have to query roadrunner each time the spacenav was moved, but i dont think it would be sluggish at all.

The software is currently capable of doing different things in different contexts. Also, it's able to switch to a named context based on a window message.

The software will never be designed to be tied directly to RR, though a lot of it's functionality revolves around that. I'm trying to make it as "generic" as possible.

If you want this functionality, you can add a command to each skin that you want a custom control set for, which sends a window message to the software, to switch skins. I'll try to document this better somewhere!

[inh]

Awesome, glad its already supported (for the most part.) I dont blame you for trying to make it generic, and comend you on your efforts. I took the easy way out with RRCam

I saw the contexts, but didnt know there were multiple ways to switch em. Please do document this for me =]

also, is it possible to use the device as a mouse without having to hold a button down? i would love to make it its own context, so i could click a button on the spacenav, have it switch to mouse mode, then click it again to have it go back to normal spacenav mode =]

[cherrybomb]

also, is it possible to use the device as a mouse without having to hold a button down? i would love to make it its own context, so i could click a button on the spacenav, have it switch to mouse mode, then click it again to have it go back to normal spacenav mode =]

The current configuration on an axis to "emulate mouse" doesn't require that you hold down a button. Unless I'm somehow confused, or broke that functionality.

When I'm back at a computer with the SN, I'll try configuring it to operate as a mouse. It should just be a matter of defining a separate context/device context where it is configured to operate as a mouse. :-)

Would probably be best to use some "external" source to switch back and forth, or an unused axis, rather than the button(s).

[inh]

I think it said somewhere in the config that you had to hold a button down so that mouse movements didnt get confused as gestures, though its entirely possible i miss-interpreted that.

So far i'm impressed with your work. I've managed to do everything i originally wanted to with it =] As soon as we get the app communicating with other programs worked out completely, i think this will turn in to one very popular program =]

[cherrybomb]

I think it said somewhere in the config that you had to hold a button down so that mouse movements didnt get confused as gestures, though its entirely possible i miss-interpreted that.

So far i'm impressed with your work. I've managed to do everything i originally wanted to with it =] As soon as we get the app communicating with other programs worked out completely, i think this will turn in to one very popular program =]

Ahh yes, quite true.. That refers to using the mouse as an input device. If you do, you must hold down a mouse button to perform a gesture.

Kinda whacky, I know, but if you don't define a mouse device context you can make the SN emulate a mouse, without having to press a button.

Sorry for the confusion. :-)

[inh]

Ah ok, that makes sense =] I think im going to add a Mouse context, and use the SN as a mouse sometimes too, just for fun.