Button not releasing with Girder?

[JeffS]

I have a CCF (.994 verified in .99 as well) with a button that send a cmd to girder to put JRMC into fullscreen mode.

Frequently (more often than not), the button remains depressed on the NR side and it starts looping into girder sending the command to JRMC over and over again.

The button has an action defined as:
5001 0000 0000 0002 ffff 0000 0001 0000 with a name of MCVIZ.FULLSCREEN

In girder, I'm using the std JRMC GML with a window message for the fullscreen view action.

The exact same behavior is true for a similar button that puts JRMC in Hairstyle mode.

When this occurs it is clear that the button in NR remains in a depressed state.

Any thoughts on debouncing the button in NR or Girder?

-jeff

[Ben S]

Hi Jeff,
Can you send me the .gml and the .ccf and I'll put it through the debug process?

[Ben S]

I think Jeff and I have found a solution - and it's actually pretty neat. It should make repeating commands a lot cleaner/more stable. Jeff is playing with the new code to make sure it's stable enough, and then I'll release it to everyone.

[JeffS]

Ben's fix resolved the issue I had. The situation was when NR and JRMC were running on the same machine.

The command I was invoking via girder was to switch JRMC into full-screen or hairstyle mode which usurped the mouse events from getting back to NRW32

The only potential issue I've observed is:

Send the hairstyle cmd from NR to Girder. JRMC goes into hairstyle mode.

Send the fullscreen cmd from NR to Girder. JRMC goes into Hairstyle mode -

In both cases, the underlying girder cmd when tested independently works fine. The log in girder shows the right message coming from NR, but when girder posts the window message (using sendmessage in girder), JRMC responds with hairstyle.

If I change the girder action to use the mjextman.exe - they both work.

Not sure if the change in NR had anything to do with this, but these commands worked independently before the NR change.

Thanks for the quick turnaround Ben

[Ben S]

No problem. I'm glad we were able to fix it. This should assist with some other problems people were having, as well. It -may- even fix the Toshiba light issue (believe it or not). I don't have a Toshiba so don't know for sure.

This fix will be in the next update (most likely available this weekend).