> I think Update and Search Bars could be updated in the
> DisableInterface call... Geoff and Jason, what do you think?
> Otherwise, the list of UpdateBar and SearchBar objects would
> have to be retrieved and write app code to call Enable=False on

them.

The simplest way to include the bars in the existing disable interface
would be to change the bars to use TIB_ControlDataLink instead of
TIB_DataLink. I suspect this will not be directly practical because
ControlDataLink expects the control to be something that can be
focused and has color attributes etc.

The Enable/Disable interface calls work by detecting datalinks based
on TIB_ControlDataLink as an indicator that the link is for a visual
control. What I would suggest (for best long term flexibility) would
be to insert another layout in the datalink heirarchy.

TIB_DataLink
TIB_InterfaceDataLink
TIB_ControlDataLink
<etc>


TIB_InterfaceDataLink - would probably do almost nothing over
TIB_DataLink (it may take some of the control attribute details out of
TIB_ControlDataLink and place it in the lower layer). It would
primarily be there to allow datalinks to be distinguished as interface
versus mechanical.

We update the bars (and any similar interface) to use
TIB_InterfaceDataLink and then Enable/Disable interface to work off
TIB_InterfaceDataLink rather than TIB_ControlDataLink.

BTW. This would directly help me with some of my base-form code.
Since at the moment these are also receiving notifications when
disableinterface is used.

Jason, how does this sound?

Geoff Worboys
Telesis Computing