Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!isgate!krafla!aries
From: aries@rhi.hi.is (Mimir Reynisson)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Icons in popup menus (like Std. File dialog)?
Message-ID: <2871@krafla.rhi.hi.is>
Date: 6 Mar 91 13:49:37 GMT
References: <12338@goofy.Apple.COM>
Distribution: comp
Organization: University of Iceland
Lines: 30

I've two things to add to this discussion as I just recently created
a browser similar to SFGetFile. I wanted a pop-up like SFGetFile had
but couldn't find out anything from IM about SICNs. After messing
about in MacsBug for a short while I found that it uses cmdChar $1A.
That way the SICNs are much closer to the left menu border then if
I were to use $1E.

A small picture to explain what I mean:

   -------------    --------------    ------------
  | O MenuItem1 |  |  O MenuItem1 |  |  MenuItem1 |
  | O MenuItem2 |  |  O MenuItem2 |  |  MenuItem2 |
  | O ...etc... |  |  O ...etc... |  |  ...etc... |
   -------------    --------------    ------------
    cmdChar $1A      cmdChar $1E      Normal menu

See what I mean?

Anyway, the second point I'd like to make is: if you're are in doubt
whether some given system supports SICNs in its menus or not, you could
include MDEF0 from a system that does and set its id to something else.
And when you finally land right in the middle of such a situation, you
simply create your pop-menu with your included MDEF. I think there's
a far worse problem with systems that don't support pop-up menus. What
can you do then? Draw it yourself I presume.

However, I havn't a clue as to what Apple might have to say about that.

--MymR
Disclaimer: Who me??