| || |
VBFrame showing up as CustomWin
We are seeing a problem where sometimes the first screen in our app - a login screen - comes up containing a CustomWin instead of a VBFrame when invoked through the SilkTest. This occurs about half the time (half the time it comes up as a VBFrame and other times
it comes up as a CustomWin).
The CustomWin has a bunch of the ThunderRT6* goodness in it.
When invoked normally (straight from the DeskTop; no SilkTest) we have never seen the CustomWin.
Is this some kind of timing issue? or do we have something set funny.
Environment: Win2k, Silktest5.5
Re: VBFrame showing up as CustomWin
Sounds like the VB extension is failing to load sometimes, or it is trying to act on the object before the extension can be loaded fully. I've found 2 things that help in this case:
1 - Add sleep statement in the Invoke method for the application so that it pauses right after starting the .exe.
2 - Check to see if the VBFrame exists and if not use the Disconnect function to disconnect from the Agent and then follow it with another Connect function to reconnect to the Agent. I've found that this can cause the Agent to reload the extensions.