I am using the normal motion script.
Or enable the 'debug keymap' code in the gui_draw_debug_vals_osd() function in core/gui.c.Phil.
so far most of the memory mapped i/o for buttons etc has ended up in a three word array. It's read in platform/s100/kbd.c at the start of the routine my_kbd_read_keys(). At one point I printed the whole array to the screen from the spytask() when I was looking for something. If you look at the bottom of the spytask code in core/main.c you can still see where I inserted the hack - its commented out now with a #ifdef DEBUG_PRINT_TO_LCD ....
On the first script issue I had with the script causing fisheye. I tried shooting in raw (canon raw) and got no fish-eye distortion.Could the camera be correcting this even in Raw?
I go uncomment these... build... and then have no idea what I am supposed to do after that....or if I am even doing it right am I missing something?Can you guys explain a little more?
Has anyone used the Motion Detect script on the s100?The MD script tries to focus after detecting motion unless you have MF set up on the ring.
Started by Brando
Started by mv3830
Started by x3oo
General Help and Assistance on using CHDK stable releases
Started by hiker_jon
Started by ironsting