Package unloading and extensions
This is strange so I report it. When we unload Nautilus package we still get the methods in ThemeIcons with category *Nautilus-contents and antoher one *Nautilus-icons so we thought that unload does not unload extensions whose name is composed (*Nautilus vs. *Nautilus-icons) so we built a case with a package and extensions (on instance and class side of different classes). But unload was unloading them perfectly: *Box, *Box-green, *Box-foo the only difference is that the second experience we did we used the UI MC browser while else we used some script ie (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload. So we are puzzled. Stef and Pavel
On Dec 11, 2013, at 11:45 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
This is strange so I report it. When we unload Nautilus package we still get the methods in ThemeIcons with category *Nautilus-contents and antoher one *Nautilus-icons
so we thought that unload does not unload extensions whose name is composed (*Nautilus vs. *Nautilus-icons) so we built a case with a package and extensions (on instance and class side of different classes). But unload was unloading them perfectly: *Box, *Box-green, *Box-foo
the only difference is that the second experience we did we used the UI MC browser while else we used some script ie
(MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload.
So we are puzzled.
We unloaded Nautilus using the MC Browser and we got the same result the methods in ThemeIcons *Nautilus-icons and *Nautilus-contents where not unloaded.
Stef and Pavel
We did another experience: we moved all the methods in *Nautilus extension and unloaded it but it failed. The methods were not unloaded. On Dec 11, 2013, at 11:45 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
This is strange so I report it. When we unload Nautilus package we still get the methods in ThemeIcons with category *Nautilus-contents and antoher one *Nautilus-icons
so we thought that unload does not unload extensions whose name is composed (*Nautilus vs. *Nautilus-icons) so we built a case with a package and extensions (on instance and class side of different classes). But unload was unloading them perfectly: *Box, *Box-green, *Box-foo
the only difference is that the second experience we did we used the UI MC browser while else we used some script ie
(MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload.
So we are puzzled.
Stef and Pavel
We did another experience: we moved all the methods in *Nautilus extension and unloaded it but it failed. The methods were not unloaded.
In fact this is worse: - we create a new package extensions - did RPackageOrganizer initializeDefaultFromMC. - move all the method to *Nautilus - then we unload them but and we get the methods iconNamed: smallSizeNamed iconNamed:ifNone: and normalSizeNamed (which are normally in accessing when you open the browse, but in polymorph-widgets when displayed using the messageBrowser-implementor) in the *Nautilus extensions. So there is a real bug in there. Stef
On Dec 11, 2013, at 11:45 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
This is strange so I report it. When we unload Nautilus package we still get the methods in ThemeIcons with category *Nautilus-contents and antoher one *Nautilus-icons
so we thought that unload does not unload extensions whose name is composed (*Nautilus vs. *Nautilus-icons) so we built a case with a package and extensions (on instance and class side of different classes). But unload was unloading them perfectly: *Box, *Box-green, *Box-foo
the only difference is that the second experience we did we used the UI MC browser while else we used some script ie
(MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload.
So we are puzzled.
Stef and Pavel
participants (1)
-
Stéphane Ducasse