• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [firstPath appendBezierPath: [secondPathbezierPathByReversingPath]];
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [firstPath appendBezierPath: [secondPathbezierPathByReversingPath]];


  • Subject: Re: [firstPath appendBezierPath: [secondPathbezierPathByReversingPath]];
  • From: email@hidden (Tim Ramsey)
  • Date: Fri, 21 May 2004 19:31:28 -0500

Hamish Allan wrote:
>Hi Bob,
>
>On May 21, 2004, at 13:30, Robert Clair wrote:
>
>> But you have to start the process somewhere, that is what moveTo is
>> for. If you
>> try and add a segment without establishing a current point with a
>> moveTo, the beginning point of the segment is undefined and you will
>> get, as you note, an error.
>
>Well, you should not have to start the process somewhere. A closed path
>is the same wherever you start drawing it. When you draw a circle, you
>don't have to choose a 'start' point, do you? What is the problem with
>taking the last point in the path as the point from which the first
>line is drawn?

It seems to me that this distinction is between math and algorithm
design. One could do that, but the designer chose not to. There is
nothing wrong with implementing a bezier method with the function of
adding a point to an existing point as its paradigm. It should make for
a simple, efficient method.
>
>> An open polyline of N segments has N+1 points and the path is created
>> by
>>
>> moveTo: point0, lineTo: point1, lineTo: point2, ..., lineTo: pointN
>
>Ah; from what you previously said:
>
>> 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.
>
>it seemed as though you were referring to "paths with only line
>elements in them" as "open polylines". In answer to your question, I
>can assume that paths with only line elements in them are implicitly
>closed because, as you note, open polylines are not paths with only
>line elements in them. They also have a point element in them.
>
>> I'm sorry, but I am not grasping the cause of your allergy to moveTo.
>
>I have already explained what advantages would be offered by allowing
>lineToPoint without moveToPoint. I have no objection to moveToPoint: as
>you note, it would be impossible to create open polylines without it. I
>am simply suggesting that bezier paths are enhanced in the way I
>describe. You have stated that this would break existing code. Could
>you please give an example of how?

It sounds to me like you are making a case for the addition of an alternate Bezier
generator as an enhancement. Why not file an enhancement request? A new
method would do what you want with no risk of breaking code.
>
>Regards,
>Hamish
>_____________________________
--
Tim

Life consists not in holding good cards but in playing those you hold well.
-Josh Billings, columnist and humorist (1818-1885)
_______________________________________________
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.


  • Follow-Ups:
    • Re: {Spam?} Re: [firstPath appendBezierPath: [secondPathbezierPathByReversingPath]];
      • From: Hamish Allan <email@hidden>
References: 
 >Re: [firstPath appendBezierPath: [secondPath bezierPathByReversingPath]]; (From: Robert Clair <email@hidden>)
 >Re: [firstPath appendBezierPath: [secondPath bezierPathByReversingPath]]; (From: Hamish Allan <email@hidden>)

  • Prev by Date: Re: 'Search field' class yet?
  • Next by Date: Re: NSMakePoint and such - what about memory allocation?
  • Previous by thread: Re: [firstPath appendBezierPath: [secondPath bezierPathByReversingPath]];
  • Next by thread: Re: {Spam?} Re: [firstPath appendBezierPath: [secondPathbezierPathByReversingPath]];
  • Index(es):
    • Date
    • Thread