>With Pharo beta, right button still doesn't work out of the box
>in Windows. Mariano, can you try the installer executable on http://pharo-project.org/pharo-download ? For me right button work out of the box on XP and Vista and the installer uses the same image as Damien provides on the download site. Bye Torsten -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
What I don't understand is why InputEventSensor
installMouseDecodeTable would solve the problem because this method is run at startup... Adrian On Aug 11, 2009, at 20:19 , Torsten Bergmann wrote: >> With Pharo beta, right button still doesn't work out of the box >> in Windows. > > Mariano, can you try the installer executable on > http://pharo-project.org/pharo-download ? > > For me right button work out of the box on XP and Vista and the > installer uses the same image as Damien provides on the download > site. > > Bye > Torsten > > > > > > > > > -- > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla > Firefox 3 - > sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Torsten Bergmann
On Tue, Aug 11, 2009 at 5:19 PM, Torsten Bergmann <[hidden email]> wrote: >With Pharo beta, right button still doesn't work out of the box It doesn't work neither.
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Adrian Lienhard
On Tue, Aug 11, 2009 at 5:29 PM, Adrian Lienhard <[hidden email]> wrote: What I don't understand is why InputEventSensor I really don't know, but works :(
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Can you reproduce this with a fresh Pharo-core?
It would be interesting to know whether the method is run at startup in your image. It is run as expected in my image (latest pharo-core). Could you add a halt in #installMouseDecodeTable save and restart the image? Adrian On Aug 11, 2009, at 20:38 , Mariano Martinez Peck wrote: > On Tue, Aug 11, 2009 at 5:29 PM, Adrian Lienhard <[hidden email]> > wrote: > >> What I don't understand is why InputEventSensor >> installMouseDecodeTable would solve the problem because this method >> is >> run at startup... > > > I really don't know, but works :( > > >> >> >> Adrian >> >> On Aug 11, 2009, at 20:19 , Torsten Bergmann wrote: >> >>>> With Pharo beta, right button still doesn't work out of the box >>>> in Windows. >>> >>> Mariano, can you try the installer executable on >>> http://pharo-project.org/pharo-download ? >>> >>> For me right button work out of the box on XP and Vista and the >>> installer uses the same image as Damien provides on the download >>> site. >>> >>> Bye >>> Torsten >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla >>> Firefox 3 - >>> sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Tue, Aug 11, 2009 at 6:15 PM, Adrian Lienhard <[hidden email]> wrote: Can you reproduce this with a fresh Pharo-core? Yes, I did that. Clean pharo beta core. The situation is this: When you first open the image, it doesn't work. However, if you save it (without doing nothing) and open it again, it start working (even when not evaluating InputEventSensor installMouseDecodeTable) I am alone? best, mariano
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Hi Mariano,
You are not alone. I also get this problem on Windows (Vista) with Pharo1.0betaCore-10401. The cause of the problem is this... Both OSPlatform and InputEventSensor are in the
Smalltalk StartUpList.
It is ESSENTIAL that OSPlatform's startup code runs BEFORE InputEventSensor's startup code. This is because installMouseDecodeTable calls
"Preferences swapMouseButtons", which in turn calls "OSPlatform current
platformFamily".
The OSPlatform startup code sets "OSPlatform Current" to a new instance representing the current platform. If InputEventSensor startup runs BEFORE
OSPlatform's startup, then "OSPlatform current" will be an instance representing
the Operating System on which the image was SAVED. (This explains why saving the
image and restarting solves the problem)
Try evaluating this in an image with the right
mouse button not working...
((SystemDictionary classPool at:
'StartUpList') indexOf: #OSPlatform) < ((SystemDictionary classPool at:
'StartUpList') indexOf: #InputEventSensor).
It should be true, but will evaluate to
false.
Now evaluate...
OSPlatform initialize.
((SystemDictionary classPool at: 'StartUpList') indexOf: #OSPlatform) < ((SystemDictionary classPool at: 'StartUpList') indexOf: #InputEventSensor). It is now true - the startups are in the correct
order.
I guess that the solution is to build a new core
image with the startup order repaired by evaluating "OSPlatform
initialize."
Cheers,
Andy
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
That explains it! Thanks for figuring out, Andrew.
I reopened http://code.google.com/p/pharo/issues/detail?id=838 Adrian On Aug 12, 2009, at 09:54 , Andrew Tween wrote: > Hi Mariano, > You are not alone. > I also get this problem on Windows (Vista) with > Pharo1.0betaCore-10401. > > The cause of the problem is this... > > Both OSPlatform and InputEventSensor are in the Smalltalk StartUpList. > It is ESSENTIAL that OSPlatform's startup code runs BEFORE > InputEventSensor's startup code. > > This is because installMouseDecodeTable calls "Preferences > swapMouseButtons", which in turn calls "OSPlatform current > platformFamily". > The OSPlatform startup code sets "OSPlatform Current" to a new > instance representing the current platform. > > If InputEventSensor startup runs BEFORE OSPlatform's startup, then > "OSPlatform current" will be an instance representing the Operating > System on which the image was SAVED. (This explains why saving the > image and restarting solves the problem) > > Try evaluating this in an image with the right mouse button not > working... > > ((SystemDictionary classPool at: 'StartUpList') indexOf: > #OSPlatform) < ((SystemDictionary classPool at: 'StartUpList') > indexOf: #InputEventSensor). > > It should be true, but will evaluate to false. > > Now evaluate... > > OSPlatform initialize. > ((SystemDictionary classPool at: 'StartUpList') indexOf: > #OSPlatform) < ((SystemDictionary classPool at: 'StartUpList') > indexOf: #InputEventSensor). > > It is now true - the startups are in the correct order. > > I guess that the solution is to build a new core image with the > startup order repaired by evaluating "OSPlatform initialize." > > Cheers, > Andy > "Mariano Martinez Peck" <[hidden email]> wrote in message news:[hidden email] > ... > > > > On Tue, Aug 11, 2009 at 6:15 PM, Adrian Lienhard <[hidden email]> > wrote: > > Can you reproduce this with a fresh Pharo-core? > > It would be interesting to know whether the method is run at > startup > in your image. It is run as expected in my image (latest pharo- > core). > Could you add a halt in #installMouseDecodeTable save and restart > the > image? > > Yes, I did that. Clean pharo beta core. The situation is this: > > When you first open the image, it doesn't work. However, if you > save it (without doing nothing) and open it again, it start working > (even when not evaluating InputEventSensor installMouseDecodeTable) > > I am alone? > > best, > > mariano > > > Adrian > > > On Aug 11, 2009, at 20:38 , Mariano Martinez Peck wrote: > >> On Tue, Aug 11, 2009 at 5:29 PM, Adrian Lienhard <[hidden email]> >> wrote: >> >>> What I don't understand is why InputEventSensor >>> installMouseDecodeTable would solve the problem because this method >>> is >>> run at startup... >> >> >> I really don't know, but works :( >> >> >>> >>> >>> Adrian >>> >>> On Aug 11, 2009, at 20:19 , Torsten Bergmann wrote: >>> >>>>> With Pharo beta, right button still doesn't work out of the box >>>>> in Windows. >>>> >>>> Mariano, can you try the installer executable on >>>> http://pharo-project.org/pharo-download ? >>>> >>>> For me right button work out of the box on XP and Vista and the >>>> installer uses the same image as Damien provides on the download >>>> site. >>>> >>>> Bye >>>> Torsten >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla >>>> Firefox 3 - >>>> sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project_______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Andrew Tween
2009/8/12 Andrew Tween <[hidden email]>
WOW! Nice debugging!! Thanks for the help. Now I wonder, where to put that "OSPlatform initialize." . This may be evaluated when an image is generated? What about adding that in something like "ScriptLoader cleanUpForRelease" ? Best, Mariano
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
We need to change the startup list such that the InputEventSensor
comes after OSPlatform. This can be done in InputEventSensor class>>initialize. Will do that in one of the next updates. Adrian On Aug 12, 2009, at 15:26 , Mariano Martinez Peck wrote: > 2009/8/12 Andrew Tween <[hidden email]> > >> Hi Mariano, >> You are not alone. >> I also get this problem on Windows (Vista) with >> Pharo1.0betaCore-10401. >> >> The cause of the problem is this... >> >> Both OSPlatform and InputEventSensor are in the Smalltalk >> StartUpList. >> It is ESSENTIAL that OSPlatform's startup code runs BEFORE >> InputEventSensor's startup code. >> >> This is because installMouseDecodeTable calls "Preferences >> swapMouseButtons", which in turn calls "OSPlatform current >> platformFamily". >> The OSPlatform startup code sets "OSPlatform Current" to a new >> instance >> representing the current platform. >> >> If InputEventSensor startup runs BEFORE OSPlatform's startup, then >> "OSPlatform current" will be an instance representing the Operating >> System >> on which the image was SAVED. (This explains why saving the image and >> restarting solves the problem) >> >> Try evaluating this in an image with the right mouse button not >> working... >> >> ((SystemDictionary classPool at: 'StartUpList') indexOf: >> #OSPlatform) < >> ((SystemDictionary classPool at: 'StartUpList') indexOf: >> #InputEventSensor). >> >> It should be true, but will evaluate to false. >> >> Now evaluate... >> >> OSPlatform initialize. >> ((SystemDictionary classPool at: 'StartUpList') indexOf: >> #OSPlatform) < >> ((SystemDictionary classPool at: 'StartUpList') indexOf: >> #InputEventSensor). >> >> It is now true - the startups are in the correct order. >> >> I guess that the solution is to build a new core image with the >> startup >> order repaired by evaluating "OSPlatform initialize." >> >> > > WOW! Nice debugging!! Thanks for the help. Now I wonder, where to > put that > "OSPlatform initialize." . This may be evaluated when an image is > generated? > > What about adding that in something like "ScriptLoader > cleanUpForRelease" ? > > Best, > > Mariano > > >> Cheers, >> Andy >> >> "Mariano Martinez Peck" <[hidden email]> wrote in message >> news:[hidden email]... >> >> >> On Tue, Aug 11, 2009 at 6:15 PM, Adrian Lienhard <[hidden email]> >> wrote: >> >>> Can you reproduce this with a fresh Pharo-core? >>> >>> It would be interesting to know whether the method is run at startup >>> in your image. It is run as expected in my image (latest pharo- >>> core). >>> Could you add a halt in #installMouseDecodeTable save and restart >>> the >>> image? >> >> >> Yes, I did that. Clean pharo beta core. The situation is this: >> >> When you first open the image, it doesn't work. However, if you >> save it >> (without doing nothing) and open it again, it start working (even >> when not >> evaluating InputEventSensor installMouseDecodeTable) >> >> I am alone? >> >> best, >> >> mariano >> >> >>> >>> Adrian >>> >>> On Aug 11, 2009, at 20:38 , Mariano Martinez Peck wrote: >>> >>>> On Tue, Aug 11, 2009 at 5:29 PM, Adrian Lienhard < >>> adi-cTM//Nd5/[hidden email] <[hidden email]>> >>> >>>> wrote: >>>> >>>>> What I don't understand is why InputEventSensor >>>>> installMouseDecodeTable would solve the problem because this >>>>> method >>>>> is >>>>> run at startup... >>>> >>>> >>>> I really don't know, but works :( >>>> >>>> >>>>> >>>>> >>>>> Adrian >>>>> >>>>> On Aug 11, 2009, at 20:19 , Torsten Bergmann wrote: >>>>> >>>>>>> With Pharo beta, right button still doesn't work out of the box >>>>>>> in Windows. >>>>>> >>>>>> Mariano, can you try the installer executable on >>>>>> http://pharo-project.org/pharo-download ? >>>>>> >>>>>> For me right button work out of the box on XP and Vista and the >>>>>> installer uses the same image as Damien provides on the download >>>>>> site. >>>>>> >>>>>> Bye >>>>>> Torsten >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla >>>>>> Firefox 3 - >>>>>> sicherer, schneller und einfacher! >>> http://portal.gmx.net/de/go/atbrowser >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> [hidden email]<Pharo-project-bM+ny+RY8h+a+bCvCPl5/[hidden email] >>>>>> > >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [hidden email]<Pharo-project-bM+ny+RY8h+a+bCvCPl5/[hidden email] >>>>> > >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email]<Pharo-project-bM+ny+RY8h+a+bCvCPl5/[hidden email] >>>> > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email]<Pharo-project-bM+ny+RY8h+a+bCvCPl5/[hidden email] >>> > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> ------------------------------ >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Wed, Aug 12, 2009 at 12:33 PM, Adrian Lienhard <[hidden email]> wrote: We need to change the startup list such that the InputEventSensor Ok. Be aware that http://code.google.com/p/pharo/issues/detail?id=838 the status is fixed. I think we should put another state now until this has really been fixed. Best Mariano
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Fixed is the correct state. It means that there exists a fix for the
issue. It does not mean that the fix has been released. Latter state is named "Closed". Adrian On Aug 12, 2009, at 17:25 , Mariano Martinez Peck wrote: > On Wed, Aug 12, 2009 at 12:33 PM, Adrian Lienhard <[hidden email]> > wrote: > >> We need to change the startup list such that the InputEventSensor >> comes after OSPlatform. This can be done in InputEventSensor >> class>>initialize. Will do that in one of the next updates. >> > > Ok. Be aware that http://code.google.com/p/pharo/issues/detail?id=838 > the status is fixed. I think we should put another state now until > this has > really been fixed. > > Best > > Mariano* > * > >> >> Adrian >> >> On Aug 12, 2009, at 15:26 , Mariano Martinez Peck wrote: >> >>> 2009/8/12 Andrew Tween <[hidden email]> >>> >>>> Hi Mariano, >>>> You are not alone. >>>> I also get this problem on Windows (Vista) with >>>> Pharo1.0betaCore-10401. >>>> >>>> The cause of the problem is this... >>>> >>>> Both OSPlatform and InputEventSensor are in the Smalltalk >>>> StartUpList. >>>> It is ESSENTIAL that OSPlatform's startup code runs BEFORE >>>> InputEventSensor's startup code. >>>> >>>> This is because installMouseDecodeTable calls "Preferences >>>> swapMouseButtons", which in turn calls "OSPlatform current >>>> platformFamily". >>>> The OSPlatform startup code sets "OSPlatform Current" to a new >>>> instance >>>> representing the current platform. >>>> >>>> If InputEventSensor startup runs BEFORE OSPlatform's startup, then >>>> "OSPlatform current" will be an instance representing the Operating >>>> System >>>> on which the image was SAVED. (This explains why saving the image >>>> and >>>> restarting solves the problem) >>>> >>>> Try evaluating this in an image with the right mouse button not >>>> working... >>>> >>>> ((SystemDictionary classPool at: 'StartUpList') indexOf: >>>> #OSPlatform) < >>>> ((SystemDictionary classPool at: 'StartUpList') indexOf: >>>> #InputEventSensor). >>>> >>>> It should be true, but will evaluate to false. >>>> >>>> Now evaluate... >>>> >>>> OSPlatform initialize. >>>> ((SystemDictionary classPool at: 'StartUpList') indexOf: >>>> #OSPlatform) < >>>> ((SystemDictionary classPool at: 'StartUpList') indexOf: >>>> #InputEventSensor). >>>> >>>> It is now true - the startups are in the correct order. >>>> >>>> I guess that the solution is to build a new core image with the >>>> startup >>>> order repaired by evaluating "OSPlatform initialize." >>>> >>>> >>> >>> WOW! Nice debugging!! Thanks for the help. Now I wonder, where to >>> put that >>> "OSPlatform initialize." . This may be evaluated when an image is >>> generated? >>> >>> What about adding that in something like "ScriptLoader >>> cleanUpForRelease" ? >>> >>> Best, >>> >>> Mariano >>> >>> >>>> Cheers, >>>> Andy >>>> >>>> "Mariano Martinez Peck" <[hidden email]> wrote in message >>>> news:[hidden email]... >>>> >>>> >>>> On Tue, Aug 11, 2009 at 6:15 PM, Adrian Lienhard <[hidden email]> >>>> wrote: >>>> >>>>> Can you reproduce this with a fresh Pharo-core? >>>>> >>>>> It would be interesting to know whether the method is run at >>>>> startup >>>>> in your image. It is run as expected in my image (latest pharo- >>>>> core). >>>>> Could you add a halt in #installMouseDecodeTable save and restart >>>>> the >>>>> image? >>>> >>>> >>>> Yes, I did that. Clean pharo beta core. The situation is this: >>>> >>>> When you first open the image, it doesn't work. However, if you >>>> save it >>>> (without doing nothing) and open it again, it start working (even >>>> when not >>>> evaluating InputEventSensor installMouseDecodeTable) >>>> >>>> I am alone? >>>> >>>> best, >>>> >>>> mariano >>>> >>>> >>>>> >>>>> Adrian >>>>> >>>>> On Aug 11, 2009, at 20:38 , Mariano Martinez Peck wrote: >>>>> >>>>>> On Tue, Aug 11, 2009 at 5:29 PM, Adrian Lienhard < >>>>> adi-cTM//Nd5/[hidden email] <[hidden email]>> >>>>> >>>>>> wrote: >>>>>> >>>>>>> What I don't understand is why InputEventSensor >>>>>>> installMouseDecodeTable would solve the problem because this >>>>>>> method >>>>>>> is >>>>>>> run at startup... >>>>>> >>>>>> >>>>>> I really don't know, but works :( >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> Adrian >>>>>>> >>>>>>> On Aug 11, 2009, at 20:19 , Torsten Bergmann wrote: >>>>>>> >>>>>>>>> With Pharo beta, right button still doesn't work out of the >>>>>>>>> box >>>>>>>>> in Windows. >>>>>>>> >>>>>>>> Mariano, can you try the installer executable on >>>>>>>> http://pharo-project.org/pharo-download ? >>>>>>>> >>>>>>>> For me right button work out of the box on XP and Vista and the >>>>>>>> installer uses the same image as Damien provides on the >>>>>>>> download >>>>>>>> site. >>>>>>>> >>>>>>>> Bye >>>>>>>> Torsten >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla >>>>>>>> Firefox 3 - >>>>>>>> sicherer, schneller und einfacher! >>>>> http://portal.gmx.net/de/go/atbrowser >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Pharo-project mailing list >>>>>>>> [hidden email] >> <Pharo-project-bM+ny+RY8h+a+bCvCPl5/[hidden email] >>>>>>>>> >>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pharo-project mailing list >>>>>>> [hidden email] >> <Pharo-project-bM+ny+RY8h+a+bCvCPl5/[hidden email] >>>>>>>> >>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>>>> project >>>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> [hidden email] >> <Pharo-project-bM+ny+RY8h+a+bCvCPl5/[hidden email] >>>>>>> >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [hidden email] >> <Pharo-project-bM+ny+RY8h+a+bCvCPl5/[hidden email] >>>>>> >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>>> >>>> >>>> ------------------------------ >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [hidden email] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [hidden email] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Adrian Lienhard
On 12-Aug-09, at 6:33 AM, Adrian Lienhard wrote: > We need to change the startup list such that the InputEventSensor > comes after OSPlatform. This can be done in InputEventSensor > class>>initialize. Will do that in one of the next updates. > > Adrian > If you are going to do this I would suggest you *audit* the entire startup/shutdown ordered collection to understand if the order is correct and somehow ensure perhaps by a initialization method that does the reorder for all classes in the sequence that is run when you build a new official image. The Sophie team was burned from time to time by this order problem and having different team members just drop a class somewhere random in the sequence. As you see the order *can* be important, and bizarre things can happen. A wiki page documenting the why might be useful too. -- = = = ======================================================================== John M. McIntosh <[hidden email]> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Free forum by Nabble | Edit this page |