If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

netremote->go_device DOES NOT WORK!!

Ben,

In investigating why the Zoom Driver's auto-jump facility no longer works, which I had spotted at about the same time as samplehead did, I have made the horrendous discovery the netremote->go_device no longer does anything.

And, as an experiment, I changed the panel name to one that does not exist and I do not now get the error message box that used to appear.

Also - is it neccessary to empty out the Menu device and panel when the Play is registered and empty out Play device and panel when the Menu is registered?

Since you have these in Unregister, you can have both on the same panel, allowing you to add these to a skin (or a frame you copy to all panels, in my demo case) if you remove the Empty call from the RegisterButton.

Thanks for finding the 100% CPU problem. I hadn't spotted the issue at all, probably as in my "normal" use, the 802.11b link to the PPC throttles the performance enough. I guess it would have killed the wireless network though. Also, I'm not a great DVD user. [Enough excuses ...]

go_device never appears to get called from the ZoomPlayer plugin

In my tracing, the strstr was not necessary - I was logging just before and just after the go_device. But I see that using strstr is more robust, so I will switch to that.

Just to clarify, you're testing with the build from August 29th with the fixed jump code, right?

Oops - "fixed jump code"??? ops:
No - I was still running the August 17th.
That might explain a LOT.

Also - is it neccessary to empty out the Menu device and panel when the Play is registered and empty out Play device and panel when the Menu is registered?

Since you have these in Unregister, you can have both on the same panel, allowing you to add these to a skin (or a frame you copy to all panels, in my demo case) if you remove the Empty call from the RegisterButton.

Good idea - I will change.

I will re-do the driver for all these points tonight or tomorrow morning. I also need to incorporate a couple of requests from Jens.

In my tracing, the strstr was not necessary - I was logging just before and just after the go_device. But I see that using strstr is more robust, so I will switch to that.

I should have clarified. The jump code to go to menus never got called in the position update (1100, I think). I had to add this code to the OSD call (1200). If the OSD shows "Root Menu", I had it go to the menu.