ON_UPDATE_COMMAND_UI Prob using SetCheck

Hi,

currently I'm trying to get a pressed button in my toolbars using the "normal" ON_UPDATE_COMMAND_UI mechanism. However, it seems as all handlers are called for checking only, i.e. with a CTextCmdUI object. For this class a SetCheck is (silently) ignored....

Using the XTP FAQ Chapter 5 does not help either, because pCmdUI->m_pOther == 0

Any help where to look at?

Ciao,
    Andreas

Hi Oleg,

ok, now I tried different things using two different buttons: an ID_EDIT_UNDO (MFC predefined ID 0xe12b) button and an ID_OWN (32771) button.

The ID_EDIT_UNDO button has its handler in my CDocument derived class and is working as expected, e.g I used pCmd->SetCheck and pCmd->Enable.

For my ID_OWN button I once tried a handler in my CDocument derived class and once in my CView derived class (only one active at a time). Inside the handler I tried once with SetCheck, once with SetPressed (a'la FAQ chapter 5).

This button is working as expected if it is contained in my first toolbar and even the second toolbar. If it was contained my third toolbar (I'm using three toolbars) it only got enabled/disabled, but no longer checked. The ID_EDIT_UNDO button was working in all three toolbars.

You noticed the change from present to past? I'm not quite sure what happened on testing for this reply, but somehow now it is working. The handler is currently in my CView derived class. Hopefully it keeps on working.

Ciao,
    Andreas

oleg wrote: Please use SetCheck instead SetPressed. The last is internal method. Recommended to use identifiers from 130 to 9000 range to avoid conflicts with MFC values and XTreme resources.

We have 9600 resource how are we supposed to avoid conflicts?

we are using resources from 101  to 9600 inclusive..

Could you add an offset base to your resources so we can shift them away from our range?

P.S.: our resource range can not be shifted due to technical specs.