and what isPressSwOne, UnpressSwOne (this is shoot half)
PressSwTwo, UnpressSwTwo (this is full shoot)
You could send these from script using post_levent_to_ui, but it's not really a solution for CHDK.
Are you able to shoot using scripted key presses, like
press('shoot_half')
sleep(500)
press('shoot_full')
sleep(100)
release('shoot_full')
?
What should i do on this state? Try to verify PROPSET by CHDKPTP right?
Please recommendation, i will try to learn!!!
If PROPCASE_SHOOTING is not correct, that can cause problems with the shoot command. Some digic 6 cameras need a special workaround (see platform/generic/wrappers.c get_property_case). So far we have not seen this on older processors.
If the raw hook is incorrect, that can also interfere with scripted shooting. You should check raw_process is reached when you shoot.
Try CHDK-PTP but no respond at all, just download image and some cmd.
Are you using windows or linux? On windows, you need to need to set up the driver with zadig. On linux, you probably have a problem with gphoto udev rules. Some information on both
https://app.assembla.com/spaces/chdkptp/wiki/InstallGenerally to verify propcases using chdkptp, you can
After starting chdkptp, run
!require'extras/devutil'.init_cli()
Then for each thing you cant to check, you can use dpget to make a copy of the current values, change a setting (like shooting mode etc) and use dpcmp to see what has changed.
If you the propcase updates after halfpress (like the shutter speed in P mode) you can send some code to run before the values are read, like
dpcmp -c='press "shoot_half" sleep(500)'
You don't need chdkptp to do this, you can use the propcase viewer or one of the scripts, but chdkptp is helpful for development anyway.
