Undocumented Win2000/XP message 0x128
-
Our subclassed CButtons are receiving Windows message 0x128 (296) when tabbing out of certain controls in the same dialog tab. This causes the button to draw over (or leave unpainted?) the art we want to see. In our case, the caption on the button has the standard gray button background, which we don't want. The bad drawing only occurs once in the life of the dialog. Covering/reexposing the bad areas causes them to redraw correctly. If we return 0 from message 0x128 (not passing it to CButton), the problem disappears. This occurs only on Windows 2000 and XP. Does anyone know what undocumented Windows message 0x128 (296) is supposed to do? -- Phil Davidson phil@phildavidson.com
-
Our subclassed CButtons are receiving Windows message 0x128 (296) when tabbing out of certain controls in the same dialog tab. This causes the button to draw over (or leave unpainted?) the art we want to see. In our case, the caption on the button has the standard gray button background, which we don't want. The bad drawing only occurs once in the life of the dialog. Covering/reexposing the bad areas causes them to redraw correctly. If we return 0 from message 0x128 (not passing it to CButton), the problem disappears. This occurs only on Windows 2000 and XP. Does anyone know what undocumented Windows message 0x128 (296) is supposed to do? -- Phil Davidson phil@phildavidson.com
The answer: This message 0x128 is WM_UPDATEUISTATE, which is documented in the MSDN library. I would have found this if I had inspected WINUSER.H from a recent version of the Platform SDK. Thanks to Usenet correspondents for this information. -- Phil