Hi Tanya,
In fact the behavior is due to another modification in the code:
I've changed a Process["VCLObject"] instruction for a Process["WaitVCLObject"], as I didn't want to get the error message if the window is not present, in order to populate some variables first.
As this occurs few instructions after launching the application (I first wait that the process exists but no more), it seems this difference between both methods
"A call to any
WaitXXXObject method causes the
object tree to refresh"
is responsible of what I observe. If I introduce a break point or a 3 seconds delay just before calling the WaitVCLObject method, I get the TConfigControler0 name.
I will see to find a way to wait for the window in a manner that allows me to retrieve the previous version, as additionnaly to name changes, I observe also that the tree is different with some object that are not present in the tree.
Thanks for help,
Christophe
