Bug 425 - XST local rendering mode should support both rendering via XGetIMage()/XPutImage() and via XPutImage()-only
Summary: XST local rendering mode should support both rendering via XGetIMage()/XPutIm...
Status: RESOLVED WONTFIX
Alias: None
Product: STSF
Classification: Unclassified
Component: XST: X Client Library (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: STSF mailinglist
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-07 19:10 UTC by Roland Mainz
Modified: 2008-01-22 17:39 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Roland Mainz 2004-04-07 19:10:36 UTC 
The XST client library's "local" rendering mode should support both rendering
via XGetIMage()/XPutImage() and via XPutImage()-only.

Three reasons why there should be a 2nd "local" rendering mode:
1. XGetImage()/XPutImage() requires a round-trip to the Xserver - which is bad
for performance
2. On higher resolutions (like 200DPI or higher) AA for fonts may not be wanted
anymore
3. Read
http://xprint.mozdev.org/docs/Xprint_FAQ.html#why_does_xgetimage_not_work - the
PostScript and PCL DDX do not support XGetImage()

For [3] I suggest to make a call to |XpGetContext| - if that returns anything
else than |None|(="0") then [3] should be used (since Xprint printing is being
used).
Comment 1 Alexander Gelfenbain 2004-04-12 19:34:33 UTC 
Jay, please take a look at it.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.