Subclassing

The place for threads about TimoSoft ButtonControls.
Post Reply
TickTick
Lt. Commander
Posts: 54
Joined: 17 Feb 2009, 01:41

Subclassing

Post by TickTick »

What happens if I don't subclass for WM_NOTIFYFORMAT?
I don't see any changes...

From MSDN http://msdn.microsoft.com/en-us/library ... 85%29.aspx:
All common controls will send WM_NOTIFYFORMAT messages. However, the standard Windows controls (edit controls, combo boxes, list boxes, buttons, scroll bars, and static controls) do not.

Thank you.
User avatar
TiKu
Administrator
Administrator
Posts: 832
Joined: 28 Sep 2004, 21:10
Location: Unterföhring
Contact:

Re: Subclassing

Post by TiKu »

In general (not specific to ButtonControls), any features that are based on notification messages, won't support Unicode if you don't do the WM_NOTIFYFORMAT stuff. An example is the ItemGetDisplayInfo event of e. g. ExplorerListView.

The MSDN statement is probably wrong. With comctl32.dll 6.0, the standard Windows controls like Edit, Button, Combo Box... have become part of comctl32.dll (before they were implemented in user32.dll) and now are common controls. New features that are added to these controls, are implemented in common controls style, e. g. WM_NOTIFY is preferred over WM_COMMAND and therefore WM_NOTIFYFORMAT becomes important.
On the other hand, Microsoft usually supports Unicode only nowadays. This means that new messages that would have been implemented in an ANSI and a Unicode version back in the Win2k/Win9x days, now have a Unicode version only. So it might be possible that the button controls send only Unicode notifications anyway and therefore don't need the WM_NOTIFYFORMAT stuff. I'll check that.
Crunching for Fab36_Folding-Division at Folding@Home. Join Fab36/Fab30! - Folding@Home and BOINC
Boycott DRM! Boycott HDCP!
Post Reply