Re: [firstPath appendBezierPath: [secondPath bezierPathByReversingPath]];
Re: [firstPath appendBezierPath: [secondPath bezierPathByReversingPath]];
- Subject: Re: [firstPath appendBezierPath: [secondPath bezierPathByReversingPath]];
- From: Hamish Allan <email@hidden>
- Date: Fri, 21 May 2004 05:17:00 +0100
On May 20, 2004, at 14:10, Robert Clair wrote:
Can you (or anyone else) think of any negative outcomes, before I file
a bug report myself?
How about "It would break lots of existing applications." ? ... for a
start
Could you please elaborate? I believe I am suggesting allowing
NSBezierPaths to allow for adding elements in a way which is currently
not permitted, so any existing applications could not contain such
NSBezierPaths.
Currently, as you know, an NSBezier won't let you add a line until
you've added an initial point (I don't know about other curves, I
haven't tried them). Relaxing this restriction (by assuming that the
point from which the line is drawn is the final point in the path,
i.e., paths with only line elements in them are implicitly closed)
would have at least three positive outcomes:
And a rather large negative one - how can you assume
"paths with only line elements in them are implicitly closed" ???
Open polylines are not an unknown or unused item.
I have found that if I try lineToPoint: on an NSBezierPath without
having first called moveToPoint: I get a runtime error. How do I obtain
these open polylines?
Best wishes,
Hamish
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.