Path: utzoo!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!swrinde!mips!cs.uoregon.edu!ns.uoregon.edu!milton!sumax!quick!amc-gw!nwnexus!roper
From: roper@nwnexus.WA.COM (Michael Roper)
Newsgroups: comp.windows.ms
Subject: Re: collecting icons
Message-ID: <476@nwnexus.WA.COM>
Date: 17 Mar 91 20:34:55 GMT
References: <2869@s2.Morgan.COM> <474@nwnexus.WA.COM> <1991Mar15.130928.28094@watserv1.waterloo.edu>
Reply-To: roper@nwnexus.UUCP (Michael Roper)
Organization: hDC Computer Corporation, Redmond WA
Lines: 20

Tom Haapanen writes:

> Strictly speaking, not correct.  Icons can be extracted from .EXEs and
> .DLL using the ViewIcon/GetIcon programs recently posted to c.b.i.p,
> and combined to DLLs using the Windows SDK.  Of course most people
> do not have access to an SDK, but it *is* an alternative.

You're right.  However, if this is something you intend to do on a
regular basis (or even once, depending on how much your time is worth), 
or if you would actually like to modify the libraries you create, 
hDC Icon Designer is clearly superior to the approach you describe.  

Icon Designer can extract hundreds of icons and convert them to a
library in about a minute or less, depending on your hardware.  Even
if GetIcon does not require that you name the .ico's you extract, 
you're still looking at a relatively painful experience using the
"alternative."

Michael Roper
hDC Computer Corporation