Path: utzoo!censor!geac!torsqnt!jarvis.csri.toronto.edu!mailrus!umich!samsung!think!snorkelwacker!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: Re: XView application without olcursor?
Message-ID: <9003110755.AA20288@Larry.McRCIM.McGill.EDU>
Date: 11 Mar 90 07:55:48 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 17

>>> This is a valid request for change--if the toolkit cannot find the
>>> OpenLook fonts, it loads in bitmap data and uses that instead.  The
>>> only problem we would have with this is increasing the library size.
>>I thought shared libraries eliminated the problems associated with
>>growing a library, at least by small amounts (like this).

> You still increase size to handle two cases for rendering.  A size
> increase is a size increase whether you have shared libraries or not.

Well yes, but a size increase of 2K (say) would likely be tolerable
whereas a size increase of 2K * number-of-XView-binaries probably would
not.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu