On my cameras it is enabled because using AEL and AFL also set the 'canon_shoot_menu_active' flag causing the CHDK OSD to disappear unless CAM_SHOW_OSD_IN_SHOOT_MENU is defined.
This used to be the case on those old cameras too, looks like this has not changed (the a3200 port doesn't define CAM_SHOW_OSD_IN_SHOOT_MENU and the OSD indeed disappears when AFL is active).
If we could move this sort of thing out from gui_osd.c:
(canon_menu_active!=(int)&canon_menu_active-4) || canon_shoot_menu_active!=0to a function that can be overridden in the port, that could offer a solution to WW's problem (I think).
Or, if palette based detection proves to be useful in a larger group of cameras, we could enable it from platform_camera.h...?
I still don't think that completely disabling OSD (including in ALT mode) or disallowing ALT mode when a Canon menu is active is a good idea.
Ok, with everything going on here I'm not sure if everybody understands the problem correctly. So I'll just try to restate it more clearly.
The ALT mode works correctly imo. One wouldn't enable ALT mode if it wasn't needed at the time. It is and should be on top of other menus.
The problem is solely with the OSD elements that provide extra info when shooting. When pressing the shutter halfway the CHDK OSD disappears as it probably should and the camera displays extra shooting parameters. When entering the menu settings with the menu button the CHDK OSD also disappears. When pressing the FUNC/SET button or any of the other settings buttons including the frame button it doesn't however and remains as an overlay over the camera OSD.
The settings menu isn't a true menu and more of an impromptu OSD display. I don't know how CHDK picks up on when to switch off the OSD but it seems to be missing the signal when one of these OSD's are present.
@ Prom : I'm not really certain that this thread answered your question or if it is actually even addressed your question. But one thing we failed to mention is that you can disable individual parts of the CHDK OSD completely if you desired. You can also use the CHDK OSD editor to reposition things that are displayed to where they will be least "in the way".
I'm not sure it did either but in the mean time this is what I did. Only the elements I really need are displayed rather compact and out of the way. It's still annoying but I can make everything out at least.
