Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!male!contract3.EBay.Sun.COM!slemons
From: slemons@contract3.EBay.Sun.COM (Steve Lemons)
Newsgroups: comp.windows.ms
Subject: Icons ...
Keywords: icon
Message-ID: <4238@male.EBay.Sun.COM>
Date: 18 Dec 90 04:21:03 GMT
Sender: news@male.EBay.Sun.COM
Reply-To: slemons@contract3.EBay.Sun.COM (Steve Lemons)
Organization: Sun microsystems
Lines: 29


So - you've downloaded an icon editor, created some icons for Program Manager
that are more to your liking, and you've told Program Manager to use the new icons. Now, what to do with all those icons that you've created?

It doesn't matter!!

In another slight-of-hand trick, Windows has grabbed a copy of the icon 
bitmap and stored it in the associated .GRP file, along with the path that
you specified for the alternate icon file. From this point on, the icon
displayed in Program Manager is read from the Program Group (*.GRP) file.

This appears to be the procedure in all cases. If the Program Item contains
an icon - and you don't tell Program Manager to use a different one - the 
icon is extracted from the program and stored in the .GRP file. This appears 
to be true even with standard Windows Program Items such as Notepad, Control 
Panel, and File Mangler.

Since Program Manager keeps it's own copies of icons, there is no need to 
keep icon files on your hard disk. And that's a good thing, since an icon
file of 800 bytes is taking up at least 2048 byes of hard disk space. Save
a few of those, and you are wasting a lot of disk space.

You do need to keep a copy of the icon files on a floppy though, in case 
Program Manager 'forgets' the icon image and needs to be refreshed.


-----------------------------------------------------------------------------
"We'll burn that bridge when we get to it..." Mrs. Mondegreen
-----------------------------------------------------------------------------