Revised observations:

Make ICON 1000: app shows BW icon
Make cicn 1000: app shows BW icon
Delete ICON 1000: app shows multibit icon
Make ICON 1000: app shows multibit icon

It may be that it doesn't have a preference, but merely
takes the first ICON -or- cicn w/ the proper ID.  Therefore
the order they appear in the application makes a difference.

If somebody can confirm this, I would appreciate it -- I've
got a headache right now and may have slipped up in the
procedure.

If this -is- confirmed, I would suggest that this "first
available" behavior is not proper, and that the cicn should
be taken if present, and the ICON if not.

-- 
-Richard M. Hartman
[EMAIL PROTECTED]

186,000 mi./sec ... not just a good idea, it's the LAW!


> -----Original Message-----
> From: Richard Hartman 
> Sent: Monday, December 06, 1999 5:13 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: small icon problem
> 
> 
> -Replaced- ?? 
> 
> But the older machines don't recognize the cicn resource,
> right?  We need the ICON resource for those systems ... which
> brings me to the bug:  If you have BOTH a cicn (new) and 
> ICON (old) w/ the proper id # (1000), the ICON resource will
> be displayed!  Shouldn't the newer systems take the cicn in
> preference to the ICON?  
> 
> This is true at least on OS 3.0, and (I think) OS 3.3.  (Haven't
> checked 3.5 yet.)
> 
> -- 
> -Richard M. Hartman
> [EMAIL PROTECTED]
> 
> 186,000 mi./sec ... not just a good idea, it's the LAW!
> 
> 
> > -----Original Message-----
> > From: Eric Cloninger [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, December 06, 1999 9:24 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: small icon problem
> > 
> > 
> > Yes.  The old ICON format (b/w only) should be replaced by 
> > 'cicn' (color
> > icon).  The color icon editor has a space for b/w versions of 
> > the icon as
> > well as the color versions.  The Constructor UI isn't very 
> > obvious, but use
> > color icons going forward.
> > 
> > -E
> > 
> > > -----Original Message-----
> > > From: Richard Hartman [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, December 06, 1999 11:13 AM
> > > To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
> > > Subject: RE: small icon problem
> > >
> > >
> > > You're saying the main program icon should now also
> > > be a multibit icon, not a regular icon?
> > >
> > > btw: I defined my mini app icon as a multibit icon
> > > w/ an id of #1001 and it works fine in the list view,
> > > but the one thing you didn't mention is that the
> > > multibit icon resource is larger than the area you
> > > can use for the mini icon.  The mini icon is only
> > > the top/left portion of the full resource,  15 across
> > > by 9 down.  Anything outside that area will not be
> > > seen.
> > >
> > >
> > > --
> > > -Richard M. Hartman
> > > [EMAIL PROTECTED]
> > >
> > > 186,000 mi./sec ... not just a good idea, it's the LAW!
> > >
> > >
> > > > -----Original Message-----
> > > > From: Tim Hewitt [mailto:[EMAIL PROTECTED]]
> > > > Sent: Saturday, December 04, 1999 10:10 AM
> > > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > > > Subject: Re: small icon problem
> > > >
> > > >
> > > > Gary Spinelli wrote:
> > > > >
> > > > > I haven't been successful getting my application's small
> > > > icon to appear in
> > > > > list view.  I've followed the instructions to the letter as
> > > > documented in
> > > > > the Knowledge base article 1457.  But the app's icon is
> > > > replaced by some
> > > > > system diamond default.  I'm using CodeWarrior R5 with the
> > > > latest upgrade
> > > > > applied under NT.
> > > >
> > > > I figured this out after about an hour of bashing my head
> > > > into the wall.
> > > >
> > > > You need to define your icons as Multibit icons, as opposed
> > > > to regular icons in
> > > > Constructor (I'm using CWL R6). The main program icon is
> > > > #1000. The small icon
> > > > is #1001. They are cicn resources, and can be multi-color
> > > > (which is only grey on
> > > > my system) as well as black and white. I defined both flavors
> > > > in the editor -
> > > > since my application is bound to be used on a color 
> device soon...
> > > >
> > > > -Tim
> > > >
> > > > --
> > > > Tim Hewitt
> > > > Principal Software Engineer
> > > > Fairchild Semiconductor
> > > >
> > >
> > 
> > 
> 

Reply via email to