[stsf] [Bug 425] New: XST local rendering mode should support both rendering via XGetIMage()/XPutImage() and via XPutImage()-only

[bugzilla-daemon at pdx.freedesktop.org]

http://pdx.freedesktop.org/cgi-bin/bugzilla/show_bug.cgi?id=425

           Summary: XST local rendering mode should support both rendering
                    via XGetIMage()/XPutImage() and via XPutImage()-only
           Product: STSF
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XST: X Client Library
        AssignedTo: stsf at freedesktop.org
        ReportedBy: roland.mainz at nrubsig.org
                CC: adg at sun.com


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).



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.