menuID conflict with Page Setup dialog

[brucecoughlin]

I'm having a problem with a conflict of menuID's in my app.
I have a font menu which is a hierarchical menu for one of my app's menus.
This font menu has menuID 100.

When I call Page Setup from the File menu, the standard OS X Page Setup box
comes up. If I choose anything from the "Format For" popup in Page Setup my
appEventHandler gets called. The event class is kEventClassCommand and the
menuID is 100... the same as my hierarchical font menu! So my app calls the
function which would be called if the font menu had been picked and a new
item selected from the menu and the font changes.

I'm not sure why this conflict is taking place... It's almost like a
GetPort/SetPort type of problem.. though with menuIDs.

Thanks for any insight.

MachO CW8 C compiler

[Tom Dowdy]

In article <BB8D6D83.41E6%brucecoughlin@nyc.rr.com>,
brucecoughlin <brucecoughlin@nyc.rr.com> wrote:

> I'm having a problem with a conflict of menuID's in my app.
> I have a font menu which is a hierarchical menu for one of my app's menus.
> This font menu has menuID 100.

Application resources (including menu IDs) are allocated the range of
positive short integers greater or equal to 128.

I recommend renumbering your resources.

[Miro Jurisic]

In article <dowdy-89F616.03233317092003@news.apple.com>,
Tom Dowdy <dowdy@apple.com> wrote:

> In article <BB8D6D83.41E6%brucecoughlin@nyc.rr.com>,
> brucecoughlin <brucecoughlin@nyc.rr.com> wrote:
>

> > I'm having a problem with a conflict of menuID's in my app.
> > I have a font menu which is a hierarchical menu for one of my app's menus.
> > This font menu has menuID 100.

>
> Application resources (including menu IDs) are allocated the range of
> positive short integers greater or equal to 128.
>
> I recommend renumbering your resources.

Menu IDs are not resources.

meeroh

--
If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>

[David Phillip Oster]

In article <macdev-FD71D7.10292217092003@senator-bedfellow.mit.edu>,
Miro Jurisic <macdev@meeroh.org> wrote:

> In article <dowdy-89F616.03233317092003@news.apple.com>,
> Tom Dowdy <dowdy@apple.com> wrote:
>

> > In article <BB8D6D83.41E6%brucecoughlin@nyc.rr.com>,
> > brucecoughlin <brucecoughlin@nyc.rr.com> wrote:
> >

> > > I'm having a problem with a conflict of menuID's in my app.
> > > I have a font menu which is a hierarchical menu for one of my app's menus.
> > > This font menu has menuID 100.

> >
> > Application resources (including menu IDs) are allocated the range of
> > positive short integers greater or equal to 128.
> >
> > I recommend renumbering your resources.

>
> Menu IDs are not resources.
>
> meeroh

MenuIDs must match their resource ids in 68K & Classic. Where was this
changed in Carbon?

[brucecoughlin]

That's odd. Toolbox Essentials:
"The menu ID of a submenu of an application must be from 1 through 235"
Did this change in OS X

The real mystery to me is why my appEventHandler is receiving
kEventClassCommand events when I choose an item in a popup menu in Page
Setup dialog... Is this normal behavior?

>
> Application resources (including menu IDs) are allocated the range of
> positive short integers greater or equal to 128.
>
> I recommend renumbering your resources.

[Miro Jurisic]

In article <oster-C55E20.08110617092003@newssvr14-ext.news.prodigy.com>,
David Phillip Oster <oster@ieee.org> wrote:

> MenuIDs must match their resource ids in 68K & Classic. Where was this
> changed in Carbon?

No, they don't. Where does it say they do?

meeroh

--
If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>

[Tom Dowdy]

In article <macdev-D2F8BD.12001117092003@senator-bedfellow.mit.edu>,
Miro Jurisic <macdev@meeroh.org> wrote:

> In article <oster-C55E20.08110617092003@newssvr14-ext.news.prodigy.com>,
> David Phillip Oster <oster@ieee.org> wrote:
>

> > MenuIDs must match their resource ids in 68K & Classic. Where was this
> > changed in Carbon?

>
> No, they don't.

Yes, they do/did -- at least sometimes. The two cases I personally know
about are some early systems for heirarchical menus, and most (all?)
Classic systems for non-code installed popup menus (ie, those popups
where you place the "menuID" in the CNTL resource).

> Where does it say they do?

IM explicitly says that while it is convention to make them the same,
there isn't a requirement to do so. In the above two cases, however, it
is incorrect.

The OP cited another incorrect older IM statement, in which he thought
he had to keep sub-menus between 0 and 255. This is no longer the case
as of, gee, probably System 6 or so.

I keep all of my menuIDs at 128 or higher because there certainly used
to be menu IDs floating around the system in the low positive number
range (0-10). In more modern times, system software I've been involved
in has tried to keep in the negative range only.

-- Tom

[Miro Jurisic]

In article <dowdy-A0FEB9.09415317092003@news.apple.com>,
Tom Dowdy <dowdy@apple.com> wrote:

> In article <macdev-D2F8BD.12001117092003@senator-bedfellow.mit.edu>,
> Miro Jurisic <macdev@meeroh.org> wrote:
>

> > In article <oster-C55E20.08110617092003@newssvr14-ext.news.prodigy.com>,
> > David Phillip Oster <oster@ieee.org> wrote:
> >

> > > MenuIDs must match their resource ids in 68K & Classic. Where was this
> > > changed in Carbon?

> >
> > No, they don't.

>
> Yes, they do/did -- at least sometimes. The two cases I personally know
> about are some early systems for heirarchical menus, and most (all?)
> Classic systems for non-code installed popup menus (ie, those popups
> where you place the "menuID" in the CNTL resource).
>

> > Where does it say they do?

>
> IM explicitly says that while it is convention to make them the same,
> there isn't a requirement to do so. In the above two cases, however, it
> is incorrect.
>
> The OP cited another incorrect older IM statement, in which he thought
> he had to keep sub-menus between 0 and 255. This is no longer the case
> as of, gee, probably System 6 or so.
>
> I keep all of my menuIDs at 128 or higher because there certainly used
> to be menu IDs floating around the system in the low positive number
> range (0-10). In more modern times, system software I've been involved
> in has tried to keep in the negative range only.

Tech-note! Tech-note! Tech-note!

meeroh

--
If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>

[David Phillip Oster]

In article <macdev-D2F8BD.12001117092003@senator-bedfellow.mit.edu>,
Miro Jurisic <macdev@meeroh.org> wrote:

> In article <oster-C55E20.08110617092003@newssvr14-ext.news.prodigy.com>,
> David Phillip Oster <oster@ieee.org> wrote:
>

> > MenuIDs must match their resource ids in 68K & Classic. Where was this
> > changed in Carbon?

>
> No, they don't. Where does it say they do?

If you do a groups.google.com search for

"menu id" resource

you'll find numerous threads from the '90s of programmers reporting
problems because their resource ids don't match their menuIDs. One
reason they have problems is that GetNewMBar() uses resource ids, while,
I imagine, MenuSelect() uses MenuIDs. Certainly, keeping them in synch
was part of the lore of Macintosh programming since I started
programming them, in 1984. Before posting this, I checked that
Resorcerer, Constructor, and (I believe) ResEdit all change the menuID
for you when you change the resource id, so their authors must have
thought the two had to match.