| || |
Silk not recognizing ActiveX ctrl if it starts app
If Silk starts up my VB application, then it fails to recognize a major control in the application. There is help that addresses this EXACT issue, but I followed the instructions to no avail. It told me to set AxextDelay=<n> (where n is the number of seconds it takes to start the application). I did that, I even bumped it up to something ridiculous like 10 minutes, still no dice.
If I stop and restart agent, silk sees the control fine. If I start the application myself, silk sees the control fine.
Any other ideas? We have so many problems with our ActiveX controls that I need to be able to restart the application smoothly to work around the other issues.
Re: Silk not recognizing ActiveX ctrl if it starts app
OK, we have a combination of problems here. Problem worked around, though!
First, the basic problem: when silk starts the application there's a frame involved that is not involved when I invoke the app manually for some reason. This was revealed by recording window declarations under the different start-up circumstances.
The first work-around idea was to use multitag to identify the window - easy - but because of the extra frame we had to use a shorthand that included the parent frame in the case where silk started the app - however there appears to be a bug in silk that was preventing that syntax from working.
The second idea was to create a global in the frame file and use Exists to see which frame it was and set the global before that control is used - that more or less worked for us.