How do you use the standard edit menu in CW?
If there were a text-based resource language,
I could just add it in ... but since the darned
thing is GUI I can't figure out how add a menu
with a given ID # (like 10000) to the menu bar.
Side issue: if you accidentally delete the
title of the menu while you are working on
the menu bar, you can no longer select that
menu to remove it, or change it's title again.
The inspectors wouldn't let me get at the name
unless you could select it. The property inspector
for menu would let me get at the resource id
and the resource name -- but the resource name
is -not- the resource title! If the title is
gone it's impossible to select it again to
get it's inspector up!
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
> -----Original Message-----
> From: Danny Epstein [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 19, 1999 4:06 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Question about Standard Menus
>
>
> At 1:40 PM -0800 11/17/99, Ken Krugler wrote:
> >If the command ids of the standard edit items matches what's
> defined in UIResources.h (file name from the 3.5 SDK), then
> the system will automatically handle these commands for you.
> The defined set is:
> >
> >#define sysEditMenuUndoCmd 10000
> ><snip>
>
> In Palm OS 3.5, choosing Undo from the command bar generates
> a menuEvent with ID 10000, even if your application includes
> its own Edit menu resource with an ID other than 10000. This
> is another reason to use the standard Edit menu rather than
> rolling your own. If you need custom behavior, you can always
> handle the menuEvents yourself and set handled=true if you
> want to prevent FrmDispatchEvent from processing the events.
> For example, the ToDo List application handles the paste
> menuEvent, creating a new record before allowing the
> menuEvent to be processed by FrmDispatchEvent.
>
> I would recommend that the 3.5 documentation stress the need
> for applications to use the standard Edit menu (10000) in
> their menu bar resources. The tutorial should be changed to
> use the standard Edit menu as well. I would also recommend
> that developers switch to using the standard Edit menu if
> they're not already doing so, to ensure compatibility with
> Palm OS 3.5.
>
> I have two questions:
>
> 1. The source for the PIM apps provided with the 3.0 SDK
> include Edit menu resources with IDs different than 10000,
> and yet their menuEvent handlers look for the standard Edit
> menu item IDs (10000, etc). Anyone know what's going on here?
>
> 2. What are the rules for using the standard Edit menu? Can
> we add our own items on the end? If we do so, are we risking
> compatibility problems with future versions of the OS or with
> the Japanese versions?
> -
> Danny Epstein, Applied Thought Corporation
> Have friends with Palm organizers? Get BeamBooks!
> http://www.appliedthought.com/beambooks
>
