C / C++ / MFC

ON_NOTIFY_RANGE

If you need to process the same WM_NOTIFY message for a set of controls, you can use ON_NOTIFY_RANGE rather than ON_NOTIFY. For instance, you may have a set of buttons for which you want to perform the same action for a certain notification message.

When you use ON_NOTIFY_RANGE, you specify a contiguous range of child identifiers for which to handle the notification message by specifying the beginning and ending child identifiers of the range.

ClassWizard does not handle ON_NOTIFY_RANGE; to use it, you need to edit your message map yourself.

The message-map entry and function prototype for ON_NOTIFY_RANGE are as follows:

ON_NOTIFY_RANGE( wNotifyCode, id, idLast, memberFxn )

where the italicized parameters are replaced with:

wNotifyCode

The code for the notification message to be handled, such as LVN_KEYDOWN.

id

The first identifier in the contiguous range of identifiers.

idLast

The last identifier in the contiguous range of identifiers.

memberFxn

The member function to be called when this notification is sent.

Your member function must be declared with the following prototype:

afx_msg void memberFxn( UINT id, NMHDR * pNotifyStruct, LRESULT * result );

where the italicized parameters are:

id

The child identifier of the control that sent the notification.

pNotifyStruct

A pointer to the notification structure, as described above.

result

A pointer to the result code you'll set before you return.

ON_CONTROL_RANGE(EN_KILLFOCUS,IDC_EDIT1, IDC_EDIT10, OnKillFocus )<br />
//in the message map<br />
 virtual void OnKillFocus (CWnd *pWwd);// in the header 

Sarvan AL wrote:

I am getting the "sharing access violation" error

_Russell_ wrote:

OUTSIDE

Have a nice code day