On-screen Menu help please

[mattwire]

Problem 2: There were some problems with path resolution in OSDMenu 1.3 so that part was rewritten somewhat for version 1.4.
Basically you should not use quotes for the executable path with v1.4 but you do with 1.3. This is why 1.3 fixes the problem.
So for 1.4 you would use the following:
...
myevent=c:\program files\girder\girder.exe -eventstring bla
...
(substitute your path for girder of course).

Problem 1: Can you test the Girder 3.2/Osdmenu 1.5 for me to see if the same thing still happens.
I develop in win2k so I don't always notice 9x problems.

[stevech]

On my WinXP main machine I developed a nice Girder 3.1 config permitting me to direct Internet Explorer to different web pages, using the IR remote (via irMAN) or the PC keyboard. Such as customized TV show listings, weather, and my own web server. Works fine.

Now I moved the GML file and the OSD Menu "ini" file to my Windows 98SE machine on which this is to run for real (my home automation machine).

There are two odd problems I'm stumped on:

1. If Girder 3.1's window has the focus when I press the IR remote key to cause a menu to pop-up (via OSD Menu's DLL), the Girder event for On Menu Start is highlighted, but the menu doesn't pop-up. If I move the focus to any non-Girder window, then push the IR remote's key, the menu DOES pop-up correctly. This doesn't happen under XP - just Win98SE.

2. Under 98SE, the menus still come up properly, but the menu choices which generate Girder eventstrings don't work. Nothing regarding receipt of the event is displayed by Girder. Same with both keyboard and IR remote. The pathname for girder.exe in the menu ini file is correct - I typed that exact line of text into a DOS CLI window and the Girder event did fire correctly. Also, my menu has a choice for the pop-up message box as in the sample ini file - it DOES work correctly. Just the two menu choices for Girder events don't work, again, under 98SE but works OK under XP. So I don't think its a DLL problem. I checked that both machines have the same DLL - they do. I tried OSD Menu 1.3 and 1.4. I tried Girder 3.2beta on the 98SE machine and fell back to 3.1 due to other problems.

Stumped for now. Seems unlikely, but could this be related to the fact that I fell back to Girder 3.1 on this 98SE machine? I did an uninstall of 3.2 and reinstalled 3.1. I don't think so, since it seems to be invoking the OSD Menu plug-in's DLL OK.

[stevech]

Follow-up to problem #2 - I've hosed myself somewhat by having both v 1.3 and 1.4 of OSD Menu on the '98SE machine. In Girder's ACTION PLUGINS settings, I changed from 1.4 to 1.3 and now Problem #2 went away. I'm confused about having the choice of 1.4 and 1.3 but there's only one DLL file.

Problem #1 persists but does not prevent normal operation.

[stevech]

THANKS for a great add-on to Girder.

Quotes on the path - would it be possible to have a global param for this? The ini files have to all be changed if the path changes. Or I guess I can struggle witn WIndoze to get Girder's name in the path. Wish I hadn't wasted hours struggling with the 1.3 vs 1.4 issue - I didn't notice that change about the quotes.

I'll try Girder 3.2 on 9X when I can - My only 9X PC is the one I'm trying to stabilize for real use by the most demanding user: My Wife.

[Icthus]

Girder 3.2/Osdmenu 1.5 works great for me. Just got it set up and everything seems fine.

Thanks for a great plugin.