I'm wary of having scripts that don't allow you to terminate them via the keyboard, at least without some notification to the user.I definitely understand the use case, but the potential for frustration of users who download the script is high. Especially if they enable autostart, which seems to happen occasionally.
'shoot_full' as a script feature that is a very good but also dangerous plan.
I think, a menu option for this feature is not the best way. It would be better to use only a script function to activate the shutter as a 'script button'.
Also the problem autostart should be clarified.
Can you share why you think its dangerous? If it's just because the user could no longer stop his script with the shutter key, then my idea of having a "long press" of more than 1 second to stop the script should be enough to mitigate that risk? And there is always the On/Off button as a backup.
QuoteI think, a menu option for this feature is not the best way. It would be better to use only a script function to activate the shutter as a 'script button'. Again, why ? I suppose because the menu option would only be useful with a script that is going to map the shutter button - so you might as well just have the script set that mode?
Self Edit : the problem with the "long press" to abort solution is that is does not allow you to script "continuous shooting" situations where the user holds the shutter button down and the script keeps shooting until it's released .. drat.
Quote from: waterwingz on 24 / August / 2013, 18:49:33Self Edit : the problem with the "long press" to abort solution is that is does not allow you to script "continuous shooting" situations where the user holds the shutter button down and the script keeps shooting until it's released .. drat.How about the <alt>+<shutter> idea? The script can't see <alt> anyway, so it would never use that combo.
How about the <alt>+<shutter> idea? The script can't see <alt> anyway, so it would never use that combo.
Also, there are times when you'd like to interrupt the script RIGHT NOW, so a long press is undesirable.
One idle thought:The script can call set_abort_key("keyname")whatever the key is will never be seen by script. All non-abort keys will be passed to script, so if you set it to something other than shutter, you get shutter. If we add the ability to detect what keys are valid for the camera, we can enforce that too. The abort key could even be displayed in the ui, if you wanted. This would mean scripts would always have to sacrifice one key.It could potentially be allowable to set it to the alt key, so the first alt press ends the script, and subsequent would allow you to leave alt.I'm not sure this is a good idea, just a thought...
This is proving to be way too hard.
If we provide a mechanism for an advanced script to capture the shutter button at full press, it seems reasonable that such a script would also provide a mechanism to exit the script. You're always pushing back against adding functionality to the C core that can be done in the script. This feels the same. After all, there is always the power button. The extremely special case of autostart can be handled by deleting the script from the SD card if that ever happens.
Started by waldo
« 1 2 3 »
General Discussion and Assistance
Started by binsurf
Started by pwcal2
Started by NaveedESahar
General Help and Assistance on using CHDK stable releases
Started by Kestrel1978
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)