Practically, my interest is to know wether I may configure these
settings for other purposes than cosmetic or user interaction, or not.
As matter of fact, one sometimes needs to have controls on the front
panel which are not to be used or even seen by the user. The first
possibility then, is to resize the front panel so that "internal"
controls are not seen at run time.
But when these objects are complex structures including typedefs or wide
graphical elements (I have an example where they occupy like 8 times the
surface of the actual GUI), resizing the front panel sounds a little light.
From what you explained, a wiser technique is to hide the heavy
objects, which will actually relieve GUI processing. On the other hand,
enabling/disabling/gr
eying objects sould only be used for cosmetic purposes.
I guess we got the point so !
Thanks - oz
Greg McKaskle a écrit:
>> Do the "show/hide" and "Enabled state" status of a front panel object
>> affect the way it is handled by the internal GUI management thread ?
>>
>
> I'm not sure what the question is. The short answer is yes. Showing
> and hiding means that the object isn't visible on the panel for viewing
> or interaction. It means that events don't interact with the object and
> no time is spent drawing it. Enabling and disabling mean that the
> object is left visible, and the object processes the low level events,
> but doesn't respond to them. Graying the control means that it draws,
> then the result is blended with the background, which actually takes
> longer to draw than an enabled control.
>
> Greg McKaskle
>
