Changing back color when connection is lost and reestablished again

[vedadramovic]

Hello,

Our system is distributed and redundant.
UI that is opened on remote client PCs has Navi and main panel. Navi panel has overview of all system in small. Click on navi panel opens desired panel in main panel. This panel contains plenty of references that uses data points from remote system.
If connection is lost to remote system, before panel initialization, objects (elements, references) on this panel will change its background color to _dpdoesnotexist - which is good.

When connection to remote system is reestablished, background color of some elements will change from "thick" (sometimes "plain") to "thin" _dpdoesnotexist.
This "thin" background color _dpdoesnotexist will not change until entire UI is restarted.

"Thin" back color _dpdoesnotexist is caused by background color change inside of initializations of elements/objects that are placed on reference panels.
"Thick" back color _dpdoesnotexist - I do not know what causes this. I think it is caused by reference panels. This behavior is good for me, but it looks worse than on case of "thin" back color..

My questions are:
1. What causes "thick" back color change?
2. is this thick color change reliable enough, so I can remove part that checks for erroneous and incomplete configurations inside of initialization of elements placed on reference panels?
3. Change of a panel inside of main panel will not execute initialization control script of elements that are placed on reference panels. Is there a way to run this initialization control scripts after remote system connection is established?

Thanks in advance,
Vedad

[Gertjan van Schijndel]

When you also connect to the '_bad' attribute your callback function is also triggered when the connection to the remote system is lost or reestablished. In the online help this is documented at the control function 'isAnswer()'.

[vedadramovic]

Hi Gertjan, thank you very much for the help.
When i use dpConnect() to "_bad" it throws an exception, so isAnswer() returns false.
But it seems that when I use isRefresh() that it works nice.

Thanks again