bug-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Recent drawing optimizations


From: Richard Frith-Macdonald
Subject: Re: Recent drawing optimizations
Date: Tue, 1 Apr 2003 15:51:36 +0100


On Tuesday, April 1, 2003, at 03:31  pm, Ludovic Marcotte wrote:
The stack trace Benhur posted shows where the crash is initiated. The
subthread in GNUMail post a distributed notification to update the status
label in the MailWindow. The MailWindowController adds itself as an
observer in the main thread for those distributed notifications
(GNUMailStatusLabelMessage). Upon reception of distributed notifications,
this will call, in the main thread, MailWindowController:
-updateStatusLabelWithMessage:.

This used to work perfectly for months. I haven't changed anything lately
related to that.

On 21st Feb I modified/fixed NSDistributedNotificationCenter.m so that
notifications could arrive in any thread. Before that, notifications would
only ever arrive in the thread which made the initial connection to the
distributed notification server (I considered this a minor bug).

I don't *think* you are supposed to make assumptions about which thread
a notification will arrive in ... but I'm not sure.

Anyway, this would explain the problem ... but the obvious question arising is what the 'correct' thread behavior is for notification handling, and hence
whether this is a base library bug or an application bug.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]