Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!nrl-cmf!ukma!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!asente
From: asente@decwrl.dec.com (Paul Asente)
Newsgroups: comp.windows.x
Subject: Re: special server mechanism (deemed unnecessary)
Message-ID: <976@bacchus.dec.com>
Date: 9 Dec 88 19:32:41 GMT
References: <8812091659.AA02967@devnull.sun.com>
Organization: DEC Western Software Lab
Lines: 15

>No-one should ever do anything with the default font.  The only reason it
>exists is to prevent there being a "No-font-selected" error.

The toolkit needs some sort of default font for resource conversions.
Part of the toolkit philosophy is that for any resource type there is some
value that is guaranteed to work.  Currently to support this with fonts,
it resorts to the totally unreliable expedient of using "fixed" as the
default font.

This could be provided by either expanding the protocol to allow a
GContext anyplace it allows a Font (as it does in XQueryFont), or having
some special resource ID to refer to the default font, as someone else
suggested.

	-paul asente
	    asente@decwrl.dec.com	decwrl!asente