Path: utzoo!utgpu!water!watmath!clyde!att!alberta!ubc-cs!uw-beaver!cornell!mailrus!husc6!sunfs3!geoff From: geoff@sunfs3.camex.uucp (Geoffrey Knauth) Newsgroups: comp.sys.mac.programmer Subject: Re: Help setting application's icon Message-ID: <152@sunfs3.camex.uucp> Date: 22 Aug 88 13:46:52 GMT References: <77900005@peterson> Reply-To: geoff@sunfs3.UUCP (Geoffrey Knauth) Organization: Camex, Inc., Boston, Mass USA Lines: 100 Newsgroups: comp.sys.mac.programmer Subject: background compilation Summary: Expires: References: <418@metasoft.UUCP> <5125@husc6.harvard.edu> Sender: Reply-To: geoff@sunfs3.UUCP (Geoffrey Knauth) Followup-To: Distribution: usa Organization: Camex, Inc., Boston, Mass USA Keywords: In article <5125@husc6.harvard.edu> singer@endor.UUCP (Rich Siegel) writes: >In article <418@metasoft.UUCP> alan@metasoft.UUCP (Alan Epstein) writes: >>what i'd really like to know is whether compilations can occur >>in the BACKGROUND. anyone know? > > No, and there's no good reason for them to do so. Backgroun >compilation is such a CPU-intensive task that it would slow down all of >the foreground tasks, and the foreground tasks will slow down compilation, >particularly if they don't give sufficient time via correct use of >WaitNextEvent. I would prefer to have the option of compiling in the background. Although I don't do it that often, Unix has never said there was "no good reason" for me to compile in the background. On occasion I've needed this ability, and someday Mac developers will need it too. Newsgroups: comp.sys.mac.programmer Subject: Re: LSC 3.0 Summary: Expires: References: <418@metasoft.UUCP> <5125@husc6.harvard.edu> Sender: Reply-To: geoff@sunfs3.UUCP (Geoffrey Knauth) Followup-To: Distribution: Organization: Camex, Inc., Boston, Mass USA Keywords: In article <5125@husc6.harvard.edu> singer@endor.UUCP (Rich Siegel) writes: >In article <418@metasoft.UUCP> alan@metasoft.UUCP (Alan Epstein) writes: >>there are some hidden menus in THINK C pertaining to Multifinder >>awareness. they don't seem to be activate-able in any way i >>can figure out. > > The only such menu that I know of is the menu for setting the >flags in the project's SIZE resource; this menu is accessible from the >Project Type dialog. > >>what i'd really like to know is whether compilations can occur >>in the BACKGROUND. anyone know? > > No, and there's no good reason for them to do so. Backgroun >compilation is such a CPU-intensive task that it would slow down all of >the foreground tasks, and the foreground tasks will slow down compilation, >particularly if they don't give sufficient time via correct use of >WaitNextEvent. > > --Rich > >Rich Siegel >Quality Assurance Technician >THINK Technologies Division, Symantec Corp. >Internet: singer@endor.harvard.edu >UUCP: ..harvard!endor!singer >Phone: (617) 275-4800 x305 Newsgroups: comp.sys.mac.programmer Subject: Re: Help setting application's icon Summary: Expires: References: <77900005@peterson> Sender: Reply-To: geoff@sunfs3.UUCP (Geoffrey Knauth) Followup-To: Distribution: usa Organization: Camex, Inc., Boston, Mass USA Keywords: In article <77900005@peterson> peterson@peterson.applicon.UUCP writes: > >I am trying to make my own icon for an application that I wrote. >I know how to do this (with MPW & Rez, etc.), but there seems to be >a problem with "installing" it. The first time I built the application >with the correct signature, etc, the icon came up on the screen nicely. > >Unfortunately, I want to modify this icon. It seems that the mac system >(maybe the Desktop file) is refusing to forget the original icon, and >no matter what I set it to, the original is still used. I am using >system software 6.0 - is this a bug? Or am I not doing something??? I recently tried a program ("BindIcon" ?) from one of my Boston Computer Society or Berkeley Macintosh Users' Group disks. It worked quite nicely, and described in its documentation how it avoids some of the nastiness you've encountered. -- Geoffrey S. Knauth CAMEX, 75 Kneeland St., Boston, MA 02111, 617/426-3577 geoff@sunfs3.uucp I do not speak for Camex.