I did some cleaning up and fixing of some of the menu operation.The zoom in/zoom out button could be used to alter the step size for MENUITEM_INT items.The zoom in/out could also be held to control step size for both MENUITEM_INT and MENUITEM_ENUM items, but this was in conflict with the above operation, so I removed and modified.zoom in/zoom out increases/decreases the step size: 1,10,100,1000,10000 for MENUITEM_INT, 1,3,9,27,81 for MENUITEM_ENUM.I also extended the DISPLAY usage to all cameras. Now it alters the step size as per zoom out for both and recycles back to 1 at the top, so this can be used for cams without zoom button (I figured it may as well also extend to cams with zoom as well).The step values are saved, so they don't reset back to 1 when moving around in the menu.I also found the display of the step size at the top was inconsistent. it wouldn't clear itself when moving from item to item even though it had been changed. There were also some other display issues with it. Now it displays permanently and displays the stem to reflect the menuitem type (int or enum, for others it is blank).The half-shoot was also used to be held for step size alteration. I modified it so it is a toggle (for all cams) that alters the step size by a factor of 1 or 2. it also updates the step size display above to reflect this change.There were some other minor cleanup issues I did as well.Please have a look at it and see if it is acceptable to be commited or if some alterations may be required. *EDIT*1. Slight error in the patch, I had one line from another item I was working on that would make it not work.2. Made another addition to the menu operation. On the MISC tab there is now an item to select "Jogdial action". You can choose "KEY_U/D" (default) which is the previous operation, jogdial moves up/down menu items. Or you can select "KEY_L/R" and the jogdial will change values like the LEFT/RIGHT KEY operation. This have been enclosed with "#if CAM_HAS_JOGDIAL" so it's only included on cams with jogdials. State is also saved to config file.
Some comments on the patchDISP on cameras with a zoom lever takes you back a menu level, and unless I'm missing something, your patch breaks this. What's left only deals with user menu editing. I assume using DISP to change the increment was a hack for cams without a zoom lever, there really isn't a need for 2 different shortcuts. If there are cams that have a jogdial but not a zoom lever, we could use that to do step size (since it's function is currently redundant). Note also that some cameras don't have a DISP button (not sure if any lack both zoom lever and DISP)
The whole increment thing is a bit confused in the original, it looks like a couple different shortcut systems were merged without much thought about how they interact or whether they were all needed. For enums, this was just cosmetic since the int_incr wasn't applied to them. (edit: svn blame gives some insight into the history)I'm not sure saving the increment value between menu items is desirable. If you are adjusting multiple different fields in a single menu (which seems like the most common case to me), it's not likely to be helpful. Remembering it per menu item might be slightly useful, but I doubt it's worth the overhead.
If I understand correctly, the increment value being displayed after you switched to a new item was just a screen update issue. This should be fixed, since it is definitely confusing.
With the adjustable increment, are the half press shortcuts really needed ? The current zoom shortcut with enum also seems redundant with the half press shortcut (it does go to 6 instead of 3, but there's very few enums large enough to warrant that).
If you are going save the incr values for both ints and enums, I suggest two different variables, int_incr and enum_incr.
Is the jogdial alternate action useful enough to merit a conf entry ? I'm happy to add it if is, but otherwise I'd rather avoid the proliferation of redundant shortcuts. I don't have a jogdial camera right now, so I don't really know.
Before committing this, the DISP issue has to be resolved at a minimum, but I'd also like to get some feedback on how people think the shortcuts should work, and make them as simple and consistent as possible.
Started by eelliott General Help and Assistance on using CHDK stable releases
Started by brainwash « 1 2 » Feature Requests
Started by atalwar General Discussion and Assistance
Started by dmitrys « 1 2 3 4 » General Discussion and Assistance
Started by shinnen Script Writing
