The problem is that of course, you don't know that in general, so it's a
potentially difficult-to-find bug that could happen anywhere in your
code. For example, I now have a button that's just above a view with
complex drawing, so the border of the button overlaps with that view and
causes it t
If you don't need to do secondary-thread drawing in your view, you
don't have to. You can check which thread is sending the -drawRect
method. Allow the subviews such as the aqua button to draw themselves,
and skip over any thread-unsafe custom -drawRect stuff in your
superview.
The only thing you
Before your post, I knew that some AppKit drawing was done in
secondary threads, but it never occurred to me that this could cause
one's own NSView subclasses to be drawn in a separate thread, too.
Presumably, if one's custom drawRect: method can be called in a
separate thread due to a pulsing NSB
Hi,
Another question... I've noticed that Aqua animations, for example the
pulsing default button, are implemented via a separate thread, which
redraws the button repeatedly. This also causes the view (for example a
custom view that I wrote myself) that contains the button to receive a
drawRe
