None of the GC wrappers do anything particularly interesting with clip management. I think in theory this was meant to allow the driver to flatten the clip to a bitmap and/or keep track of a window ID, but the only example I can find of anything remotely like that in open code is Xprint's PostScript backend, which, well.
I've not tested this in any real sense. It would want at least an xts5 run against Xnest and Xvfb before committing. The CopyClip change might want to be a screen func as well for symmetry. Longer term I don't think there's any reason to have GCFuncs at all, and that the whole thing could be embedded in the ScreenRec. Dead code diff: text data bss dec hex filename 1844275 52216 64384 1960875 1debab Xorg-clip-gc 1842034 52120 64384 1958538 1de28a Xorg-clip-screen - ajax _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
