osdmenu - how to have lcd screen close on menu exit

[dmets]

I am using osdmenu with lcddriver. I have a bigclock program active most of the time. When I press the "menu" key on the remote - the big clock program closes, osdmenu takes control of the lcd screen. That part works great.

When the menu exits - I cannot trap to have Girder close the lcd screen. No matter how I attack the problem - I cannot get osd menu to shut down the lcd screen. Not through the menu exit group not through having a check reg in the VirMenuUpdate - nothing seems to work.

If you use programs other than Girder to control the LCD, through LCDDriver, please let me know how you got OSD menu to release control of the LCD screen. Thanks.

Dustin

[dmets]

I just ran some more tests (is there a debug or step procedure in Girder) I put in a ton of "wait" commands to see where and how the processing was going.

My trap actually does work - the display is shut off however, OSD menu makes another call to VirtualMenuUpdate after the on menu exit command. So I am stuck - without being able to turn off the lcd after the menu exits. THere has to be a way....

Dustin

[mattwire]

I will have a look tomorrow.

[dmets]

Any luck? Do you need anything from me? If you want a log or something, I would be happy to provide it - just let me know what and how...

Dustin

[mattwire]

Sorry, I completely forgot. I've had exams so haven't really had time anyway :oops:
Exams finish today :D so I'll take a look tomorrow.

[dmets]

Hope all went well with your exams.

Thanks for putting out such a cool and useful plugin!

Dustin

[Marsupial]

same problem here.

need to trap the menu's timout delay so I stop displaying actual choice on the LCD (afterall its no longer on the OSD) when nothing is selected.

so if you have any idea, I'm all ears!

[Marsupial]

I think I have the solution, but that the solution is buggy for me...

Erm...

Ok. here's the idea. There is one "command to execute on menu close" in the settings when starting this OSD menu... Matt had everything figured on this thing. :D this is just great!

I set this girder command to empty the LCD line where I display the actual selected item.

The way I work it is with several lines on the screen, and only the selected on my LCD.


So this command empty this line. It works, as long as I have girder main window open. If I close girder's main window, then the call seams not to be done.

something I missed in here? how come it works when the girder window is existing (but not focused) and the command is not called when the girder window is not existing....??????

[dmets]

However, that "solution", even with its bugs, doesn't work when you want to close the LCD display so that another program can take contol of the screen...

I've tried using the on menu exit to close the LCD display - OSDMenu then restarts the LCD display and then will not let go of it.

Dustin

[Marsupial]

that's the same I see here... the thing is erased, but rewritten.

have you tried having girder openned? it works like a charm when I have the girder window somewhere in the background. I tought there was a source here.

maybe I should have a 1 sec delayed "user event" to then call the LCD erasure?

anyway, there seams to have a bug in the OSDmenu exit menu feature, seams it sends the signal too soon in the way out so if you use it the menu will resend the signal to LCD

[Marsupial]

I made it work:

I call a (userEvent) delayed command to erase the LCD line I want.

1 sec works like a charm.

:D

[dmets]

Marsupial,

Would the userEvent delay work for what I want to do? (Have Girder close the LCDscreen - so another application can access it?). If so - do you call the userEvent from the exit menu command?

Secondly - would having girder open rather than minimized allow the exit menu command to work propelry without messing with this userEvent?

Thanks. Hope MattWire can find the cause of the problem. Great plugin!

Dustin

[Marsupial]

Well, as far as I understand the proble, its the LCD being called by the menu, and the exit command being called prior to closing the menu leading to a call by the menu to the LCD after the call to the exit command.

therefore, for your problem, it should work as good as it works for me.


For girder window being open, I think it is related to the main window getting focus, blocking event calls. I plainly don't see why having the windows on screen would help the plugin exit command.


anyway, I suggest you get userEvent, there is a lot of potential in this small plugin.

On my side, I changed the clearance action for a "display whatever was on before the menu" event, which is great!