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

Resolved Response! window only opening on primary monitor

  1. Issue
0
Votes
Undo
  1. John Raghanti
    John Raghanti
  2. PowerBuilder
  3. Wednesday, 4 November 2020 20:53 PM UTC

Hi. Since moving to PB 2019 from PB 12.5.2, our customers with multiple monitors are reporting seeing some issues.

Notably, they are running our MDI application on the secondary monitor, but certain windows such as response! windows are only opening on their primary monitor.

When I run the application compiled under 12.5.2, the response! windows appear on whichever monitor our application is running on.

It is frustrating for the client who doesn't realize our window appeared on the other monitor and is sitting there waiting for something to happen.

Has anyone seen this or is there any way for us to resolve it?

Here is an example call to open the window:

OpenWithParm (w_Search, lstr_PassedVars, lw_frame)

Thanks!

Run-time crash PB 2019 R2 build 2353 with 64 bits ...
Demo applications for tutorial
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 4 November 2020 21:23 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi John;

   That is strange as this issue has been an ongoing problem for PB Apps for over a decade now. I solved this issue way back when (can't remember - say PB 10.x time frame) in my STD Framework. Basically, the response windows look for an MDI parent  window and center themselves on it based on its location vs the response window's default 1st monitor. The same issue is also for Popup Window types as well that can live outside of their MDI parent.

   My framework addresses this in the Open Event of the Response / Popup window by ...

  • Determining which monitor the MDI frame is currently located on.
  • Centering the window class on the MDI frame.
  • The framework also does the same approach for PowerServer Web Apps as well. However, it uses the Browser's working window as the MDI anchor - thus resolving the window's appearance on the correct monitor where the Browser is running.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Responses (1)


There are replies in this question but you are not allowed to view the replies from this question.