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

**URL:** <https://clarionhub.com/t/any-regrets-adding-window-prop-buffer-1-after-open-window/8370>\
**Category:** uncategorized\
**Tags:** windows\
**Created:** [July 11, 2025, 12:04am UTC](https://clarionhub.com/t/any-regrets-adding-window-prop-buffer-1-after-open-window/8370 "2025-07-11T00:04:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![RichCPT](https://clarionhub.com/letter_avatar_proxy/v4/letter/r/e19b73/32.png) [@RichCPT](https://clarionhub.com/u/RichCPT)\
**Post date:** [July 11, 2025, 12:04am UTC](https://clarionhub.com/t/any-regrets-adding-window-prop-buffer-1-after-open-window/8370/1 "2025-07-11T00:04:18Z")

</div>

**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?

---

<div class="post-metadata">

**Author:** ![lodestar](https://clarionhub.com/user_avatar/clarionhub.com/lodestar/32/1055_2.png) [@lodestar](https://clarionhub.com/u/lodestar)\
**Post date:** [July 11, 2025, 5:39pm UTC](https://clarionhub.com/t/any-regrets-adding-window-prop-buffer-1-after-open-window/8370/2 "2025-07-11T17:39:45Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Bruce](https://clarionhub.com/letter_avatar_proxy/v4/letter/b/ccd318/32.png) [@Bruce](https://clarionhub.com/u/Bruce)\
**Post date:** [July 12, 2025, 12:36am UTC](https://clarionhub.com/t/any-regrets-adding-window-prop-buffer-1-after-open-window/8370/3 "2025-07-12T00:36:02Z")

</div>

I have it on by default.

---

<div class="post-metadata">

**Author:** ![Dirk1](https://clarionhub.com/letter_avatar_proxy/v4/letter/d/977dab/32.png) [@Dirk1](https://clarionhub.com/u/Dirk1)\
**Post date:** [July 13, 2025, 11:52am UTC](https://clarionhub.com/t/any-regrets-adding-window-prop-buffer-1-after-open-window/8370/4 "2025-07-13T11:52:48Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![RichCPT](https://clarionhub.com/letter_avatar_proxy/v4/letter/r/e19b73/32.png) [@RichCPT](https://clarionhub.com/u/RichCPT)\
**Post date:** [July 14, 2025, 6:32pm UTC](https://clarionhub.com/t/any-regrets-adding-window-prop-buffer-1-after-open-window/8370/5 "2025-07-14T18:32:05Z")

</div>

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.
