Device "On Select"

[brockgr]

The events set in the device properties' "On Select" section do not seem to work.

Or is this just me?

Gavin

[Ben S]

It's not just you.

This is something Dave T. and I discussed a bit in the past.

The question was should OnSelect fire only when the device is selected from the drop down menu of devices, or only when a jump button first goes into a device, or both?

Currently it is disabled.

[brockgr]

Although it may be annoying, I think it should be whenever the device is opened, throgh the user selection, a jump command, or a NR Jump to Device feedback command.

Gavin

[mrallen]

On a 'real' pronto it only executes when you select the device from the pull-down list. Generally, I find it to be a totally useless feature.

[brockgr]

Sorry, didn't realises that was the intended behaviour. It is pretty stupid, but we probably shouldn't break it. Maybe we can add another event? NR.PANEL(device,panel)?

[mrallen]

You read my mind. I would really like that call. However, the existing NR.HOME and NR.DEVICE implementations are totally unreliable and need to be fixed first.

[Ben S]

I'm confused. What is meant by NR.HOME and NR.DEVICE? The events from Girder firing back to NetRemote?

Gavin, when you say NR.PANEL should be added, is this Girder?

Sorry for being dense.

[brockgr]

What I was suggesting an extra NR->Girder Internet Event that is fired on entering any panel. The playolads would be the device and panel - not user configurable. It would then be up to girder what to do with the event.

If we wanted a user confiurable event - e.g. "sent event 'FOO' on entering this panel', it would require some way of coding it into the CCF (Stewart?)

- Gavin

[mrallen]

you wouldn't need this encoded in the CCF unless you only wanted that event sent for select panels. you could have NR send the event on every panel change. that's not such a bad idea. in fact, I'd actually prefer the scenario with buttons where *every* button press generated an event (the buttons ID was sent -- NR currently ignores this) instead of just ones with specially marked IR actions. this is a perfect use of the button ID field and it's much cleaner/simpler (IMO) than the IR codes. (button ID is a separate field from Name).

[Ben S]

Does the button ID allow text, or is it a number only? I didn't even know the ID was embedded in the .ccf. My bad!

Would the button ID somehow specify the driver ID? Unless we break NetRemote up and have all the drivers (other than the WebBrowser and WOL drivers) on the serverside, with the ID being "configured" there, I'm not sure how NetRemote would know which driver it's intended for.

Gavin, the "I'm on device/panel" might be easily handled. When you enter a panel, any buttons marked as certain drivers are "registered" in the driver. When you exit a panel, those buttons are "unregistered". So if you hit a panel that has Girder buttons, I could easily have it send the device/panel name it's on (instead of the RESEND event you're getting now).

[mrallen]

The button ID is a text field just like name. Look in button properties at the bottom in Tonto. My strong preference is to have every event sent to the server over the same TCP connection and let the server sort it out. It's a much cleaner architecture.