UI properties (PTM functions) - page 3 - General Discussion and Assistance - CHDK Forum supplierdeeply

UI properties (PTM functions)

  • 49 Replies
  • 12954 Views
*

Offline srsa_4c

  • ******
  • 4005
Re: UI properties (PTM functions)
« Reply #20 on: 01 / July / 2015, 17:49:20 »
Advertisements
But I didn't find properties for:

Tools: Lens Retraction
Tools: Power Saving: Display Off
Tools: LCD Brightness
Tools: Start-up Image
Tools: Create Folder
Tools: Video System
Tools: Language
A significant amount of UI settings seem not to be covered by these properties.
Quote
Probably, c6 is not latest property for Ixus 160 ?
I did not check this, I don't know. I have however seen cases where one of the firmware's property-like systems had "special cases", IDs in an unusual range. I don't remember if those were "UI properties" or not.
Why not to create standard Lua functions for UI properties, like http://chdk.wikia.com/wiki/CHDK_Scripting_Cross_Reference_Page ?
That would be the plan sometime later...
But note that the nature of these properties makes their use difficult (they tend to be different in each camera model). The ideal solution would be an abstraction layer, but I don't see the huge amount of contributors that would make it possible...


I spent a little time building from srsa_4c's patch above but, based on msl's kind pointer here http://chdk.setepontos.com/index.php?topic=12428.msg123114#msg123114, still wasn't able to do / discover anything useful on my sx150is
Both current "stable" (1.3) and development (1.4) releases have the UI property research tool, the patch is no longer needed...
Quote
If a slightly more comprehensive "howto" were to appear that would be a welcome hand up
My poor English skills usually fail when I try to explain something in detail. So, indeed, an improved howto would be really useful.

Re: UI properties (PTM functions)
« Reply #21 on: 02 / July / 2015, 00:01:15 »
But note that the nature of these properties makes their use difficult (they tend to be different in each camera model). The ideal solution would be an abstraction layer, but I don't see the huge amount of contributors that would make it possible...

I don't think abstraction level is possible at all, since different models contain a little bit different set of settings, and modes. But these properties will be very usable for individual cameras. If we will have good tool for values investigation, it can be useful.

2andrew: I can send my own tool for UIProperties values investigation. It uses USB connection to camera. Theoretically, this very simple code can be included into chdkptp.

Re: UI properties (PTM functions)
« Reply #22 on: 02 / July / 2015, 01:26:09 »
Some fixes in properties list in the attachment(800d and defaults)

BTW, shouldn't we create some place in wiki/svn/git for upload such files ?

Re: UI properties (PTM functions)
« Reply #23 on: 02 / July / 2015, 04:12:50 »
2andrew: I can send my own tool for UIProperties values investigation. It uses USB connection to camera. Theoretically, this very simple code can be included into chdkptp.

alex73, i'd really appreciate that :) 


Re: UI properties (PTM functions)
« Reply #24 on: 02 / July / 2015, 05:55:45 »
So, for run my test utility you need:
1. Download chdkptpJ-0.1.zip from https://github.com/alex73/chdkptpJ/releases
2. See http://usb4java.org/faq.html for setup your Windows/Linux box for using usb4java/libusb
3. Run from command line by command java -cp * TestUIProperties

It should work, but you know - this library is too young. Feel free to ask if something will be wrong.

Re: UI properties (PTM functions)
« Reply #25 on: 02 / July / 2015, 06:09:59 »
Downloaded (&bookmarked).

Will report back when I get a chance.

Thanks.

Re: UI properties (PTM functions)
« Reply #26 on: 03 / July / 2015, 03:15:08 »
But note that the nature of these properties makes their use difficult (they tend to be different in each camera model). The ideal solution would be an abstraction layer, but I don't see the huge amount of contributors that would make it possible...

BTW, even without identify all UI properties for specific camera, we could implement something like "save full state". That means, some software will just read all properties values into file, then wil "restore state", i.e. will read file and set all properties.

*

Offline srsa_4c

  • ******
  • 4005
Re: UI properties (PTM functions)
« Reply #27 on: 03 / July / 2015, 18:05:51 »
BTW, even without identify all UI properties for specific camera, we could implement something like "save full state". That means, some software will just read all properties values into file, then wil "restore state", i.e. will read file and set all properties.
Did you try doing this? I'm not 100% certain that setting so many unknown properties (or even just the known ones) at once is safe. The success might depend on the camera's current settings/state.

About abstraction: due to differences between camera generations, these properties should probably be manipulated by separate script functions. For camera-specific use, we could introduce generic functions like set_uiprop() and get_uiprop().


Re: UI properties (PTM functions)
« Reply #28 on: 04 / July / 2015, 02:02:12 »
Did you try doing this? I'm not 100% certain that setting so many unknown properties (or even just the known ones) at once is safe. The success might depend on the camera's current settings/state.

Not for unknown. But I changed almost all properties in camera, then run settings from file that contains all known properties - works good. As second option, we could have some user-friendly interface for investigation.

*

Offline srsa_4c

  • ******
  • 4005
Re: UI properties (PTM functions)
« Reply #29 on: 05 / July / 2015, 19:28:54 »
As second option, we could have some user-friendly interface for investigation.
Do you have a suggestion?

 

Related Topics