why is WM_SIZE handled before WM_DISPLAYCHANGE when the monitor's scale factor or resolution or position is changed?

  • Thread starter Thread starter mtjj_19
  • Start date Start date
M

mtjj_19

Guest
Hello everyone, in my application, when the monitor's scale factor or resolution or position is changed, the message WM_DISPLAYCHANGE is generated, and the message can be handled with the macro MESSAGE_HANDLER. However, there is also a function deals with the message WM_SIZE, and this message is always handled before WM_DISPLAYCHANGE, why? And is there a way to handle WM_DISPLAYCHANGE first?

Continue reading...
 

Similar threads

P
Why, in a Win32 application in C ++, when the window is resized, the progress bar creeps to the side.
Replies
0
Views
195
Purple_Apple
P
P
In a Win32 C ++ application, every time a PBM_STEPIT message is received, the progress bar changes from 0 to the maximum value, but does not increment
Replies
0
Views
205
Purple_Apple
P
P
When drawing a Bitmap created in the background thread instead of the picture in the window, a black background is obtained.
Replies
0
Views
152
Purple_Apple
P
V
Memory dumps for hang or performance issues, "automated" approach
Replies
0
Views
249
Viorel-Alexandru
V
C
There’s something so strange about this COVID-19 risk factor, and scientists are baffled
Replies
0
Views
98
Chris Smith
C
Back
Top