• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Open event is not fired for popup! window on RDP (Remote desktop as Service) running application

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (6)

Resolved Open event is not fired for popup! window on RDP (Remote desktop as Service) running application

  1. Issue
0
Votes
Undo
  1. Pierre DETE
    Pierre DETE
  2. PowerBuilder
  3. Monday, 10 June 2024 16:13 PM UTC

Hello,

We have just encountered a popup window opening issue with a client who is using their application compiled with PowerBuilder 2019R2 via Remote Desktop (RDS). The window does not always open, it usually requires two attempts to make it appear.

As a temporary workaround, I noticed that adding a This.Show() at the end of the open event solves the problem. However, I would like to understand what is happening.

The previous solution doesn't work for the complex event management window, so we have to forget about it.

So there's no solution.

 

For the problem of the window not appearing, if I minimize and restore the main window, the popup window appears...

 

 

 

It is not easy to trace this issue as we are obliged to recompile each time to test in the client’s environment…

If you have an explanation that could help me to correct this appropriately, I would appreciate it.

Thank you in advance.

Report is printing the wrong value from the databa...
PowerClient 2022 Application Not Updating
Responses (6)
Pierre DETE
Pierre DETE Accepted Answer Pending Moderation
  1. Thursday, 20 June 2024 17:40 PM UTC
  2. PowerBuilder
  3. # 1

Finally I found a workaround for RDS display : 

I open and close immediately  a small popup in the activate event of the window that is not displayed. This forces it to remain visible... 

I do it with a parameyter activated only for the RDS environment and only for popup! type windows 

Comment
There are no comments made yet.
Pierre DETE
Pierre DETE Accepted Answer Pending Moderation
  1. Wednesday, 12 June 2024 09:15 AM UTC
  2. PowerBuilder
  3. # 2

I can confirm that the problem only occurs with the popup! WindowType.

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Wednesday, 12 June 2024 09:18 AM UTC
Interesting. Maybe you should report it as a bug?

regards.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 12 June 2024 17:58 PM UTC
Hi Roland;

Since PB 2019 R2 was EOMM as of 2022.08.06

Plus, PB 2019 was down in VC++2010, PB 2022 VC++2019 and now PB 2022R3 VC++2022

I would like to suggest that customers try PB 2022 R3 and see if this RDP issue still exists

If so, then I would open a Support ticket for this under PB 2022 R3.

Regards .. Chris
  1. Helpful
There are no comments made yet.
Pierre DETE
Pierre DETE Accepted Answer Pending Moderation
  1. Tuesday, 11 June 2024 08:42 AM UTC
  2. PowerBuilder
  3. # 3

I tried "ACCESSIBILITY" with 0 and 1 and "UseHwnd" set to Yes (which is usually set to No for us). But unfortunately, this doesn't solve the problem.

The solution of such a parameter would be interesting, as they have other strange problems, like freezing... I'd rather not modify the code specifically for them

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 11 June 2024 11:21 AM UTC
No. I'd recommend if you don't have any problems with UseHwnd set to No, then leave it as No.

It was just to explain the setting and in case you had it set to Yes.



BTW: you'd have to distribute such a small PB.INI with the settings to the folder where your EXE is when not running from the IDE, but I supposed you know that.

Sorry I couldn't solve your problem.

regards.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 11 June 2024 08:15 AM UTC
  2. PowerBuilder
  3. # 4

Possible problems of setting  UseHwnd=No:

Yes = use MS-Window handles in DS processing
No = gives much better performance!
(Recommended to set to 'No' ?)
NOTE: Setting the value to 'No' might have an undesired side effect (thank you Benjamin Gaesslein!). "No" will break print functionality for Datastores, specifically, print (true, true) [which is called by pfc_print if you're a PFC user] will no longer show the regular print dialog for Datastores. I've incorporated Benjamin's workaround into the "PFC 2021" https://github.com/OpenSourcePFCLibraries/2021
More info: Proposed solution by Benjamin Gaesslein and MS PDF Printer problem.
Another possible problem has been reported by Simone Olianti of a failing retrieve() using datastores with REST API: https://community.appeon.com/index.php/qna/q-a/need-for-documentation-on-all-existing-pb-ini-entries?limitstart=0#reply-32167
Dean Helsley reports that setting this value to "No", might affect javascript Apache E-charts negatively,. See: https://community.appeon.com/index.php/qna/q-a/e-charts-deployment
Another problem has been reported by BKR Sivaprakash: https://community.appeon.com/index.php/qna/q-a/re-importjsonbykey-fails-on-compiled-project It has to do with using the function "ImportJSONByKey()" when running an executable and having this setting set to 'No'.
Tomaz Kralj reports it changes print behavior: https://community.appeon.com/index.php/qna/q-a/powerbuilder-runtime-behavior-with-dedicated-gpu-performance "If I change UseHwnd=no, I have problems with printing as I get printsetup dialog of current printer and not dialog for selecting printer."

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 11 June 2024 08:14 AM UTC
  2. PowerBuilder
  3. # 5

Hi Pierre,

I'm using these PB.INI settings:

[PB]
UseSimpleMAPI=No

[DataStore Behavior]
UseHwnd=No

[Data Window]
ACCESSIBILITY=0
ForgetColumnKeyboardLayout=Yes

[RichText]
PageSizeAsControlSize=1

 

 

I think it's the Accessibility setting that might improve things.

The UseHwnd=No should speed up your application also, but there's various known possible problems with that one.
See my next answer for an explanation of those.

regards

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 10 June 2024 19:59 PM UTC
  2. PowerBuilder
  3. # 6

Migrate to R3, R2 has lots of problems.

Comment
Load more comments
Pierre DETE
  1. Pierre DETE
  2. Tuesday, 11 June 2024 07:57 AM UTC
Hi Miguel, thank you for your reply. Yes, that may be the reason, but what parameter should I use in the pb.ini?
  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Thursday, 13 June 2024 11:24 AM UTC
We have seen issues in a terminal services environment where the window changes do not render, are you able to see the window in the task bar? and what happens if you move it? Just a random thought, but we have not seen this issue for many years now.



Good luck
  1. Helpful
Pierre DETE
  1. Pierre DETE
  2. Wednesday, 19 June 2024 17:34 PM UTC
For the problem of the window not appearing, if I minimize and restore the main window, the popup window in it appears.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


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