Display button disables scripts

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Activate the !Intervalometer script with whatever options
2. Press Set button to start the script
3. Press Disp. button to turn off display and preserve battery

What is the expected output? What do you see instead?
Expected the script to keep on running in the case of a very long 1 minute 
sequence of photos. I saw that the blue led stopped blinking and after the 1 
minute, 2 minutes 3 ... of proposed time in the script, no photo was taken. 
When the Disp. button was pressed again, the script resumed.

What version of the product are you using?
400plus-20120415-11.bin.zip 

Please provide any additional information below.

Original issue reported on code.google.com by carlozo...@gmail.com on 9 Jul 2012 at 9:16

[GoogleCodeExporter]

Sorry, I mentioned I was using the stable release ... but it's the nightly ... 
    400plus automated build - 20120709 - r1394 

Original comment by carlozo...@gmail.com on 9 Jul 2012 at 10:46

[GoogleCodeExporter]

Users are not expected to press any button while a script is running, but it 
surprises me that DISP can pause a script that way; I'll have a look at it.

In the meantime, remember that there is an option to make the scripts turn the 
display off automatically when they start.

Original comment by eduardo....@gmail.com on 10 Jul 2012 at 12:47

[GoogleCodeExporter]

Confirmed: pressing the DISP button stops the execution of the script (even the 
DP signaling stops). This only happens if "Review time" is set to "Off" in the 
camera's standard menu, however.

Looks like the camera enters some sort of "low power" mode when this button is 
pressed, and all tasks are set to sleep. Perhaps we could block the button 
while a script is running, but I'm not sure we want to do this.

Original comment by eduardo....@gmail.com on 10 Jul 2012 at 9:24

• Changed state: Accepted

[GoogleCodeExporter]

Can we change the "Review time" to != "Off" while the scripts are executing ?

Original comment by fired...@gmail.com on 11 Jul 2012 at 8:29

[GoogleCodeExporter]

> Can we change the "Review time" to != "Off" while the scripts are executing ?

Don't see why not!

What is still not clear to me is whether this is a feature or a bug, if we 
should try to fix it, or just document it. So we have found that the camera has 
this low-power mode, that pauses all tasks, and it interferes with our scripts; 
well, do we want / need to (optionally?) block that action? or is it useful to 
users? ...?

Original comment by eduardo....@gmail.com on 11 Jul 2012 at 9:16

• Changed state: Started

[GoogleCodeExporter]

I was almost sure that this would be the case... Pressing the DISP button will 
turn off the display (expected). Once in this mode the camera "knows" you do 
not need to see anything on the display and therefor will set the "sleep" timer 
to expire sooner. If the display is on, then it is normal the "sleep" timer to 
wait longer. This is expected behaviour IMO.

I agree that we should decide if this is a feature for us or a bug. I vote to 
leave it this way and document it.

Original comment by fired...@gmail.com on 11 Jul 2012 at 10:34

[GoogleCodeExporter]

This issue was closed by revision r1412.

Original comment by eduardo....@gmail.com on 29 Jul 2012 at 9:28

• Changed state: Fixed

[GoogleCodeExporter]

Hi, and sorry for the late response as I was on external work, and had no 
internet. I downloaded the 1423 version of the nightly and the problem 
persists. Upon activating the intervalometer, the camera starts shooting 
pictures and as soon as I press the Display button to turn off the display, the 
script stops and so does the flashing blue led. On the settings, I activated 
the "turn display off" and the scripts do not run if this option is set. So i'm 
at a bound right now ...
Thank you!

Original comment by carlozo...@gmail.com on 12 Aug 2012 at 3:43

[GoogleCodeExporter]

As has been commented above, pressing the DISP button will stop the camera; 
this is expected behavior.

On the other hand, I tried to launch a script with the "LCD display" option set 
to "Off" in the "Config. Scripts" menu; while it did not managed to power the 
display completely off, it completed the script without incidents. We are going 
to need more info about your options; could you save your configuration as a 
preset and post it here, please?

Original comment by eduardo....@gmail.com on 12 Aug 2012 at 8:42

[GoogleCodeExporter]

"LCD display" option set to "Off" seems does not work for me..

Original comment by hip80...@gmail.com on 27 Jan 2013 at 3:51