Hi Chris,
Related to this original question, and somewhat solving my problem by changing a few controls to INDICATORS, I ended up doing a few ATTR_DIMMED to disable some controls under certain circumstances.
All was fine in UI land, until tricky user (that would be me trying to crash my own program) decided to go on a tabbing frenzy. It just so happens that when I got to the tab index associated with the DIMMED control, it crashed. I'm thinking because CVI is confused as I made the control HOT and then under a special event, it turns "quasi disabled" by DIMMING it, and when tab index hits it, it freaks out. This is my creative speculation. I get pretty creative at these odd hours.
So, I tried to be even trickier by issuing a few ATTR_CTRL_TAB_POSITIO
N assignments to give a type of circular/recursive tab order such that when the tab counter would hit the "dimmed" control, it would be associated with a new updated TAB order which would point it to a non-dimmed control. Needless to say, it didn't like that either, and crashed again.
So, I ended up with setting the control to a ATTR_NO_EDIT_TEXT which effectively does everything I want, and doesn't disturb the TAB GODS, but doesn't really indicate to the user that the control is inactive as it's not grayed out as I'd like.
I would still like to gray out the control, while keeping the TAB GODS happy. Is this possible or am I doing something overly tricky? 🙂
Thanks in Advance.