Due to the nature of these IDs (camera model dependency), new CHDK features building upon PTM functions will be enabled only for tested models These features are the kind of things I was thinking about when I suggested pushing this off to be part of 1.4.0
There aren't any such features planned at the moment.
What the patch does is:
- identifies a few functions that will be useful later
- determines the UI property count
- adds debug facilities that help future research
I'm not pushing this, if its impact feels too big, it will be added after 1.4.
Here's a poor howto on usage:
Miscellaneous stuff -> Debug parameters -> ALT +/- debug action -> [CmpUIPr]
The UI properties will be sampled when the "debug shortcut" button is pressed in ALT mode.
The debug shortcut is usually one of the following buttons:
- "erase" (if it's not one of the directional buttons)
- DISP (if there is a separate DISP button)
- a button which is not a directional button, not SET, not MENU; for example the video (aka movie) button
In some cases there is no button assigned for this.
From the second sampling on, differences to the previous sample will be listed on screen.
This listing may conflict with CHDK on-screen elements, you may want to switch those off.
If you're hunting a specific setting: make sure you only change the desired setting.
For example, the vertical cursor position in the shooting menu has its own ID, but it is obviously not much of interest.
The IDs and values will be printed in decimal.
If somebody wants to use the IDs with the PTM_SetCurrentItem eventproc:
Add 0x8000 to the ID (you need to convert the decimal ID to hex). Only 2 exception is the ixus30 and 40 which use native IDs starting from 0.