Update of bug #14759 (project gnustep):
Status: None => Invalid
_______________________________________________________
Follow-up Comment #2:
Here are some notes on which Cocoa classes are thread safe or not:
<http://developer.apple.com/documentation/Cocoa/Conceptual/Multithreading/articles/CocoaSafety.html>
In theory, AppKit is not really thread-safe except for drawing operations
which involve NSView, NSString, NSBezierPath.
I think this -setApplicationImage: method is relying on NSImage which is not
thread-safe. According to Cocoa documentation, NSImage can draw in its own
buffer within a thread, I don't know if GNUstep NSImage is implemented in a
similar fashion.
-setApplicationImage: should be called with DO or with -[NSObject
performSelectorOnMainThread:withObject:waitUntilDone:] (still not implemented
in -base iirc)
We should close this bug probably ? Unless we decide to have NSApplication
fully thread-safe; -performSelectorOnMainThread:withObject:waitUntilDone: has
probably to be implemented then.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=14759>
_______________________________________________
Message posté via/par Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
