I ran the Activating a Window program and found that it goes in an endless loop, where one of the three states it can switch to will be selected, however none of the close buttons on the message boxes function and the only way I was able to end the program was by use of the Task Manage. I have tried a variety of solutions, but none are worthy. I also notice that even when I use my mouse to react to the message boxes, the message that comes up can be This window has been activated, without the mouse.
This seems pretty dysfunctional in terms of a tool to switch between window, since a method should be possible by which to deactivate and close all the windows shown.
we are developing a simple testing tool for GUI testing using AutomationElement (AE). We want extend it to support VB controls also.
But we can not VB control information using AE. I want use .Net remoting to VB control information. Is it possible?
It is only the VS tool Intellisense that produces the red lines. Intellisense is not as clever as the compiler, so it may have trouble identifying some symbols. This is less of an issue in newer versions of VS (you didn't say which version you have), but it can still happen in code that requires multiple passes to interpret, e. g. code involving #define macros and/or templates.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)