Redefine wxTRANSPARENT_WINDOW as 0 and stop using it
This style never did anything useful in wxMSW and did nothing at all in all the other ports, so always was rather useless, but became actively harmful not that WS_EX_COMPOSITED is used in wxMSW because using it and WS_EX_TRANSPARENT, enabled by wxTRANSPARENT_WINDOW, together doesn't work and results in an endless stream of WM_PAINT messages being sent to the _siblings_ of the window with wxTRANSPARENT_WINDOW style.
This commit is contained in:
parent
a4ebfbb773
commit
20bbc43a20
39 changed files with 19 additions and 46 deletions
|
|
@ -46,6 +46,10 @@ Changes in behaviour not resulting in compilation errors
|
|||
asserts, make sure that wxImageList is created with a valid size before
|
||||
operating on it.
|
||||
|
||||
- wxTRANSPARENT_WINDOW doesn't do anything and shouldn't be used any more. If
|
||||
you ever used it under MSW (it never did anything in the other ports), you
|
||||
can turn on the native WS_EX_TRANSPARENT extended style if really needed.
|
||||
|
||||
|
||||
Changes in behaviour which may result in build errors
|
||||
-----------------------------------------------------
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue