🚀 go-pugleaf

Juan Diego Garc�s wrote:
> Is not an excuse, Our application is really a set of 5 
 > programs that have to work together: There is an
 > applic. that makes the communication with the PLCs,
 > another one that shows the synoptique images to control
 > the station, another one that is the boss of others...
> 
> Then, when the user want to send a command to the PLC, 
 > he has to click the object that he wants (in the
 > synoptique applic.) and the boss application has to
 > show a window where the user can set the new value.
 > Then this new window has to be brought in front.
 > This is a short and quick explanation of what we make.
> 

There is an API function named AllowSetForgroundWindow()
that the foreground process can call to give permission
to another process to call SetForegroundWindow(). If you
have control of all of the programs involved, you might
be able to make use of that function, but such permission
only applies to one process at a time and only lasts until
the calling function receives some input.

Another loophole that may or may not be useful to you is
that a process can set the foreground window if was started
by the current foreground window. If you could arrange for
one application to spawn the others, they may be able force
their way in front.

By the way, I'm only speculating on things I've read. I have
no practical experience except for modifying the registry.