[BUG] Double initialize still in FileContentsBrowser
goran.krampe at bluefish.se
goran.krampe at bluefish.se
Mon May 24 14:05:46 UTC 2004
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
More information about the Squeak-dev
mailing list
|