This restores pre-3.3 behaviour of not using composition (native double buffering) for all windows and removes many workarounds that are not necessary any more. It wasn't simple to find all such workarounds and I'm not sure if I found all of them, please let me know anything else that could/should be reverted now.
This should fix #25025, #25797 and maybe others I'm forgetting around.
Please test this if you can, TIA!
https://github.com/wxWidgets/wxWidgets/pull/25808
(20 files)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
@vadz pushed 13 commits.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.
I'm just wondering if the wxGrid
control will be affected by these changes. I don't have time to check it myself, as I'm preparing a pull request to add RTL support to the wxQt
port, and also trying to complete #25426.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
At first glance the grid sample seems to work fine, is there anything more concrete you think should be tested in it? I've checked selection, editing, scrolling.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
If I understand correctly, wxMSW behaves more like other ports when this PR is NOT applied. Is that correct? If so, with this PR applied, how should I configure my wxMSW application to go back to the more-portable behavior?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
If I understand correctly, wxMSW behaves more like other ports when this PR is NOT applied. Is that correct? If so, with this PR applied, how should I configure my wxMSW application to go back to the more-portable behavior?
You'll just have to avoid the use of wxClientDC
. Maybe we could add some wxNO_CLIENT_DC
preprocessor symbol that could be predefined by the application to make its declaration inaccessible to them, in order to prevent them from accidentally relying on it working.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
I'm going to merge this soon if there are no other comments.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Merged #25808 into master.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.