As a general question: Is it relavant that on some cameras without a jogdial or "touch control dial" the "wheel l" and "wheel r" buttons work in executing left / right movement while for some others they just don't do anything? I didn't mention where they don't work if the camera has no dial but just noticed on the I750 that the buttons worked so I was wondering that.
Oh that's a good catch. For reasons I don't remember, chdkptp actually uses post_levent like
post_levent_to_ui("RotateJogDialLeft",1)
instead of calling CHDK wheel_left and wheel_right script functions. So it works if the Canon firmware recognizes it, which I guess some non-jogdial cameras do.
Unfortunately, this also means that testing the GUI buttons didn't tell us if the script wheel_left and wheel_right functions work correctly.
If you want to add
=wheel_left()
=wheel_right()
to your tests, that would verify the CHDK functions. However, it's pretty unlikely that the keyboard changes would have broken these, so it's OK if you don't want to, and you don't need to go back and retest the cams already done.
Note on USB Remote: The cam only has the odd wide connector for its charging bowl and the bowl has the USB connector. When the cam is in the bowl it won't go to Rec mode unless told to by CHDKPTP. So, in order to test USB Remote I connected by CHDKPTP, went to Rec, disconnected, set the remote options up and could then use them (using the remote on the bowl's usb port). So yeah it works.
This is interesting, in previous discussion about this camera
http://chdk.setepontos.com/index.php?topic=11723.msg114947#msg114947 it wasn't clear the USB remote could be made to work at all.
This is a very old/unique camera, so if you don't want to mess with it more that's fine. Anyone who wants to actually use it can be directed to these threads. Information for future reference below...
From the above, I think there is a separate way the camera detects whether it is in the bowl (cradle), independent of the the USB bit. There is a good chance this is another physw bit. Based on the old thread, the USB bit is 0x08000000 in physw word 1 (and works, per your test above), and the other bit (if it exists) is NOT in word 1.
If you want to look at the other two words of physw_status in this camera without the bowl, that might be interesting. To do this, you can use the memory browser and look at 0x10FF0 and 0x10FF8 with and without the camera in the cradle.
There are also some possibly related event procs.
UiEvnt_StartDisguiseCradleStatus
UiEvnt_StopDisguiseCradleStatus
UIFS_SetCradleSetting
These functions would (probably) be registered with call_event_proc'UI_RegistDebugEventProc' and may need set_levent_script_mode(1) before taking effect.
And levents
AttachCradle
DetachCradle
it's possible that post_levent_to_ui'DetachCradle' will allow normal mode switching.
