Hi Guys,

thank's for the info, that worked like a charm.

Thanks again,

Peter

oleg wrote: As workaround  you can add Toolkit project to solution, rebuild your application, and remove it again (if you want).

I actually always add the XTP to the solution, because it then allows me to get Intellisense working as well, plus I might want to do some weird optimizations

As workaround  you can add Toolkit project to solution, rebuild your application, and remove it again (if you want).

thanks for clarifying that ICBM

yes in vc6 its possible.

just started using vc2003 past month or so.

  thanks Microsoft

This is 'normal' behaviour for Visual Studio. As soon as you change the base class to something that is not part of standard MFC, various useful functions are disabled including adding command handlers.

I believe it used to be possible (with VC6) to make some changes to a config file to add your own classes, but it's been a long time...

Anyhoo, this is not a fault of the codejock libraries.

Addendum:

just noticed, that every extreme sample program also exhibits the same problem with the mainframe class, in which you can't access/add to the class.

if change public CXTPMDIFrameWnd back to public MDIFrameWnd, the class overrides and messages are accessible again.

is their something wrong with my installation or files ??

thanks, any help appreciated

Peter

Hi all,

strange problem...i think.

just created a new project (vc2003/w2kpro) using the xtreme toolkit with basic options. When i goto add a menu event handler to my cmainframe class, it won't let me, every other class allows the event to be created..

then i created a stand mfc project with no xtreme template, and tried to add a menu event to the cmainframe and it allowed me to !!

is it just me still asleep or just stupid, any suggestions greatly appreciated.

Thanks

Peter