{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Jason Townsend <[EMAIL PROTECTED]>
on 3/16/02 10:28 PM, Nick Kocharhook <[EMAIL PROTECTED]> wrote:
> A reboot fixed that, so here's the log. This bug is 100% reproducible for
> me. Just use Fire for any length of time and Cmd-drag any toolbar item off
> the toolbar.
...
> Thread 0:
> #0 0x706bab64 in objc_msgSend
> #1 0x70eac3b4 in -[NSToolbar isVisible]
> #2 0x70eae034 in -[NSToolbar _notifyView_DidRemoveItemAtIndex:]
> #3 0x70ead724 in -[NSToolbar
> _removeItemAtIndex:notifyDelegate:notifyView:notifyFamilyAndUpdateDefaults:]
> #4 0x70eaeb64 in -[NSToolbar _toolbarRemovedItemNotification:]
OK, I was able to reproduce this... The trick is that it only happens after
you close at least one chat window.
Turns out the ChatWindow controller was not being deallocated on window
close because the retain count was 2 instead of 1 at that point.
I've fixed this as well as some leaks which were exposed once the ChatWindow
was properly deallocated. Changes are checked in to TOT for those using CVS
builds. The workaround for those on .30b is to simply customize the toolbar
first thing when the application starts before you close the first chat
window.
-Jason
--
<http://homepage.mac.com/townsend/>
"The best way to predict the future is to invent it."
- Alan Kay
{#} ----------------------------------------------------+[ fire ]+---
