The 'ALT start' idea is very good. I think every extra method to start a script is welcome.However, the easiest way would be a start via user menu. But this is certainly a challenging task.
The behavior when you enter and leave the script menu seems a bit confusing. When you first set the auto start option to alt, the script starts when you leave the menu using the menu key. If you subsequently enter and exit the the script menu, it doesn't. Exiting the script menu via the alt key works as you'd expect, the script starts the next time you enter alt.
The other thing that concerns me is if a script changes the script abort key to something that doesn't work on the camera, the only way to get out of it would be deleting the script or cfg using a card reader, since you can no longer enter alt to change the setting. I guess this is true of autostart as well.
The whole thing feels a bit kludgy, but I admit I don't really have a better idea...
I prototyped a version of the above patch that also spits out a 1 second warning on the title line prior to starting a script on <ALT> entry.
Incidentally, my download script to transfer CHDK to the SD card via ptp does not like this patch either - it forces the download to wait one second between modules while the warning message displays. Are there other unintended things that happen with CHDKPTP and these patches?
There is still a possible issue with a script being started on <ALT> entry and then overriding the exit key, disabling the title line, and setting the console to "OFF", thereby leaving the user confused if the script dies somehow.
Started by jetzt
Started by igor
RAW Shooting and Processing
Started by Blackadder
Started by nstoker
Started by pigeonhill
General Discussion and Assistance