Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!sun-barr!newstop!sun!satori!dmc
From: dmc%satori@Sun.COM (Doug Cook)
Newsgroups: comp.windows.x
Subject: Re: Pixrects in XView
Message-ID: <124730@sun.Eng.Sun.COM>
Date: 14 Sep 89 22:07:23 GMT
References: <887@skye.ed.ac.uk>
Sender: news@sun.Eng.Sun.COM
Reply-To: dmc@sun.UUCP (Doug Cook)
Organization: Sun Microsystems, Mountain View
Lines: 32

In article <887@skye.ed.ac.uk> richard@aiai.UUCP (Richard Tobin) writes:
>I'm having some problems with code which uses pixrects.  XView defines
>memory pixrects, but makes almost all operations on them invalid.  Why
>is this?  The conversion manual clearly implies they still work.  Will
>it work to use the operations from the sunview pixrect library? (I'd
>try it, but I have to fix innumerable other problems before I can tell
>whether it works...)

XView itself does not support operations on memory pixrects, though you 
can use the Sun pixrect library in conjunction with XView. However, this
construct is not portable, since only Suns have the pixrect library.
If you're concerned with portability, I would suggest using server
images instead of memory pixrects.

>How does XView differ from View2?  Or is it just another name for it?

You got it. View2 was an early name for the XView toolkit.

>Why are all the page numbers in the manuals wrong?

The documents were written using Frame, which apparently 
resolves page numbers properly when the document is printed as 
a book. However, we dumped the documents to separate PostScript files, 
so that the page numbers weren't calculated properly. Our group's tech 
writer is currently working on fixing this. We'll post properly
numbered docs soon. Sorry for any hassle this may have caused.

	-Doug

Doug Cook		(dmc@sun.com)	
Software Engineer, XView Group		This space intentionally left blank.
Sun Microsystems, Inc.