1. Ivan Aase
  2. PowerBuilder
  3. Monday, 21 January 2019
Hi,

We run pb 2017 r2 in a distributed RDP solution so that pb runs as one
window on local machine.
The problem is that a user starts other processes on a local machine
and then returns to the rdp process.

In this case, sometimes PB does not give focus to users,
so users have to stop everything and start over to move on.
Is there anyone who has thoughts for solving this?

 

Who is viewing this page
Ivan Aase Accepted Answer Pending Moderation
0
Votes
Undo

Hi Chris,

I'm not sure if I've managed to express our problem properly.


What we are struggling with is that we have a Powerbuilder process that one has published on RDP,
and when then starts other processes (ex. Word, excel ..) on the machine that this pb prosess is published on
it is often one cannot manage to get back focus on the powerbuilder application again.
Although one clicks on the icon on the process line, the focus stays on oen of the others.

One had to minimize all other processes for the powerbuilder process to become active again.

So it seems that powerbuilder fail to become the active process without everyone else being minimized.

You suggest getfocus () and setfocus (), but I am unsure I have explained too poorly and that you may have understood me so that it is the powerbuilder process that starts the rdp process and not that it is the published rdp process.

If it turns out that I am wrong and that you have not misunderstood me, then I am still unsure where to enter Getfocus and Setfocus.

 

best regards

Ivan.

Comment
Hi Ivan;

Yes, RDT (formerly "terminal Services") by MS is not officially supported by Appeon PB. Most Apps will work OK but do experience odd things like you describe, focus issues and lack of mouse wheel scrolling (jut to name a few). I am not sure what else to advise you here to escape your RDT issue.

Maybe other RDT users can "chime in" here if they have developed any "workarounds" or have tips / insights when using RDT.

Regards ... Chris
  1. Chris Pollach
  2. Tuesday, 12 February 2019


Hi Chris,



Thank you so much for your informational responses. I think my solution now has to be in dialogue with operation. We must look at opportunities to change the use of the system. Thus, we must consider how we can get away from the RDP (MS-Terminal) service using the Powerbuilde application.



I also think to leave the thread open a little longer in the hope that there may be someone out there who has been in the same problem and managed to create a solution that works.



best regards

Ivan.
  1. Ivan Aase
  2. Wednesday, 13 February 2019
There are no comments made yet.
  1. Tuesday, 12 February 2019
  2. PowerBuilder
  3. # 1
Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Ivan;

   Yes, RDT can have these quirks for sure. Sometimes you just need to enhance your code a bit to make sure that you always do a GetFocus( ) before the external process starts and and then a SetFocus() on the return to PB  to get around this type of issue that RDT introduces.

   If the spawned local process is involuntary from your PB App and focus does not return afterwards ... please build a simple test App that replicates that issue. Then, open a support ticket for this problem and attached your test case App. That will allow Appeon Engineering to work on this lack of RDT compliance if possible.

Regards ... Chris

 

Comment
How will I do that in an MDI App that could have opened many different windows.

Where are you think I had to do a GetFokus () on leaving and a SetFocus() when returning ?



regards Ivan.
  1. Ivan Aase
  2. Wednesday, 23 January 2019
There are no comments made yet.
  1. Tuesday, 22 January 2019
  2. PowerBuilder
  3. # 2
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.