And here's one more little quirk I was shown by one of our many script users.
If you attempt to use the Playback key to check images while running the script then you usually can see your most recent image.
But only if the Playback key is your <ALT> key. And only after the HELP screen comes up. And with no playback functionality like scrolling through the stored images (as the arrow keys are still grabbed by the script).
And if you have Playback set as the <ALT> key, and you don't press long enough to bypass that, you get dumped out of <ALT> . Running the script while not in <ALT> gets really nasty and really confusing very quickly.
Ideally, the script would be able to prevent the user from leaving <ALT> (much like it currently hijacks the "full press" key). One simple way to add that would be to have
set_draw_title_line() disable exiting <ALT> - either implicitly or as a passed parameter option (i.e. set_draw_title_line(1) = <ALT> line hidden, set_draw_title_line(2) = <ALT> line hidden and <ALT> exit disabled ).
It would also be nice to be able to detect the playback key. It's defined as KEY_PLAYBACK in many camera
kbd.c files but not in
modules/script_key_funcs.c. With it defined, the script could control the switch between shooting and playback modes and it would allow things like the arrow keys to work by simply passing them through in playback mode (the same way the zoom level works now in shooting mode.
Every so often I consider just re-coding this whole thing in C as a module. But so far, with some tweaks to core CHDK functionality, I have not discovered a need to do that give the power of Lua. Other than making it easier for the user to access (without going through all the steps of downloading the script and installing it and selecting it as the current script and then getting into <ALT> mode and pressing the shutter button ...)
