Response window focus difficulties in Terminal Server
Hello.
I’m trying to deal with a problem I suspect has to do with MS Terminal Server. I read this post:
http://www.tokeshi.com/modules.php?op=modload&name=News&file=article&sid=2005
It spoke about Citrix and I wonder if the following problem sounds the same to you:
If you run any application through a Citrix client or a Terminal Services Client where the scenario is as follows:
You open a response window, say window_A. From the response window A you open a second response window, say window_B. The only thing is, there is a delay of about 10 seconds before window B actually opens. While you are waiting for window B to open, you minimize the session’s client to do something on you own desktop. Once you return to the session, you find that window_B has indeed opened but doesn’t have the focus. Instead, window_A has the focus.
Depending on the language the application is written in, in my case PowerBuilder, you will, in most cases, run into the problem of not being able to change the focus to window_B since window A is a response window and won’t let you leave it.
If you think your can help, kindly let me know what I can do. The solution I'm looking for should not drastically change my current PB6.5 application is there are may response windows and to retest the entire up is not an option with this project.
mailto:epitchon@shaw.ca
May thanks for your time.
Erez Pitchon.
I’m trying to deal with a problem I suspect has to do with MS Terminal Server. I read this post:
http://www.tokeshi.com/modules.php?op=modload&name=News&file=article&sid=2005
It spoke about Citrix and I wonder if the following problem sounds the same to you:
If you run any application through a Citrix client or a Terminal Services Client where the scenario is as follows:
You open a response window, say window_A. From the response window A you open a second response window, say window_B. The only thing is, there is a delay of about 10 seconds before window B actually opens. While you are waiting for window B to open, you minimize the session’s client to do something on you own desktop. Once you return to the session, you find that window_B has indeed opened but doesn’t have the focus. Instead, window_A has the focus.
Depending on the language the application is written in, in my case PowerBuilder, you will, in most cases, run into the problem of not being able to change the focus to window_B since window A is a response window and won’t let you leave it.
If you think your can help, kindly let me know what I can do. The solution I'm looking for should not drastically change my current PB6.5 application is there are may response windows and to retest the entire up is not an option with this project.
mailto:epitchon@shaw.ca
May thanks for your time.
Erez Pitchon.
ASKER
Yes, this happens only if I minimize the Citrix or Terminal client (problem happens in both). I don't think the problem is specific to PowerBuilder though. I created a macro in Excel that opens a FORM_B from FORM_A with a pause before FORM_B opens. If you minimize the session before FORM_B opens, when you return, FORM_A has the focus and FORM_B does not. I did try SetFocus explicitly, but to no avail.
Erez.
Erez.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
can u update me abt a query...does ur window B get the focus if u don't minimise ur session client.??... as u must be aware that citrix only passes across snapshots and keystrokes.... so what i feel is when the response returns to the citrix client after u call the open window B the problem arises coz it is minimised...
try explicitly calling setfocus to an object on window B and let me know if it works fine if ur session client is not minimised,,,,
on a normal application it works fine if u open a response window from another response window.. the second window gets the focus....
Cheers,
Rosh