Forum Discussion
soda
14 years agoContributor
It seems that this problem is mainly occuring when we use WaitNamedChild().exists in an If statment. It is a problem beyond just dialogs.
If we add the Sys.Refresh() before the if(object.WaitNamedChild("name", 0).exists statement, things work fine.
We would rather not go through the code adding Sys.Refresh() all over when they have not been needed in previous versions of TC.
Is there a global preference in TC9 we are not setting or something to cause object refreshes automatically?
Thanks,
Mark
If we add the Sys.Refresh() before the if(object.WaitNamedChild("name", 0).exists statement, things work fine.
We would rather not go through the code adding Sys.Refresh() all over when they have not been needed in previous versions of TC.
Is there a global preference in TC9 we are not setting or something to cause object refreshes automatically?
Thanks,
Mark