j
: Next unread message k
: Previous unread message j a
: Jump to all threads
j l
: Jump to MailingList overview
While testing/approving the fix to SystemBrowser>>systemOrganizer: (removing the "super initialize"-call) I noticed that FileContentsBrowser still initializes twice because Browser class>>new calls #systemOrganizer.
The problem lies in FileContentsBrowser class>>browseStream:named: where it says:
(browser := super new) systemOrganizer: organizer
..and since "super new" ends up in Browser class>>new, oopsidaisy,
Not sure how we want to refactor this.
regards, Göran
squeak-dev@lists.squeakfoundation.org