home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!lsl!snail
- From: snail@lsl.co.uk
- Newsgroups: comp.windows.x.intrinsics
- Subject: Re: --- BadFont X-Error when opening HP -display ---
- Message-ID: <1993Jan25.172012.2978@lsl.co.uk>
- Date: 25 Jan 93 17:20:12 GMT
- References: <KDH.93Jan23174109@nimrud.ira.uka.de>
- Organization: Laser-Scan Ltd., Cambridge
- Lines: 30
-
- In article <KDH.93Jan23174109@nimrud.ira.uka.de>, kdh@nimrud.ira.uka.de (Klaus Hartenstein) writes:
- >
- > Hi,
- >
- > the small test-program at the bottom produces the following
- > X-Error, when the other display is on a HP:
- >
- > X Error of failed request: BadFont (invalid Font parameter)
- > Major opcode of failed request: 55 (X_CreateGC)
- > Resource id in failed request: 0x2800001
- > Serial number of failed request: 11
- > Current serial number in output stream: 29
-
- Well, I'm not sure what's going on. Could it be that your fontList resource for
- your program is specified using wildcards and the font found using this
- method on the HP server has a pixel height of zero? This means it is scalable.
- We found that when this happens, running say, from a DECstation to a HP it
- all bombs out. I can't remember if ours died as above or with a seg. fault.
- I think this causes problems if the XLib in the application is a lower
- revision that the server, and cannot handle fonts of height zero. Just a guess,
- I don't have source code access - no room for on line, I wish!
-
- Worth a thought though.
- --
- snail@lsl.co.uk
-
- "Washing one's hands of the conflict between the powerful and the powerless
- means to side with the powerful, not to be Neutral."
- Quote by Freire.
- Poster by OXFAM.
-