Well now I'm reconsidering the change to use save/restore in NSView's
lockFocus. The problem with this is that user objects (such as gstates)
are stored in local VM, and a restore invalidates anything in local VM.
This in fact screws up the xdps backend (not the xgps backend because
xgps is only a weak attempt at implementing DPS).
I could store gstates in some global dictionary, but that would be a
pain to implement.
The only other alternative is to go back to gsave/grestore. Then of
course we couldn't use rectviewclip (since grestore doesn't restore
those) and instead use rectclip. The drawback to this is that a custom
view could potentially (i.e. on purpose) mess with the clip path and
draw all over the window. But I suppose that's the application
developer's problem...
If anyone has any opinions, let me know.
On second though, I suppose a custom view could call rectviewclip and
screw with the window also, so perhaps it doesn't matter anyway...
--
Adam Fedor, Digital Optics | Fudd's law of opposition: Push
[EMAIL PROTECTED] http://www.doc.com | something hard enough, and it
[EMAIL PROTECTED] http://www.gnustep.org | will fall over.
_______________________________________________
Bug-gnustep mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gnustep
