Update of bug #14759 (project gnustep):
Status:None = Wont Fix
Open/Closed:Open = Closed
___
Follow-up Comment #6:
Closed as we seem
Follow-up Comment #5, bug #14759 (project gnustep):
Thanks for your help.
Especially the mentioning of the performSelectorOnMainThread-Method
sounds very useful for solving the problem. :-)
-Guenther
___
Reply to this item at:
Update of bug #14759 (project gnustep):
Item Group: Bug = Change Request
Status: Invalid = None
___
Follow-up Comment #4:
Thanks for the
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:
Follow-up Comment #3, bug #14759 (project gnustep):
Quentin, I think that performSelectorOnMainThread:withObject:waitUntilDone:
is implemented in base and hope that it is actually working correctly, as it
gets used by the gui view refreshing quiet heavily.
URL:
http://savannah.gnu.org/bugs/?func=detailitemitem_id=14759
Summary: NSApplication image multithreading problem
Project: GNUstep
Submitted by: None
Submitted on: Mon 10/10/05 at 12:22
Category: Gui/AppKit
Follow-up Comment #1, bug #14759 (project gnustep):
I know the gui library, and NSApplication, is not supposed to be thread-safe,
so anything related to drawing is supposed to nbe done in the main thread.
Does that mean that this report is invalid? Or do we want to make
-setApplicationImage: be
