Camera Features Table has two new columns:BPLT : "Bitmap Palette", shows the palette number used in the port.CCOL: "Custom Colors", shows if custom colors are loaded into the camera color palette.
For A3200 it's showing as Palette 16 with custom colors = NO; but platform_camera.h for this camera sets both CHDK_COLOR_BASE and CAM_LOAD_CUSTOM_COLORS?
The legibility of CHDK OSD values can be greatly improved if their background color is a semi-transparent grey. Recent CHDK ports use custom color palette code get twelve custom colors that are guaranteed to be "correct" in shooting and playback modes. What I propose is adding a 13th standardized color - semi-transparent grey - as part of the custom palette color mod. Note that this has already been done on the Powershot N and the SX200 (palette 13). The SX200 takes this a step farther and defines COLOR_ALT_BG and COLOR_BG to use the semi-transparent grey. I don't have that camera but I'll bet it looks great !Adding this and making it standard will be a bit of work. Making the background a standard color also means modifying this : http://chdk.wikia.com/wiki/Lua/Drawings#ColorsAm I missing anything here?
For the CHDK menus I'd argue against it - I tried this for a while on some of my cameras and in the end found it more of a distraction having the image behind showing through the menu.
Another area that might benefit from having semi transparent greys would be the script colors - this could allow scripts to display a UI with some visibility of the image behind.
The problem with adding more custom colors is the risk of overwriting colors the Canon UI is using - palettes 13 and 16 are used by quite a few cameras.
If there are no objections to these changes I'll implement them in the near future.
3. Replace COLOR_SELECTED_FG and COLOR_SELECTED_BG.These are only used for the menu 'cursor' highlight. I think they should simply default to COLOR_GREY_DK and COLOR_WHITE respectively (e.g. the inverse of the normal menu item colors).
Quote from: philmoz on 22 / October / 2014, 04:28:28If there are no objections to these changes I'll implement them in the near future.Works for me - some nice cleanups!What about collapsing all the #define COLOR_ICON_REC_* & #define COLOR_ICON_PLY_* where they are just using the custom palette or "standard" colors. For cameras without custom colors, the ones with explicit hex values for colored icons probably need to stay that way (that can be handled with #ifdefs obviously).Can we move every camera that uses custom palettes into a common palette definintion / number ?
Is this a good time to add #define COLOR_TRANS_GREY .. take the risk of adding to the custom palette and default to COLOR_GREY_LT if not defined there ?
Sounds good.By the way, in the beginning of the CHDK story the background color was defined as a dark semi-transparent color - see palette 1. I think a solid grey is better for the menu background.I wonder why have we extra definitions for the histogram colors?White, black, semi-transparent, transparent and 3 shades of grey, red, green, yellow & blue should be enough for all possibilities.msl
Started by a710is Feature Requests
Started by Novex General Chat
Started by Cortexelus Script Writing
Started by pigeonhill General Discussion and Assistance
Started by koshy « 1 2 3 4 » General Discussion and Assistance
