Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!apple!lsr
From: lsr@Apple.com (Larry Rosenstein)
Newsgroups: comp.sys.mac.programmer
Subject: Re: C++ programming under MPW - advice sought
Message-ID: <11497@goofy.Apple.COM>
Date: 12 Dec 90 00:03:24 GMT
References: <1082@exua.exeter.ac.uk> <47268@apple.Apple.COM>
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 21

In article <47268@apple.Apple.COM>, ksand@Apple.COM (Kent Sandvik) writes:
> 
> In article <1082@exua.exeter.ac.uk> kt@msor.msor (Keith Tizzard) writes:
> >In the following member function why do we have:  ?
> >
> >EnableItem(menu, iNew);      instead of  menu->EnableItem(iNew)           
> >DisableItem(menu, iClose);   instead of  menu->DisableItem(iClose);
> >                                                   
> >menu = GetMHandle(mFile);    instead of  menu = mFile->GetMHandle();
> 
> Some parts of the MacApp framework are not so object oriented, there

Note that the examples that Keith was using were from the MPW C++ examples,
and not MacApp.  

MacApp doesn't provide menu/menubar objects either, but it does take care 
of more of the details (e.g., you normally don't have to know about 
GetMHandle).  You specify the menus in your resource file, and MacApp takes
care of reading them in properly.

Larry Rosenstein