Path: utzoo!attcan!uunet!bu.edu!snorkelwacker!apple!vsi1!hsv3!jls From: jls@hsv3.UUCP (James Seidman) Newsgroups: comp.windows.ms Subject: Re: icons for non-Windows 3.0 applications Message-ID: <5059@hsv3.UUCP> Date: 1 Oct 90 16:28:29 GMT References: <6669@ul.ie> <4707@hsv3.UUCP> <1990Sep29.184653.4693@cs.uoregon.edu> Reply-To: jls@headland.UUCP (James Seidman) Organization: Video Seven / Headland Technology Lines: 17 In article <1990Sep29.184653.4693@cs.uoregon.edu> akm@cs.uoregon.edu (Anant Kartik Mithal) writes: >What would happen if you used the resource compiler to link in an icon >to a dos executable? Well, this *might* let you access the icon from the Properties... menu of the Program Manager (I haven't tried) but it still wouldn't give you that icon when you minimize the program. Each windows program needs to designate a "class icon" for its window to let the system know what it should look like when you minimize it. (That's not quite true, as the program can draw its icon itself, as clock does, but it's approximately true.) Now, a non-Windows app is not going to know about the resource you linked in, so it's definitely not going to tell Windows that it's the class icon. (Nice thought, though...) -- Jim Seidman (Drax), the accidental engineer. UUCP: ames!vsi1!headland!jls ARPA: jls%headland.UUCP@ames.nasa.arc.gov