dadisigursveinn / 400plus

Automatically exported from code.google.com/p/400plus
0 stars 0 forks source link

Add an option so presets do not overwrite page order #297

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Set mode dial to any option other than A-DEP
2.Go to Settings-->Config. Pages
3.Select a new page order using playback button and UP/DOWN buttons
4.Press AV to save and return to Settings page
4.Switch mode dial to A-DEP

What is the expected output? What do you see instead?
The set page order should be retained in all modes. However, setting to A-DEP 
mode resets page order to default.

What version of the product are you using?
r1507

Please provide any additional information below.
If page order is set while in A-DEP mode, the order is reset after the camera 
is turned off.

Original issue reported on code.google.com by colinban...@gmail.com on 21 Nov 2012 at 10:56

GoogleCodeExporter commented 9 years ago
Do you happen to have a preset "active"?

The ordering of the pages is part of the "settings" saved with a preset; so 
when entering ADEP while a preset is active, 400plus will revert to the 
ordering of the pages when the preset was saved.

In this case, you could disable the "400plus" option in the "Config. Presets" 
menu; then, applying a preset will not overwrite your current settings. 
However, this applies to all settings, and probably it is not what the user 
wants in most cases.

Perhaps we should add a "Pages" entry in the "Config. Presets" menu...

[Thanks for your useful comments, by the way]

Original comment by eduardo....@gmail.com on 21 Nov 2012 at 11:21

GoogleCodeExporter commented 9 years ago
After confirmation from the reporter that this is indeed an issue about the 
presets (see https://groups.google.com/d/msg/400plus/DAnXJChnKks/4WD2WFcyXswJ), 
I'm changing this to a feature request; thanks.

Original comment by eduardo....@gmail.com on 22 Nov 2012 at 6:51

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r1546.

Original comment by eduardo....@gmail.com on 3 Dec 2012 at 10:06