Save Bug - General Help and Assistance on using CHDK stable releases - CHDK Forum supplierdeeply

Save Bug

  • 4 Replies
  • 1327 Views
Save Bug
« on: 29 / January / 2012, 17:11:20 »
Advertisements
BUG!

NOT specific to anay Build
as i have run a few and all do the SAME

ixus220_elph300hs-101d-1.0.0-1532-full_ALPHA
ixus220_elph300hs-101d-1.0.0-1545-full_ALPHA
ixus220_elph300hs-101d-1.0.0-1557-full_ALPHA
ixus220_elph300hs-101d-1.0.0-1571-full_ALPHA
ixus220_elph300hs-101d-1.0.0-1599-full_ALPHA
ixus220_elph300hs-101d-1.0.0-1611-full_ALPHA
ixus220_elph300hs-101d-1.0.0-1619-full_ALPHA




Camera CanonPowerShot 300HS

when you go and load a script or make changes to settings "MOST" of the time CHDK does not save them 99% of the time.
EVEN with the option >Clear override values@start< UNticked
AND
>Save params< TICKED
and when you turn your camera off and then back on....
it Reloads the default script and all the changes you have made are lost.

I have found a way to make SHURE it saves the settings.

#1 load your script
#2 make your changes and use the >Go Back<

#3 then exit all menus
#4 then Re enter menu
#5 Then close menu

Then your settings are saved.
« Last Edit: 29 / January / 2012, 17:25:41 by radioman193 »

Re: Save Bug
« Reply #1 on: 29 / January / 2012, 17:28:06 »
I have found a way to make sure it saves the settings.

#1 load your script
#2 make your changes and use the >Go Back<
#3 then exit all menus
#4 then Re enter menu
#5 Then close menu

Then your settings are saved.
I believe I have noticed something similar on my cameras but I could never quite put my finger on it.  And I've come up with similar things as what you suggested to get around it. 

I've also not figured out how to make the Parameter set values work correctly.   There must be some magic sequence needed - maybe I'll go "cave diving" in the code and see if I can figure it out.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: Save Bug
« Reply #2 on: 29 / January / 2012, 17:42:06 »
I must have found the "magic sequence " cause if i do it this way it works everytime...
its just a hastle when your out in -14 weather and wind to play the "magic sequence  game"   :(
« Last Edit: 29 / January / 2012, 17:45:37 by radioman193 »

Re: Save Bug
« Reply #3 on: 20 / February / 2012, 03:59:39 »
im still haven problems with this isue    :(



*

Online reyalp

  • ******
  • 12934
Re: Save Bug
« Reply #4 on: 20 / February / 2012, 16:50:02 »
Assuming I've understood the code, the params are only saved if you actually run the script (from the gui) after setting, or change the parameter set number.  It seems to do this OK on my cameras. The entire param saving thing is a horrible mess.

Two other possible issues:
1) DryOS has trouble with file names longer than 8.3. The names of the files where the script params are saved are generated based on the script file name, and can probably run into problems with this

2) If you use lua and ubasic scripts with the same name, they will share the same files for the params. Same if you use scripts with the same name but different directories.

Don't forget what the H stands for.

 

Related Topics