Re: [NSBezierPath appendBezierPathWithGlyph:inFont:] and current graphics port
Re: [NSBezierPath appendBezierPathWithGlyph:inFont:] and current graphics port
- Subject: Re: [NSBezierPath appendBezierPathWithGlyph:inFont:] and current graphics port
- From: Marco Binder <email@hidden>
- Date: Fri, 2 May 2003 18:33:38 +0200
But then, how come appending any other path beside a glyph works?! What
is the reasoning behind that?
Plus, as I have posted earlier today, append...WithGlyphs:count:inFont:
works without locking focus, but then flips the path? (At least for me)
If this is really a feature, they REALLY should document that!
marco
Am Freitag, 02.05.03 um 18:18 Uhr schrieb Brock Brandenberg:
>
>
> It is nowhere documented that -[NSBezierPath
>
> appendBezierPathWithGlyph:inFont:] does actually append no path to the
>
> receiver if the current NSGraphicsContext has no graphics port. Is it
>
> really the case?
>
>
>
> The only workaround I found so far is to lock the focus on a static
>
> NSImage (not quite efficient, I guess).
>
>
This is indeed the case. It's most likely an undocumented feature
>
rather
>
than a bug since it would make sense that the method would look to the
>
current graphics context for a transform (ctm) to do it's work. BTW,
>
getting
>
a temporary empty NSImage and locking focus on it has worked fine for
>
me too
>
when the work isn't being done inside of drawRect:.
>
--
|\ /| email@hidden
http://www.marco-binder.de
| \/ | Telefon: 07531 / 94 19 94 Fax: 07531 / 94 19 92
| |ARCO Snail-Mail: Banater Str. 3 - 78467 Konstanz
BINDER _____________________________________________________
_______________________________________________
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.