You can still exit_alt() under script control. Can you think of a use case for doing it via the <ALT> key while a script is running?

(Spin this to its own thread ?)

Quickly adjust something in the canon shooting menus (though if the script itself also listens for keys, this wouldn't work well) ? I have no idea if people use it this way, but it seems more like a behavior change than a bug fix to me.

After a little thought, being able to actually use the button assigned to <ALT> in a script on cameras with few actual buttons seems even more attractive.

As my initial patch is a "no" on the assumption that somebody somewhere might want to actually exit <ALT> mode while a script is running, is it worth me even taking the time to submit a patch with a menu item that lets you select the desire behavour? Or a new script command? [ e.g. alt_button_mode( mode ) ]

Or are you really saying I should drop this and the "full_press" trap patch and wait for the complete button patch:

I think I know what you want there - I suppose I could just take a whack at that instead. The actual code that remaps button presses in real time seems easy enough. But getting a usable UI with the existing menu code will probably be difficult. As will handling the various camera button configurations and touch screen cameras. And whatever UI does the mapping, a script interface to read & set button choices is going to be needed. Other than that, no problem

I think the current <alt> key behavior is an unintended bug. I can't imagine anyone using it. Most users don't understand what's happening when a script is running, so it's not wise to let them leave <alt> mode at any random time while running a script. The behavior of the script is unpredictable and unintended by the script writer. Furthermore, if you hold the <alt> key down while a script is running, it exits <alt> mode and sends the real <alt> keystroke to the camera. For the sx260, that switches my script to <play> mode. In any event, it trashes the script and you can't even tell it's still running. Let's fix this.

I think the current <alt> key behavior is an unintended bug. I can't imagine anyone using it. Most users don't understand what's happening when a script is running, so it's not wise to let them leave <alt> mode at any random time while running a script. The behavior of the script is unpredictable and unintended by the script writer. Furthermore, if you hold the <alt> key down while a script is running, it exits <alt> mode and sends the real <alt> keystroke to the camera. For the sx260, that switches my script to <play> mode. In any event, it trashes the script and you can't even tell it's still running. Let's fix this.

Have to disagree. I believe it would be better to fix whatever is broken and allow scripts to run correctly whether CHDK is in <ALT> mode or not. The audio meter script is a perfect example of why this would be useful.

Have to disagree. I believe it would be better to fix whatever is broken and allow scripts to run correctly whether CHDK is in <ALT> mode or not. The audio meter script is a perfect example of why this would be useful.

While I disagree with making script abort an <ALT> key function - for reasons I've posted on the other thread - I still struggle with going out of <ALT> mode while a script is running by pressing the <ALT> key. In the case of the audio meter script, the script could use the exit_alt() command to get out of <ALT> mode as it was designed to run that way! Doing it accidentally with any old script is not a good thing.

Have to disagree. I believe it would be better to fix whatever is broken and allow scripts to run correctly whether CHDK is in <ALT> mode or not. The audio meter script is a perfect example of why this would be useful.

While I disagree with making script abort an <ALT> key function - for reasons I've posted on the other thread - I still struggle with going out of <ALT> mode while a script is running by pressing the <ALT> key. In the case of the audio meter script, the script could use the exit_alt() command to get out of <ALT> mode as it was designed to run that way! Doing it accidentally with any old script is not a good thing.

I'd argue that running scripts in alt mode is a design flaw and by default scripts should always run in normal mode. Entering alt mode should pause the script so you can change CHDK settings. This would also allow for script menu options to abort/pause/restart the currently running script.