Using set_record(1) did not help to enable the buttons. But luar post_levent_to_ui(4484) does, it is just that I didn't think that it should. But still cannot get the other functions (such as timelapse and change mode) to do anything except loop forever on the luar get_mode() command.
Does set_record(1) switch it into record mode ?
If it does, what does
=return get_mode()
do in chdkptp after calling set_record(1)
In vxworks, switch_mode_usb and set_record do the same thing (switch mode with levent) but maybe this camera needs the dryos style switch_mode since it's right on the transition...
Unfortunately, I do not know how to tell if it has switched to record mode. None of the buttons work and nothing in the display changes, so I presume it does not. Following is the output, immediately after initialization of the camera, of the sequence:
set_record(1); get_mode(); click('menu'); post_levent_to_ui(4484); get_mode(); click('menu');
The menu will not come up until after the post_levent_to_ui(4484):
** init() successful
>> luar set_record(1) << script:6
6:ret:nil (Length: 19)
>> luar get_mode() << script:7
7:ret:false (Length: 21)
>> lua click('menu') << script:8 (Length:
>> script-status << script-status:0x0 run=no msg=no (Length: 31)
>> luar post_levent_to_ui(4484) << script:9
9:ret:nil (Length: 19)
>> luar get_mode() << script:10
10:ret:false (Length: 23)
>> lua click('menu') << script:11 (Length: 9)
>> script-status << script-status:0x0 run=no msg=no (Length: 31)
After dozes of times running the get_mode() in various conditions and after many commands, I have never seen it return anything except a false.
In chdkptp the return from get_mode() is always:
> = return get_mode()
9:return:false
9:return:false
9:return:513
