Re: [Pharo-users] To be there or not to be there

2018-04-12 Thread Hilaire
Glad to read that. Note: it is unlikely I could met again such situation as I already re-organized the code. But good to know there is this update menu item if such case arise again. Thanks Hilaire Le 12/04/2018 à 15:17, Denis Kudriashov a écrit : Stef found and I fixed one case which cou

Re: [Pharo-users] To be there or not to be there

2018-04-12 Thread Denis Kudriashov
Stef found and I fixed one case which could be related to your problem. So next release it will be integrated. Also I added to #extra menu group the item "Update" which will help in such buggy cases. 2018-04-03 23:06 GMT+02:00 Hilaire : > Hello, > > I have re-organized the packages and classes i

Re: [Pharo-users] To be there or not to be there

2018-04-04 Thread Sean P. DeNigris
HilaireFernandes wrote > I come to a situation where methods seems to be there without been > there. I encountered two seemingly similar problems, not sure yet how to reproduce and also may have been fixed since then, but for reference they were: - extension methods saved 2 places in filetree - b

Re: [Pharo-users] To be there or not to be there

2018-04-04 Thread Hilaire
Le 04/04/2018 à 11:19, Denis Kudriashov a écrit : How you performed renaming? From package pane menu/shortcut? From pane menu When you rename DrGeoII-Polymorph to DrGeoII-UI the last was already exists? Not it did not exist. -- Dr. Geo http://drgeo.eu

Re: [Pharo-users] To be there or not to be there

2018-04-04 Thread Denis Kudriashov
2018-04-04 10:28 GMT+02:00 Hilaire : > Hi Denis, > > The origin of the problem seems related when renaming a package, the > category extension (*DrGeoII-Polymorph not renamed as *DrGeoII-UI) seems to > not been renamed accordingly. > How you performed renaming? From package pane menu/shortcut? W

Re: [Pharo-users] To be there or not to be there

2018-04-04 Thread Hilaire
Hi Denis, The origin of the problem seems related when renaming a package, the category extension (*DrGeoII-Polymorph not renamed as *DrGeoII-UI) seems to not been renamed accordingly. I did all the source code re-organization with Calypso. Later when I saw the problem, I open the class with

Re: [Pharo-users] To be there or not to be there

2018-04-04 Thread Denis Kudriashov
Hi Hilaire. Probably there is some case where Calypso do not react on particular system changes. Internally it maintains the cache which needs to be invalidated. I did a lot of recategorization during my work and I did't saw such problems quite a long time after I fixed last related issue. If you

Re: [Pharo-users] To be there or not to be there

2018-04-03 Thread Hilaire
I got the problem gone wtih #newTable: by categorizing it, different random attempts were needed. I still have problem with another method in the same class, named #openModal: This one is an override, Nautilus says there is not such implementor but shows it! Calypso says the contrary and ins

Re: [Pharo-users] To be there or not to be there

2018-04-03 Thread Ben Coman
On 4 April 2018 at 05:06, Hilaire wrote: > Hello, > > I have re-organized the packages and classes in DrGeo with Calypso. An now > I come to a situation where methods seems to be there without been there. > > For example DrGeoWindow>>newTable: methods, > > - Calypso can browse it and can show its