Space Navigator PE Driver Development Thread

[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]

Quote: Originally Posted by inh

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]

Quote: Originally Posted by 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 =]

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.

[inh]

Below is (most of) my config file. When the program start up, it acts as a mouse, using the mouse butons like normal.
When you twist it to the right, it changes contexts and goes to the SpaceNavigator
context, which will send commands to RoadRunner for controlling themedia player.
To get back in to mouse mode, you press the left button.

Code:

  <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="200" type="binary" posAction="RR Prev" negAction="RR Next"/> <!-- axe 4 tilt left/right -->
	  <axe threshold="100" 
        type="exponential"
        startPulse="1"
        endPulse="20"
        posAction="RR Volume Up"
        negAction="RR Volume Down" /> <!-- axe 5 Twist -->
	  <buttons>
        <button downAction="Context Down"
          upAction="" />
        <button downAction="RR FullVisu"
          upAction="" />
      </buttons>
	</deviceContext>
	<deviceContext name="Mouse" 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="" negAction=""/> <!-- axe 2 push/pull -->
	  <axe simulateMouseMove="y"
        threshold="50"
        divisor="30" />
	  <axe simulateMouseMove="x"
        threshold="50"
        divisor="30" />
	  <axe threshold="200" type="binary" posAction="Context Up" negAction=""/> <!-- axe 5 twist -->
	  <buttons>
		<button simulateMouseButton="left" />
		<button simulateMouseButton="right" />
	  </buttons>
	</deviceContext>
  </deviceContexts>

  <contexts>
    <context name="Default"
      deviceContext="Mouse" />
	<context name="SpaceNavigator"
	  deviceContext="SpaceNavigator" />
	<context name="Mouse"
      deviceContext="Mouse" />
  </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 Mute"
      type="CopyData"
      window="RoadRunner"
      message="MUTE"/>
	  <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"/>
	  <sendWindowMessage name="RR FullVisu"
      type="CopyData"
      window="RoadRunner"
      message="Full_Visu"/>
    <keyPress name="Copy">
      <key>17</key>
      <key>67</key>
    </keyPress>
    <keyPress name="Paste">
      <key>17</key>
      <key>86</key>
    </keyPress>
  </actions>

[cherrybomb]

Quote: Originally Posted by inh

Below is (most of) my config file. When the program start up, it acts as a mouse, using the mouse butons like normal.
When you twist it to the right, it changes contexts and goes to the SpaceNavigator
context, which will send commands to RoadRunner for controlling themedia player.
To get back in to mouse mode, you press the left button.

Excellent!

Glad you're getting a handle on how to use the config file. By the time I get a config app finished, you won't need it.

P.S. You can switch to a context by name instead of incrementally. So you could use "CONTEXT;Mouse" to switch to the mouse context, or "CONTEXT;SpaceNavigator" to switch to the SN context.

HINT: This is how you can have RR change the context, by sending the SN app a window message with the context you wish to switch to. Something like maybe "CONTEXT;RRAudio" for the audio skin. The command can be embedded in the skin, so that any time it's activated it sends the window message. ;-)

[ironfinger]

awesome guys!

[inh]

Hah sweeet! Gonna try that tomorrow =D I suspected there was a way to change context exactly like that, i just never got around to trying it. Something about how it was context;down instead ofo just context down, ya know? Ah well, glad its there! =]

Im definatly going to add this in.. I gotta check in RR, but i hope theres a way to send the message when the skin page loads, not just when a button is clicked to load it and then send the message.. There are sooo many ways a skin can be loaded, ya know? Ah well, i'll look in to it and report back =] I'm having fun working with my fusion brain too, so between the two projects, im making loads of progress and having a blast!

Is there any other tricks i should know about? Is there a button command that will activate when both buttons are pressed down? And i just have this nagging feeling i recognize you (or your truck) from explorer forum..

[cherrybomb]

Quote: Originally Posted by inh

Hah sweeet! Gonna try that tomorrow =D I suspected there was a way to change context exactly like that, i just never got around to trying it. Something about how it was context;down instead ofo just context down, ya know? Ah well, glad its there! =]

Im definatly going to add this in.. I gotta check in RR, but i hope theres a way to send the message when the skin page loads, not just when a button is clicked to load it and then send the message.. There are sooo many ways a skin can be loaded, ya know? Ah well, i'll look in to it and report back =] I'm having fun working with my fusion brain too, so between the two projects, im making loads of progress and having a blast!

Is there any other tricks i should know about? Is there a button command that will activate when both buttons are pressed down? And i just have this nagging feeling i recognize you (or your truck) from explorer forum..

No other special tricks that I can think of off the top of my head. I still have to document a lot of this stuff!

And yes, I'm also on explorer forum as "cherrybomb". I've been a lot more active here since this is my current project, but I intend to post over there when I "finish" this project. :-)

[inh]

Finish, hah! I havent been on EF in forever.. but when i get back to the states and it's time to replace my motor in mine, im sure i'll be back. Hell maybe i'll finish the motor build i had all planned out... woot for off-topicness!

[inh]

There is one thing that I'd like you to add, and then i think this app would be complete.

LED Control.. I think the best way to do it is to add it as an option for each context, as well as being able to send window messages to the app to turn it on or off (for integration with front ends)

[inh]

OK, i'm back at it again. I have context switching from roadrunner working almost perfectly. Im having two issues right now, and i think only one is related to the program, the other might just be some wierd quirk of my system.

The big issue is that when i send the app "CONEXT;Mouse" It will start treating the axe's as the mouse, as per the mouse context, but the buttons still act like they do under my SpaceNavigator context.

The other issue is that no matter what, it wants to start up and default to the SpaceNavigator context, no matter what i set the Default setting to. This just popped up recently as i started playing with context switching, so it might be the program, but it might be my computer as well..

[inh]

Ok, heres the problem, or at least, where the problem is located.

If I have this for contexts:

Code:

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

**** is the variable im talking about below. If i set **** to "Audio" It defaults to loading the SPaceNavigator context.
In fact, any value from A to D does it. But only uppercase. And if i try something like "Dill" it wont cause the error.
If i set it to anything else, Like E, no problems..So it seems the issue is only with uppercase letters, and only those few.

So for now, I set the Context name to Media, for the play/pause commands and the like. So far so good,at least it's switching the contexts now.

Last issue I've found is that when it recieves the command to switch contexts, it does, but the mouse buttons dont get redefined and set to the
new context.

[cherrybomb]

Hey man,

Haven't been ignoring you, I swear! Work has been hectic, and I've been trying to get my CarPC project off the ground.

The good news is, everything is "installed" and my CarPC is operational! WOO! Now to tweak (I'm not even using the SN yet ).

At any rate to address your comments/questions

Quote: Originally Posted by inh

There is one thing that I'd like you to add, and then i think this app would be complete.

LED Control.. I think the best way to do it is to add it as an option for each context, as well as being able to send window messages to the app to turn it on or off (for integration with front ends)

I'll look into adding this, it should be trivial, but I have to figure out how to make it somewhat "generic" for other devices.

Don't worry, it's on the list. :-)

On the last two issues, it's going to be most productive for me to have a copy of your ENTIRE config file. You can just PM it to me.

That way I can run it exactly as you are, and watch it with the debugger.

No promises on how quickly I can fix/change any of this, but I'll take a look at it ASAP. :-)