Skip navigation.
 
mlRe: NSView out of memory problem
FROM : Andre Schnoor
DATE : Wed Apr 02 10:51:37 2008

Am 02.04.2008 um 01:05 schrieb Graham Cox:
> As I said, it says nothing about how it's implemented. Chances are, 
> it will avoid creation of an unnecessary NSBezierPath object, but 
> relying on that being the case is folly.
>
>
> On 2 Apr 2008, at 2:23 am, Matthew Whillock wrote:

>> The class reference has this to say about it:
>>
>> Strokes a line between two points using the current stroke color 
>> and the default drawing attributes.
>> + (void)strokeLineFromPoint:(NSPoint)point1 toPoint:(NSPoint)point2
>>
>>
>> So it will just draw a line.
>>
>> Cheers,
>> Matt
>>
>>

>>> Are you sure? This could be just a convenient interface for 
>>> creating a
>>> bezier object with the points passed, stroking it and releasing or
>>> autoreleasing it. The docs say nothing about how it's implemented.

>>



I've done a FPS benchmark recently and can confirm it is significantly 
faster. This indicates it is implemented in a more efficient way.

Andre

Related mailsAuthorDate
mlNSView out of memory problem Leslie Smith Apr 1, 14:40
mlRe: NSView out of memory problem Matt Gough Apr 1, 14:50
mlRe: NSView out of memory problem Jean-Daniel Dupas Apr 1, 15:09
mlRe: NSView out of memory problem Graham Cox Apr 1, 15:17
mlRe: NSView out of memory problem Matthew Whillock Apr 1, 15:18
mlRe: NSView out of memory problem Graham Cox Apr 1, 15:36
mlRe: NSView out of memory problem Gorazd Krosl Apr 1, 15:43
mlRe: NSView out of memory problem Jean-Daniel Dupas Apr 1, 15:57
mlRe: NSView out of memory problem Matthew Whillock Apr 1, 17:23
mlRe: NSView out of memory problem Andre Schnoor Apr 1, 17:27
mlRe: NSView out of memory problem Graham Cox Apr 2, 01:05
mlRe: NSView out of memory problem Matthew Whillock Apr 2, 09:45
mlRe: NSView out of memory problem Andre Schnoor Apr 2, 10:51