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

Resolved Problems with screen “flickering”

  1. Issue
0
Votes
Undo
  1. Sylvain .
    Sylvain .
  2. PowerBuilder
  3. Wednesday, 18 May 2022 12:34 PM UTC

In many of our windows mainly those with a lot of visual objects and tabs, each time the window resize or a tab change within the window,  the system after executing all of our lines of code just and before releasing control to the user, some of the window control begin to ‘flicker’ and sometimes for many seconds. For example I can see the text on each tab flicker like if something was click on each tab one after the other very quickly.

During those seconds the windows is inaccessible, I tried to debug this by asking for a PBDebug ASCII file with no result. In that file there is no line of code that would explain the flickering for many seconds, I can only see our code.

I know that my current description is not very helpful but is there anyone who has had a similar problem or any suggestion on what I could look at.

I’m using PB CloudPro Version 2019 R3 build 2703 (but I had that problem since PB 2017).

Thank you in advance for your help, it is always appreciated.

URGENT: Richt Text Edit Control
PBAutoBuild errorlevel
Who is viewing this page
Ashley Lamplugh
Responses (4)
Sylvain .
Sylvain . Accepted Answer Pending Moderation
  1. Wednesday, 18 May 2022 18:14 PM UTC
  2. PowerBuilder
  3. # 1

Hi Chris,

Thank you for your response,

I already have something similar, but the problem is not when the window open but when everything is done and the user for example resize its screen or simply go to another tab within the window.

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 18 May 2022 19:28 PM UTC
Then the culprit could be on the LoseFocus, Deactivate, Resize, SelectionChanged (Tab Ctrl) etc events that might be causing this. However if you can create a small simple test case PB App that reflects these issues - then I would open a Support Ticket & attach the test case for Appeon to study further.

BTW: Does your App use the PFC framework?
  1. Helpful
Sylvain .
  1. Sylvain .
  2. Wednesday, 18 May 2022 19:42 PM UTC
I do not use PFC, I also in this context do not use lostFocus or Deactivate. But if your thinking some kind of recursive problem with Resize and selectionChanged, I did a full trace and a PBDebug, I think it would have shown in one of those...

Again thanks Chris for your help.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 18 May 2022 18:00 PM UTC
  2. PowerBuilder
  3. # 2

Hi Sylvain;

   FYI: I do not have this issue but here is what I do in my framework over all - for all Windows & controls to allow "smooth" painting of any Windows during the OPEN processing, as follows:

1) The Window class base ancestor has the "Visible" property OFF
2) The Window class base ancestor has an "oe_PostOpen" user event "Posted" from the Open event (no other code) .
3) All Ancestor controls have a "oe_PostConstructor" user event "Posted" from the Constructor event (no other code) .
4) In the "oe_PostOpen" event of the Ancestor Window class is where I set the "Visible" property ON
5) In the "oe_PostConstructor" event of any Control is where recommend that your App places all the initialization logic (typically at the "concrete" level).

  Using the above approach, I do not get any flickering on ANY Controls or the parent window itself.  I have been doing it this way since PB version 4-5 with no such problems cropping up. Just my $0.02 for a permanent "fix" for now and the future of newer versions of PBVM and MS-Windows O/S as they can affect the visual presentation opening sequences (ie timing of events, behaviours & internal code execution, etc do change). Your PowerScript needs to counteract these PBVM & O/S changes over time. Your App needs to make sure that all controls, window & menu resources are only visible & initialized after all objects are fully instantiated (trust me - been there done that over many PBVM & O/S releases over the past decades).  ;-)

HTH
Regards ... Chris

Comment
There are no comments made yet.
Sylvain .
Sylvain . Accepted Answer Pending Moderation
  1. Wednesday, 18 May 2022 13:47 PM UTC
  2. PowerBuilder
  3. # 3

Thank you for your answer,

I just tried this and sorry to say it did not fix the problem...

Any other suggestion...

Comment
There are no comments made yet.
Andreas Mykonios
Andreas Mykonios Accepted Answer Pending Moderation
  1. Wednesday, 18 May 2022 13:07 PM UTC
  2. PowerBuilder
  3. # 4

Hi Sylvain.

Is accessibility enabled or disabled in your application (do you have pb.ini with Accessibility key in the same folder where your application resides)?

If not, try to create a pb.ini with the following content:

[Data Window]
Accessibility=0

Let us know if you see any difference. This is mainly related to PB 2019 R3+...

Andreas.

Comment
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.