We need a simple solution. And waterwingz's patch is simple and good. Everything else would be more cosmetic improvements.
The patch isn't a solution. The simple solution was the "purpose" in the original post, to hide everything (not just the <alt> line). Why do you want to hide just the <alt> line, anyway?
I fixed the concerns with touchscreens, textbox, and file browser. And MD scripts might want to turn off the chdk overlays.
Purpose: Hide all CHDK overlays, including OSD, Console, and bottom "<ALT>" line. This gives scripts a "clean slate" to draw on.
I'm writing a more generalized solution to the "on/off" problem. It's based on the press/release/click function idea.
on("switch")
off("switch")
toggle("switch")
boolean_variable=status("switch") -- this function isn't really necessary. toggle() could also return the status, if needed
"switch" can be anything you want to turn off or on, including:
"alt", "osd", "console", "overlays"
"backlight", "display" (display on/off capability to be added)
"led1","led2" (turn led on/off camera independently - future possibility)
====
I'm also considering the single function:
boolean_variable=status("[+ | - | ~]switch")
for example:
status("+alt") -- means turn on "alt" line display
status("-alt") -- turn off "alt"
status("~alt") -- toggle "alt"
boolean_variable=status("alt") -- no change in "alt" state
Just saw this:
One further digression. I was chatting with reyalp on IRC last night and he suggested using something like
It sounds like you're going to do what you're going to do, but it's not a solution to the original "purpose" of this topic. I'll write up my solution and add it to my custom build, and others can use it if they want.