Re: [gphoto-devel] Canon EOS custom functions

[Marcus M. <ma...@je...>]

Hi Axel,

I applied it, replacijng one gp_log by ptp_debug.

On Fri, Apr 06, 2012 at 03:41:10PM +0200, Axel Waggershauser wrote:
> To whom it may concern... ;-)
> 
> attached is a patch to enable some _very_ low level (but therefore
> general) access to the custom functions of (modern) EOS cameras. But
> before anyone gets excited: this is nowhere near something like
> 
>     gphoto2 --set-config mirrorlockup=on
> 
> instead it's more like
> 
>     gphoto2 --set-config
> customfuncex=60,1,1,54,6,101,1,1,102,1,0,104,1,0,105,1,0,106,2,2,1,108,1,0
> 
> 
> The background details: There is a PTP property called CustomFuncEx
> (hex code 0xd1a0) for accessing custom functions. Unfortunately, this
> property is not like any other standard PTP property (like e.g. the
> aperture property, which has exactly one meaning and one value at a
> time and you can select a value from an automatically enumerated list
> of supported values):
>  * the CustomFuncEx property represents all custom functions at the same time
>  * the list of available functions may differ from camera to camera
>  * there is no automatic enumeration of available values for
> individual custom functions
>  * the individual custom functions can only be changed/accessed in
> groups simultaneously
> Therefore it does not fit into the libgphoto2 supplied structures to
> access camera properties. And therefore I came up with this minimal
> invasive patch with the downside of having a horrible user interface.

I think it might still fit...

We could do per-camera model hooks that on "set" get the previous
customfuncex, exchange the relevant part of the specific function and write it back

Just some work on all the functions though :/

Ciao, Marcus