Could also be added... #define PROPCASE_ICONTRAST // 0=off, 1=auto //
PS2=290, PS3=294, PS4=296, PS6=295, N/A= 9,12,ILC?
PS5=318 (0,1,200,400), & 319 (0=off,200%,400%, 1=auto)
Yes, I started doing this when I made the other change, but then it got complicated:
D10 (PS2):
icontrast is 290, 0 = off, 1 = auto
SX160 (PS5):
296, 318, 319 all 0 = off, 1 = auto
Which camera is your PS5?
Elph130 (PS6):
295, 317, 318 all 0 = off, 1 = auto
G7 X (PS7)
COMBO BREAKER
There is no icontrast setting. Instead, there are two settings: "DR correction" with values Off, Auto, and 200%, and Shadow Correction with Off and Auto.
"DR Correction" is propcase 325 as 0, 1 and 200 respectively.
"Shadow correction" is 303, 0 = off, 1 = Auto
SX710 (also PS7)
has icontrast, both 303 and 325 are 0=off, 1=auto
SX730 (PS12)
308, 330 0 = off, 1 = auto
(aside, also has "Safety Shift" in 234, 0=ff, 1=on)
Elph180 (PS10)
305, 327 0 = off, 1 = auto
This raises the some questions:
* How to name them, especially the cams that have 3. We could do ICONTRAST1, 2, 3, but from G7X they have different meaning in some cases.
* For cams with multiple props but only the icontrast setting, can we control shadow/DR separately using the props? Or use the 200, 400 values, or values in between?
Edit2: Set PS5(298) to -1, now is stable 65535, like PS3, nice for chaining scripts...
Again, I really wouldn't recommend using random, unknown propcases as variables. If you want information to persist between script runs, use a file.