great, many thanks, now Zebra and edge overlay work perfect with your Fix
I only see that histogram seem not work correct.seem it read some random data.
I can produce the problem by do this steps.
switch on Camera, so it go direct to 4:3 or in Case of G12 to 1:1 shooting mode, and then move camera to a dark place(without press of shutter).now on my camera always the overexpose signal is show, and you can see that there are bright pixels in the history line at end .the problem was before your fix too in.so seem only histogramm code problem
when you switch mode during run from 16:9 to 4:3 then no overexpose is show, i guess the buffer keep some 16:9 data which is always read from 4:3 histogram.
only when you was in 16:9 mode and have a overexpose part, then its possible that 4:3 always show overexpose
EDIT:
maybe to get bracketing work G12 SX30 and some other define need add here.Ixus1000 and SX210 is add here too
http://chdk.setepontos.com/index.php?topic=5574.msg60231#msg60231@@ -736,10 +736,12 @@ short shooting_get_drive_mode()
736 736
defined (CAMERA_a480) || \
737 737
defined (CAMERA_s90) || \
738 738
defined (CAMERA_sx20) || \
739
- defined (CAMERA_d10)
739
+ defined (CAMERA_d10) || \
740
+ defined (CAMERA_ixus300_sd4000)
740 741
short n;
741 742
// unlike other cameras, sx200 does set PROPCASE_DRIVE_MODE when in custom timer mode
742 743
// SX 200 IS 0,1,2,3,4=Off, 2 Second, Custom, Face Detection
744
+ // SD4000: 0,1,2,3 = Off, 2 Seconds, Custom timer
743 745
_GetPropertyCase(PROPCASE_TIMER_MODE, &n, sizeof(n));
744 746
// note we return this only in custom mode.
745 747
// Other cameras would return 3 if any timer mode is set (?) even if it doesn't do multiple exposures
