Fred Kiefer wrote: > The gsave/grestore operations are rather expensive. Where possible we > should try to avoid them internally. Even without this there are > different ways we could achive the same results. This is one of the
Of course. It's certainly permissable for the path to just unset/reset the things that were set. > > The GSSendBezierPath: allows for the fast transfer of the coordinates of > a path, what is missing is the fast transfer of the properties of a > path. This would for all but the ps backends set the path to a copy of > the provided path. This can only work if the path parametes are applied > before each drawing action. And this is why I opt for the new drawing > model for all the gsc backends. > Oh. I really put that method in there for NSBezierPath. I think I just misunderstood what you wanted when you talked about it at first. I could easily see changing the semantics of this to replace the current path (attributes and all). That's a very simple operation that easily fits in the DPS and Quartz models. This still would not remove the requirement that NSBezierPath remove any attributes it set (either vie gsave/grestore or some other mechnism). I think that's a separate issue. -- Adam Fedor, Digital Optics Corp. | I'm glad I hate spinach, because http://www.doc.com | if I didn't, I'd eat it, and you | know how I hate the stuff. _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
