WindowAction fails to maximize Citrix windows

[gdyvig]

The following failed under MacroScheduler v12 and Windows XP:


WindowAction>1,Windows Internet Explorer*

Code: Select all

//visible windows
Let>WF_TYPE=2
//for Citrix key strokes
Let>SK_LEGACY=1
SetFocus>Windows Internet Explorer*
//1st param=1 means maximize window
WindowAction>1,Windows Internet Explorer*

The above code does not maximize the Windows Internet Explorer window when it is a Citrix published application. It does work for WindowAction codes 0, 2, and 3. Code 1 works for non-Citrix windows such as Windows Internet Explorer displayed without Citrix.

I can use an image based or keystroke workaround, but it would be better if WindowAction worked in this case.



Gale

[Marcus Tettmar]

The trouble is Citrix uses hidden windows which contain the windows you see. Citrix obfuscates the real situation and reacts differently - acting as a layer in the middle. So there may not be much we can do about this. WindowAction simply calls the Windows API functions - it's just a wrapper for existing API functions - and if Citrix won't respond as you would expect from the Windows API then ......

[gdyvig]

Hi Marcus,

Thanks for the explanation.

It is strange that the WindowAction command is still able to minimize and restore the window. Perhaps the maximize command was not valid with the hidden window present.

If I were able to find the hidden window, wonder if it would respond to maximize requests.

Anyway, I do have other alternatives.


Thanks,

Gale