- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Understanding ClassModifiedClassDefinition announcement

by Yuriy Tymchuk

Oh, thanks. This was useful! On 21 Jul 2014, at 21:02, Nicolai Hess <nicolaihess(a)web.de> wrote: > during > Object subclass: #SomeClass instanceVariableNames: 'one' > the announcement is send and your class var points to the old class definition. > after > Object subclass: #SomeClass instanceVariableNames: 'one' > is done, your class var points to the new class definition. > And yes, I think it is the wrong behavior. The announcement is not useful > if it announces this change before the class has changed. > > There is a bug report for this: > > 13020 ClassModifiedClassDefinition should be announced AFTER the class is changed > > > > > > > 2014-07-21 20:09 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, I did this small experiment > > class := Object subclass: #SomeClass. > SystemAnnouncer uniqueInstance > when: ClassModifiedClassDefinition > do: [ :ann | > Transcript cr; > crShow: class == ann oldClassDefinition; > crShow: class == ann newClassDefinition ]. > Transcript > crShow: class == (Object subclass: #SomeClass instanceVariableNames: 'one' ). > > and got > > true > false > true > > I could understand getting true, false, false, and so having a new object for a new class, or getting false, true, true e.i getting the same object and oldClassDefinition would be a mock that can be used for consistency. > > How is all this thing working? Because Iâm tracking classes and I need to switch to another object if itâs changed and evaluate some methods. But I canât evaluate them on newClassDefinition because itâs a different object, and I canât do it on oldClassDefinition because itâs oldâ¦ > > > I would be very grateful. > Uko >

July 21, 2014

Re: [Pharo-dev] Understanding ClassModifiedClassDefinition announcement

by Nicolai Hess

during Object subclass: #SomeClass instanceVariableNames: 'one' the announcement is send and your class var points to the old class definition. after Object subclass: #SomeClass instanceVariableNames: 'one' is done, your class var points to the new class definition. And yes, I think it is the wrong behavior. The announcement is not useful if it announces this change before the class has changed. There is a bug report for this: 13020 <https://pharo.fogbugz.com/default.asp?13020> ClassModifiedClassDefinition should be announced AFTER the class is changed 2014-07-21 20:09 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, I did this small experiment > > class := Object subclass: #SomeClass. > SystemAnnouncer uniqueInstance > when: ClassModifiedClassDefinition > do: [ :ann | > Transcript cr; > crShow: class == ann oldClassDefinition; > crShow: class == ann newClassDefinition ]. > Transcript > crShow: class == (Object subclass: #SomeClass > instanceVariableNames: 'one' ). > > and got > > true > false > true > > I could understand getting true, false, false, and so having a new object > for a new class, or getting false, true, true e.i getting the same object > and oldClassDefinition would be a mock that can be used for consistency. > > How is all this thing working? Because Iâm tracking classes and I need to > switch to another object if itâs changed and evaluate some methods. But I > canât evaluate them on newClassDefinition because itâs a different object, > and I canât do it on oldClassDefinition because itâs oldâ¦ > > > I would be very grateful. > Uko >

July 21, 2014

Understanding ClassModifiedClassDefinition announcement

by Yuriy Tymchuk

Hi, I did this small experiment class := Object subclass: #SomeClass. SystemAnnouncer uniqueInstance when: ClassModifiedClassDefinition do: [ :ann | Transcript cr; crShow: class == ann oldClassDefinition; crShow: class == ann newClassDefinition ]. Transcript crShow: class == (Object subclass: #SomeClass instanceVariableNames: 'one' ). and got true false true I could understand getting true, false, false, and so having a new object for a new class, or getting false, true, true e.i getting the same object and oldClassDefinition would be a mock that can be used for consistency. How is all this thing working? Because Iâm tracking classes and I need to switch to another object if itâs changed and evaluate some methods. But I canât evaluate them on newClassDefinition because itâs a different object, and I canât do it on oldClassDefinition because itâs oldâ¦ I would be very grateful. Uko

July 21, 2014

Re: [Pharo-dev] mistakenly committed in Pharo30

by stepharo

Thanks doru for the notice I has normally no impact since we only load versionned versions. Stef On 21/7/14 18:21, Tudor Girba wrote: > Hi. > > Just to let you know: > I committed by mistake Keymapping-Core-TudorGirba.185 directly in the > http://smalltalkhub.com/mc/Pharo/Pharo30/main repository. > > I logged in on SmalltalkHub, and I deleted the offending mcz now. > > Cheers, > Doru > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

July 21, 2014

Re: [Pharo-dev] How to close all inspector windows ?

by Jan Vrany

On 21/07/14 17:46, Esteban Lorenzano wrote: > > On 21 Jul 2014, at 18:40, Peter UhnÃ¡k <i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com>> wrote: > >> > We should not get limited in spawning inspectors, I think. >> My question is... is there any legitimate reason to have opened >> hundreds of any type of window? Whether they are browser, debugger, >> inspector or anything else. At least to me that would seem like an error. > > is there any legitimate reason to forbid it? > placing artificial restrictions in base of âwhat we think it should beâ > is definitively a bad a idea. Both for programming and life. > (also, being able to restrict, filter, etc. in taskbar is a better idea, > and a non-restrictive one) > > Esteban What about a token bucket sort of mechanism? This protects well against window bomb and does not impose any artificial limit at the same time. Best. Jan > >> >> >> On Mon, Jul 21, 2014 at 6:30 PM, Esteban Lorenzano >> <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> >> >> On 21 Jul 2014, at 18:26, Guillermo Polito >> <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: >> >>> +1 to Doru. >> >> +1 >> >>> >>> In addition, if managed at the inspector level, you'll have the >>> same problem with the debuggers and any other easily-spawned window. >>> >>> >>> On Mon, Jul 21, 2014 at 6:24 PM, Tudor Girba >>> <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >>> >>> I think the issue should be addressed at the level of the >>> TaskbarMorph. That should be the one that gets limited, for >>> example, by providing a "more windows" button. >>> >>> We should not get limited in spawning inspectors, I think. >>> >>> Cheers, >>> Doru >>> >>> >>> On Mon, Jul 21, 2014 at 3:58 PM, stepharo <stepharo(a)free.fr >>> <mailto:stepharo@free.fr>> wrote: >>> >>> >>> On 21/7/14 10:29, Peter UhnÃ¡k wrote: >>>> Wouldn't it be easier to simply enforce fixed limit of >>>> Inspector/Debug instances (e.g. 10 or 20)? After >>>> reaching the limit creation of more would be simply >>>> ignored. Because as a victim I don't see much use of >>>> having vastly more windows than even fit on the screen >>>> especially since most of the erroneous windows are >>>> actually identical. >>> >>> yes this is a nice idea. >>> If somebody is ready for the challenge, please try and we >>> will integrate it. >>> >>> >>>> >>>> Peter >>>> >>>> >>>> On Mon, Jul 21, 2014 at 10:00 AM, phil(a)highoctane.be >>>> <mailto:phil@highoctane.be> <phil(a)highoctane.be >>>> <mailto:phil@highoctane.be>> wrote: >>>> >>>> It would be nice to have the toolbar have some kind >>>> of Win7 spinner to the right to solve this. >>>> >>>> Is there a way to know when a system window was opened? >>>> >>>> Who hasn't been a victim of the attack of the too >>>> many windows popping up all over? >>>> >>>> Phil >>>> >>>> Le 21 juil. 2014 02:12, "Ben Coman" >>>> <btc(a)openinworld.com <mailto:btc@openinworld.com>> a >>>> Ã©crit : >>>> >>>> kilon alios wrote: >>>>> I am afraid I could not do that, it seems that >>>>> when pharo has opened too many windows the >>>>> bottom bar takes all the space of the pharo >>>>> windows and because it has higher viewer >>>>> priority you cannot view any kind of window. >>>>> All you see is that bars that represent open >>>>> windows filling your screen. >>>> >>>> That is a problem. >>>> https://pharo.fogbugz.com/f/cases/13618/Toolbar-should-never-fill-more-than… >>>> >>>>> >>>>> So the solution for me was to reopen the image >>>>> , fetch most of my lost code from changes and >>>>> fortunately only add a few lines of code back >>>>> that were permanently lost. >>>>> >>>>> So a big thank you for changes , it saved me at >>>>> least hours of work and thank you for trying to >>>>> help me. >>>>> >>>>> >>>>> On Sun, Jul 20, 2014 at 6:13 PM, Ben Coman >>>>> <btc(a)openinworld.com >>>>> <mailto:btc@openinworld.com>> wrote: >>>>> >>>>> As Peter said, you can execute any code in >>>>> an inspector window. Here is how you might >>>>> solve this yourself :) >>>>> There is a menu option >>>>> World > Windows > Delete unchanged windows. >>>>> Of course, you can't use that directly >>>>> since your background is covered with >>>>> windows. But you could open up another >>>>> image and then do this... >>>>> 1. Bring up the halos on that menu option >>>>> 2. Click the "Debug" spanner icon and >>>>> choose 'Inspect Morph' >>>>> 3. Scroll down to /target/ where you find >>>>> "[ World closeUnchangedWindows ]" >>>>> 4. Evaluate that back in the problem image >>>>> in any Inspector. >>>>> >>>>> I describe this process since until a >>>>> moment ago when I did that, I didn't know >>>>> about the existence of "closeUnchangedWindows." >>>>> cheers -ben >>>>> >>>>> >>>>> Peter UhnÃ¡k wrote: >>>>>> Maybe running something like this would work: >>>>>> ---- >>>>>> InspectorNavigator allInstancesDo: [ :each >>>>>> | each window close ]. >>>>>> ---- >>>>>> >>>>>> You can run arbitrary code from basically >>>>>> anywhere where you can enter text (and >>>>>> Inspector has couple of boxes where you >>>>>> can enter text). >>>>>> >>>>>> Also doesn't holding escape close it too? >>>>>> >>>>>> Peter >>>>>> >>>>>> >>>>>> On Sun, Jul 20, 2014 at 3:33 PM, kilon >>>>>> alios <kilon.alios(a)gmail.com >>>>>> <mailto:kilon.alios@gmail.com>> wrote: >>>>>> >>>>>> Is there a shortcut to close all >>>>>> inspector windows ? and if not how I >>>>>> close the window of a selected inspector ? >>>>>> >>>>>> Basically I accidentally opened over >>>>>> 1000 inspector windows and i want to >>>>>> close them all now because they have >>>>>> occupied the entire GUI and I cant do >>>>>> anything other than closing them on by >>>>>> one. I cant open the world menu or >>>>>> open a new window because they take >>>>>> not only the entire window but also >>>>>> they are always on top. >>>>>> >>>>>> The tragedy is that I had plenty of >>>>>> code that I don't want to lose because >>>>>> I have not saved, please help :( >>>>>> >>>>>> Can't open a workspace to issue pharo >>>>>> commands or any other window :( >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com <http://www.tudorgirba.com/> >>> >>> "Every thing has its own flow" >>> >>> >> >> >

July 21, 2014

Re: [Pharo-dev] How to close all inspector windows ?

by Esteban Lorenzano

On 21 Jul 2014, at 18:40, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > We should not get limited in spawning inspectors, I think. > My question is... is there any legitimate reason to have opened hundreds of any type of window? Whether they are browser, debugger, inspector or anything else. At least to me that would seem like an error. is there any legitimate reason to forbid it? placing artificial restrictions in base of âwhat we think it should beâ is definitively a bad a idea. Both for programming and life. (also, being able to restrict, filter, etc. in taskbar is a better idea, and a non-restrictive one) Esteban > > > On Mon, Jul 21, 2014 at 6:30 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 21 Jul 2014, at 18:26, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > >> +1 to Doru. > > +1 > >> >> In addition, if managed at the inspector level, you'll have the same problem with the debuggers and any other easily-spawned window. >> >> >> On Mon, Jul 21, 2014 at 6:24 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> I think the issue should be addressed at the level of the TaskbarMorph. That should be the one that gets limited, for example, by providing a "more windows" button. >> >> We should not get limited in spawning inspectors, I think. >> >> Cheers, >> Doru >> >> >> On Mon, Jul 21, 2014 at 3:58 PM, stepharo <stepharo(a)free.fr> wrote: >> >> On 21/7/14 10:29, Peter UhnÃ¡k wrote: >>> Wouldn't it be easier to simply enforce fixed limit of Inspector/Debug instances (e.g. 10 or 20)? After reaching the limit creation of more would be simply ignored. Because as a victim I don't see much use of having vastly more windows than even fit on the screen especially since most of the erroneous windows are actually identical. >> >> yes this is a nice idea. >> If somebody is ready for the challenge, please try and we will integrate it. >> >> >>> >>> Peter >>> >>> >>> On Mon, Jul 21, 2014 at 10:00 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >>> It would be nice to have the toolbar have some kind of Win7 spinner to the right to solve this. >>> >>> Is there a way to know when a system window was opened? >>> >>> Who hasn't been a victim of the attack of the too many windows popping up all over? >>> Phil >>> >>> Le 21 juil. 2014 02:12, "Ben Coman" <btc(a)openinworld.com> a Ã©crit : >>> >>> kilon alios wrote: >>>> >>>> I am afraid I could not do that, it seems that when pharo has opened too many windows the bottom bar takes all the space of the pharo windows and because it has higher viewer priority you cannot view any kind of window. All you see is that bars that represent open windows filling your screen. >>> >>> That is a problem. >>> https://pharo.fogbugz.com/f/cases/13618/Toolbar-should-never-fill-more-than… >>> >>>> >>>> So the solution for me was to reopen the image , fetch most of my lost code from changes and fortunately only add a few lines of code back that were permanently lost. >>>> >>>> So a big thank you for changes , it saved me at least hours of work and thank you for trying to help me. >>>> >>>> >>>> On Sun, Jul 20, 2014 at 6:13 PM, Ben Coman <btc(a)openinworld.com> wrote: >>>> As Peter said, you can execute any code in an inspector window. Here is how you might solve this yourself :) >>>> There is a menu option >>>> World > Windows > Delete unchanged windows. >>>> Of course, you can't use that directly since your background is covered with windows. But you could open up another image and then do this... >>>> 1. Bring up the halos on that menu option >>>> 2. Click the "Debug" spanner icon and choose 'Inspect Morph' >>>> 3. Scroll down to /target/ where you find "[ World closeUnchangedWindows ]" >>>> 4. Evaluate that back in the problem image in any Inspector. >>>> >>>> I describe this process since until a moment ago when I did that, I didn't know about the existence of "closeUnchangedWindows." >>>> cheers -ben >>>> >>>> >>>> Peter UhnÃ¡k wrote: >>>>> >>>>> Maybe running something like this would work: >>>>> ---- >>>>> InspectorNavigator allInstancesDo: [ :each | each window close ]. >>>>> ---- >>>>> >>>>> You can run arbitrary code from basically anywhere where you can enter text (and Inspector has couple of boxes where you can enter text). >>>>> >>>>> Also doesn't holding escape close it too? >>>>> >>>>> Peter >>>>> >>>>> >>>>> On Sun, Jul 20, 2014 at 3:33 PM, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>> Is there a shortcut to close all inspector windows ? and if not how I close the window of a selected inspector ? >>>>> >>>>> Basically I accidentally opened over 1000 inspector windows and i want to close them all now because they have occupied the entire GUI and I cant do anything other than closing them on by one. I cant open the world menu or open a new window because they take not only the entire window but also they are always on top. >>>>> >>>>> The tragedy is that I had plenty of code that I don't want to lose because I have not saved, please help :( >>>>> >>>>> Can't open a workspace to issue pharo commands or any other window :( >>>>> >>>>> >>>> >>>> >>> >>> >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > >

July 21, 2014

Re: [Pharo-dev] How to close all inspector windows ?

by Peter UhnÃ¡k

> We should not get limited in spawning inspectors, I think. My question is... is there any legitimate reason to have opened hundreds of any type of window? Whether they are browser, debugger, inspector or anything else. At least to me that would seem like an error. On Mon, Jul 21, 2014 at 6:30 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 21 Jul 2014, at 18:26, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > +1 to Doru. > > > +1 > > > In addition, if managed at the inspector level, you'll have the same > problem with the debuggers and any other easily-spawned window. > > > On Mon, Jul 21, 2014 at 6:24 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> I think the issue should be addressed at the level of the TaskbarMorph. >> That should be the one that gets limited, for example, by providing a "more >> windows" button. >> >> We should not get limited in spawning inspectors, I think. >> >> Cheers, >> Doru >> >> >> On Mon, Jul 21, 2014 at 3:58 PM, stepharo <stepharo(a)free.fr> wrote: >> >>> >>> On 21/7/14 10:29, Peter UhnÃ¡k wrote: >>> >>> Wouldn't it be easier to simply enforce fixed limit of Inspector/Debug >>> instances (e.g. 10 or 20)? After reaching the limit creation of more would >>> be simply ignored. Because as a victim I don't see much use of having >>> vastly more windows than even fit on the screen especially since most of >>> the erroneous windows are actually identical. >>> >>> >>> yes this is a nice idea. >>> If somebody is ready for the challenge, please try and we will integrate >>> it. >>> >>> >>> >>> Peter >>> >>> >>> On Mon, Jul 21, 2014 at 10:00 AM, phil(a)highoctane.be <phil(a)highoctane.be >>> > wrote: >>> >>>> It would be nice to have the toolbar have some kind of Win7 spinner to >>>> the right to solve this. >>>> >>>> Is there a way to know when a system window was opened? >>>> >>>> Who hasn't been a victim of the attack of the too many windows popping >>>> up all over? >>>> >>>> Phil >>>> Le 21 juil. 2014 02:12, "Ben Coman" <btc(a)openinworld.com> a Ã©crit : >>>> >>>> kilon alios wrote: >>>>> >>>>> I am afraid I could not do that, it seems that when pharo has opened >>>>> too many windows the bottom bar takes all the space of the pharo windows >>>>> and because it has higher viewer priority you cannot view any kind of >>>>> window. All you see is that bars that represent open windows filling your >>>>> screen. >>>>> >>>>> >>>>> That is a problem. >>>>> >>>>> https://pharo.fogbugz.com/f/cases/13618/Toolbar-should-never-fill-more-than… >>>>> >>>>> >>>>> So the solution for me was to reopen the image , fetch most of my >>>>> lost code from changes and fortunately only add a few lines of code back >>>>> that were permanently lost. >>>>> >>>>> So a big thank you for changes , it saved me at least hours of work >>>>> and thank you for trying to help me. >>>>> >>>>> >>>>> On Sun, Jul 20, 2014 at 6:13 PM, Ben Coman <btc(a)openinworld.com> >>>>> wrote: >>>>> >>>>>> As Peter said, you can execute any code in an inspector window. >>>>>> Here is how you might solve this yourself :) >>>>>> There is a menu option >>>>>> World > Windows > Delete unchanged windows. >>>>>> Of course, you can't use that directly since your background is >>>>>> covered with windows. But you could open up another image and then do >>>>>> this... >>>>>> 1. Bring up the halos on that menu option >>>>>> 2. Click the "Debug" spanner icon and choose 'Inspect Morph' >>>>>> 3. Scroll down to /target/ where you find "[ World >>>>>> closeUnchangedWindows ]" >>>>>> 4. Evaluate that back in the problem image in any Inspector. >>>>>> >>>>>> I describe this process since until a moment ago when I did that, I >>>>>> didn't know about the existence of "closeUnchangedWindows." >>>>>> cheers -ben >>>>>> >>>>>> >>>>>> Peter UhnÃ¡k wrote: >>>>>> >>>>>> Maybe running something like this would work: >>>>>> ---- >>>>>> InspectorNavigator allInstancesDo: [ :each | each window close ]. >>>>>> ---- >>>>>> >>>>>> You can run arbitrary code from basically anywhere where you can >>>>>> enter text (and Inspector has couple of boxes where you can enter text). >>>>>> >>>>>> Also doesn't holding escape close it too? >>>>>> >>>>>> Peter >>>>>> >>>>>> >>>>>> On Sun, Jul 20, 2014 at 3:33 PM, kilon alios <kilon.alios(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Is there a shortcut to close all inspector windows ? and if not how >>>>>>> I close the window of a selected inspector ? >>>>>>> >>>>>>> Basically I accidentally opened over 1000 inspector windows and i >>>>>>> want to close them all now because they have occupied the entire GUI and I >>>>>>> cant do anything other than closing them on by one. I cant open the world >>>>>>> menu or open a new window because they take not only the entire window but >>>>>>> also they are always on top. >>>>>>> >>>>>>> The tragedy is that I had plenty of code that I don't want to lose >>>>>>> because I have not saved, please help :( >>>>>>> >>>>>>> Can't open a workspace to issue pharo commands or any other window :( >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > >

July 21, 2014

Re: [Pharo-dev] How to close all inspector windows ?

by Esteban Lorenzano

On 21 Jul 2014, at 18:26, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > +1 to Doru. +1 > > In addition, if managed at the inspector level, you'll have the same problem with the debuggers and any other easily-spawned window. > > > On Mon, Jul 21, 2014 at 6:24 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I think the issue should be addressed at the level of the TaskbarMorph. That should be the one that gets limited, for example, by providing a "more windows" button. > > We should not get limited in spawning inspectors, I think. > > Cheers, > Doru > > > On Mon, Jul 21, 2014 at 3:58 PM, stepharo <stepharo(a)free.fr> wrote: > > On 21/7/14 10:29, Peter UhnÃ¡k wrote: >> Wouldn't it be easier to simply enforce fixed limit of Inspector/Debug instances (e.g. 10 or 20)? After reaching the limit creation of more would be simply ignored. Because as a victim I don't see much use of having vastly more windows than even fit on the screen especially since most of the erroneous windows are actually identical. > > yes this is a nice idea. > If somebody is ready for the challenge, please try and we will integrate it. > > >> >> Peter >> >> >> On Mon, Jul 21, 2014 at 10:00 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> It would be nice to have the toolbar have some kind of Win7 spinner to the right to solve this. >> >> Is there a way to know when a system window was opened? >> >> Who hasn't been a victim of the attack of the too many windows popping up all over? >> Phil >> >> Le 21 juil. 2014 02:12, "Ben Coman" <btc(a)openinworld.com> a Ã©crit : >> >> kilon alios wrote: >>> >>> I am afraid I could not do that, it seems that when pharo has opened too many windows the bottom bar takes all the space of the pharo windows and because it has higher viewer priority you cannot view any kind of window. All you see is that bars that represent open windows filling your screen. >> >> That is a problem. >> https://pharo.fogbugz.com/f/cases/13618/Toolbar-should-never-fill-more-than… >> >>> >>> So the solution for me was to reopen the image , fetch most of my lost code from changes and fortunately only add a few lines of code back that were permanently lost. >>> >>> So a big thank you for changes , it saved me at least hours of work and thank you for trying to help me. >>> >>> >>> On Sun, Jul 20, 2014 at 6:13 PM, Ben Coman <btc(a)openinworld.com> wrote: >>> As Peter said, you can execute any code in an inspector window. Here is how you might solve this yourself :) >>> There is a menu option >>> World > Windows > Delete unchanged windows. >>> Of course, you can't use that directly since your background is covered with windows. But you could open up another image and then do this... >>> 1. Bring up the halos on that menu option >>> 2. Click the "Debug" spanner icon and choose 'Inspect Morph' >>> 3. Scroll down to /target/ where you find "[ World closeUnchangedWindows ]" >>> 4. Evaluate that back in the problem image in any Inspector. >>> >>> I describe this process since until a moment ago when I did that, I didn't know about the existence of "closeUnchangedWindows." >>> cheers -ben >>> >>> >>> Peter UhnÃ¡k wrote: >>>> >>>> Maybe running something like this would work: >>>> ---- >>>> InspectorNavigator allInstancesDo: [ :each | each window close ]. >>>> ---- >>>> >>>> You can run arbitrary code from basically anywhere where you can enter text (and Inspector has couple of boxes where you can enter text). >>>> >>>> Also doesn't holding escape close it too? >>>> >>>> Peter >>>> >>>> >>>> On Sun, Jul 20, 2014 at 3:33 PM, kilon alios <kilon.alios(a)gmail.com> wrote: >>>> Is there a shortcut to close all inspector windows ? and if not how I close the window of a selected inspector ? >>>> >>>> Basically I accidentally opened over 1000 inspector windows and i want to close them all now because they have occupied the entire GUI and I cant do anything other than closing them on by one. I cant open the world menu or open a new window because they take not only the entire window but also they are always on top. >>>> >>>> The tragedy is that I had plenty of code that I don't want to lose because I have not saved, please help :( >>>> >>>> Can't open a workspace to issue pharo commands or any other window :( >>>> >>>> >>> >>> >> >> > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

July 21, 2014

Re: [Pharo-dev] How to close all inspector windows ?

by Guillermo Polito

+1 to Doru. In addition, if managed at the inspector level, you'll have the same problem with the debuggers and any other easily-spawned window. On Mon, Jul 21, 2014 at 6:24 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I think the issue should be addressed at the level of the TaskbarMorph. > That should be the one that gets limited, for example, by providing a "more > windows" button. > > We should not get limited in spawning inspectors, I think. > > Cheers, > Doru > > > On Mon, Jul 21, 2014 at 3:58 PM, stepharo <stepharo(a)free.fr> wrote: > >> >> On 21/7/14 10:29, Peter UhnÃ¡k wrote: >> >> Wouldn't it be easier to simply enforce fixed limit of Inspector/Debug >> instances (e.g. 10 or 20)? After reaching the limit creation of more would >> be simply ignored. Because as a victim I don't see much use of having >> vastly more windows than even fit on the screen especially since most of >> the erroneous windows are actually identical. >> >> >> yes this is a nice idea. >> If somebody is ready for the challenge, please try and we will integrate >> it. >> >> >> >> Peter >> >> >> On Mon, Jul 21, 2014 at 10:00 AM, phil(a)highoctane.be <phil(a)highoctane.be> >> wrote: >> >>> It would be nice to have the toolbar have some kind of Win7 spinner to >>> the right to solve this. >>> >>> Is there a way to know when a system window was opened? >>> >>> Who hasn't been a victim of the attack of the too many windows popping >>> up all over? >>> >>> Phil >>> Le 21 juil. 2014 02:12, "Ben Coman" <btc(a)openinworld.com> a Ã©crit : >>> >>> kilon alios wrote: >>>> >>>> I am afraid I could not do that, it seems that when pharo has opened >>>> too many windows the bottom bar takes all the space of the pharo windows >>>> and because it has higher viewer priority you cannot view any kind of >>>> window. All you see is that bars that represent open windows filling your >>>> screen. >>>> >>>> >>>> That is a problem. >>>> >>>> https://pharo.fogbugz.com/f/cases/13618/Toolbar-should-never-fill-more-than… >>>> >>>> >>>> So the solution for me was to reopen the image , fetch most of my >>>> lost code from changes and fortunately only add a few lines of code back >>>> that were permanently lost. >>>> >>>> So a big thank you for changes , it saved me at least hours of work >>>> and thank you for trying to help me. >>>> >>>> >>>> On Sun, Jul 20, 2014 at 6:13 PM, Ben Coman <btc(a)openinworld.com> wrote: >>>> >>>>> As Peter said, you can execute any code in an inspector window. Here >>>>> is how you might solve this yourself :) >>>>> There is a menu option >>>>> World > Windows > Delete unchanged windows. >>>>> Of course, you can't use that directly since your background is >>>>> covered with windows. But you could open up another image and then do >>>>> this... >>>>> 1. Bring up the halos on that menu option >>>>> 2. Click the "Debug" spanner icon and choose 'Inspect Morph' >>>>> 3. Scroll down to /target/ where you find "[ World >>>>> closeUnchangedWindows ]" >>>>> 4. Evaluate that back in the problem image in any Inspector. >>>>> >>>>> I describe this process since until a moment ago when I did that, I >>>>> didn't know about the existence of "closeUnchangedWindows." >>>>> cheers -ben >>>>> >>>>> >>>>> Peter UhnÃ¡k wrote: >>>>> >>>>> Maybe running something like this would work: >>>>> ---- >>>>> InspectorNavigator allInstancesDo: [ :each | each window close ]. >>>>> ---- >>>>> >>>>> You can run arbitrary code from basically anywhere where you can >>>>> enter text (and Inspector has couple of boxes where you can enter text). >>>>> >>>>> Also doesn't holding escape close it too? >>>>> >>>>> Peter >>>>> >>>>> >>>>> On Sun, Jul 20, 2014 at 3:33 PM, kilon alios <kilon.alios(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Is there a shortcut to close all inspector windows ? and if not how >>>>>> I close the window of a selected inspector ? >>>>>> >>>>>> Basically I accidentally opened over 1000 inspector windows and i >>>>>> want to close them all now because they have occupied the entire GUI and I >>>>>> cant do anything other than closing them on by one. I cant open the world >>>>>> menu or open a new window because they take not only the entire window but >>>>>> also they are always on top. >>>>>> >>>>>> The tragedy is that I had plenty of code that I don't want to lose >>>>>> because I have not saved, please help :( >>>>>> >>>>>> Can't open a workspace to issue pharo commands or any other window :( >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

July 21, 2014

Re: [Pharo-dev] How to close all inspector windows ?

by Tudor Girba

I think the issue should be addressed at the level of the TaskbarMorph. That should be the one that gets limited, for example, by providing a "more windows" button. We should not get limited in spawning inspectors, I think. Cheers, Doru On Mon, Jul 21, 2014 at 3:58 PM, stepharo <stepharo(a)free.fr> wrote: > > On 21/7/14 10:29, Peter UhnÃ¡k wrote: > > Wouldn't it be easier to simply enforce fixed limit of Inspector/Debug > instances (e.g. 10 or 20)? After reaching the limit creation of more would > be simply ignored. Because as a victim I don't see much use of having > vastly more windows than even fit on the screen especially since most of > the erroneous windows are actually identical. > > > yes this is a nice idea. > If somebody is ready for the challenge, please try and we will integrate > it. > > > > Peter > > > On Mon, Jul 21, 2014 at 10:00 AM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> It would be nice to have the toolbar have some kind of Win7 spinner to >> the right to solve this. >> >> Is there a way to know when a system window was opened? >> >> Who hasn't been a victim of the attack of the too many windows popping up >> all over? >> >> Phil >> Le 21 juil. 2014 02:12, "Ben Coman" <btc(a)openinworld.com> a Ã©crit : >> >> kilon alios wrote: >>> >>> I am afraid I could not do that, it seems that when pharo has opened too >>> many windows the bottom bar takes all the space of the pharo windows and >>> because it has higher viewer priority you cannot view any kind of window. >>> All you see is that bars that represent open windows filling your screen. >>> >>> >>> That is a problem. >>> >>> https://pharo.fogbugz.com/f/cases/13618/Toolbar-should-never-fill-more-than… >>> >>> >>> So the solution for me was to reopen the image , fetch most of my lost >>> code from changes and fortunately only add a few lines of code back that >>> were permanently lost. >>> >>> So a big thank you for changes , it saved me at least hours of work >>> and thank you for trying to help me. >>> >>> >>> On Sun, Jul 20, 2014 at 6:13 PM, Ben Coman <btc(a)openinworld.com> wrote: >>> >>>> As Peter said, you can execute any code in an inspector window. Here >>>> is how you might solve this yourself :) >>>> There is a menu option >>>> World > Windows > Delete unchanged windows. >>>> Of course, you can't use that directly since your background is covered >>>> with windows. But you could open up another image and then do this... >>>> 1. Bring up the halos on that menu option >>>> 2. Click the "Debug" spanner icon and choose 'Inspect Morph' >>>> 3. Scroll down to /target/ where you find "[ World >>>> closeUnchangedWindows ]" >>>> 4. Evaluate that back in the problem image in any Inspector. >>>> >>>> I describe this process since until a moment ago when I did that, I >>>> didn't know about the existence of "closeUnchangedWindows." >>>> cheers -ben >>>> >>>> >>>> Peter UhnÃ¡k wrote: >>>> >>>> Maybe running something like this would work: >>>> ---- >>>> InspectorNavigator allInstancesDo: [ :each | each window close ]. >>>> ---- >>>> >>>> You can run arbitrary code from basically anywhere where you can >>>> enter text (and Inspector has couple of boxes where you can enter text). >>>> >>>> Also doesn't holding escape close it too? >>>> >>>> Peter >>>> >>>> >>>> On Sun, Jul 20, 2014 at 3:33 PM, kilon alios <kilon.alios(a)gmail.com> >>>> wrote: >>>> >>>>> Is there a shortcut to close all inspector windows ? and if not how >>>>> I close the window of a selected inspector ? >>>>> >>>>> Basically I accidentally opened over 1000 inspector windows and i want >>>>> to close them all now because they have occupied the entire GUI and I cant >>>>> do anything other than closing them on by one. I cant open the world menu >>>>> or open a new window because they take not only the entire window but also >>>>> they are always on top. >>>>> >>>>> The tragedy is that I had plenty of code that I don't want to lose >>>>> because I have not saved, please help :( >>>>> >>>>> Can't open a workspace to issue pharo commands or any other window :( >>>>> >>>> >>>> >>>> >>> >>> > > -- www.tudorgirba.com "Every thing has its own flow"

July 21, 2014