Any regrets adding window{PROP:buffer} = 1 after OPEN(window)?

1

Has anyone run into issues after using PROP:Buffer = 1 on a WINDOW structure, and then later had to remove it?

On a system running Windows 10 (build 19045), I’m seeing some strange UI behavior unless I apply PROP:Buffer = 1 after the WINDOW is opened.

Specifically:

  • TABs on a SHEET control don’t paint correctly.
  • Transparent STRING controls placed on top of a BOX also fail to render as expected.

Here’s the odd part:

  • Everything works fine the first time the window is displayed.
  • But if I close and reopen the same window, the rendering glitches appear unless PROP:Buffer = 1 is used.

Has anyone else encountered this or found a different workaround?

2

If it’s a complicated window using a buffer of 1 will make it open slightly slower but not noticeable.

This buffer “draws” the entire window in memory before it displays. It cuts flicker and I use it damn near everywhere… always have.

1 Like
3

I have it on by default.

4

How can i set prop:buffer on all windows to 1 at once. Is it a setting or a template?

5

Thanks for the replies Bruce and Lodestar. I’ve been a bit nervous to turn that on, as we are running this on an RDP server with a dozen or so PC’s remoted in.

Dirk1, my code is using legacy templates. I did not see a template setting. So, I just manually added the line of code into the main browse procedures in my application that have tab SHEETs.