|
From: | Fred Kiefer |
Subject: | [bug #18494] NSRunAlertPanel crash problems (threads?) |
Date: | Sun, 01 Apr 2007 11:49:55 +0000 |
User-agent: | Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de-de) AppleWebKit/419 (KHTML, like Gecko) Safari/419.3 |
Follow-up Comment #3, bug #18494 (project gnustep): Thank you for analysing this bug. Now even I understand wh this is going wrong :-) I think for the standard use of an alert this is a great solution. If you want top put up an alert it should be started by the main thread. We might even want to put this switch to the main thread into the NSApplication runModalForWindow: method. But what about alerts being used as error notifications by the gui code itself? I normally want to be able to fire up a debugger and look at what triggered the error condition. When we change this code to run in a seperate thread that wont be that easy. And what should happen to the thread that run into the problem? But then again debugging multi threaded applications has never been easy. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?18494> _______________________________________________ Nachricht geschickt von/durch Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |