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 <adi@netstyle.ch> 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 <amtween@hotmail.com>
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" <marianopeck@gmail.com> wrote in message news:a38fadc50908111224p181c8408qd8c6161229bcae90@mail.gmail.com...
On Tue, Aug 11, 2009 at 6:15 PM, Adrian Lienhard <adi@netstyle.ch> 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/DIfv37vnLkPlQ@public.gmane.org <adi@netstyle.ch>>
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 Pharo-project@lists.gforge.inria.fr
<Pharo-project-bM+ny+RY8h+a+bCvCPl5/gCzwTLBPCX0@public.gmane.org
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr <Pharo-project-bM+ny+RY8h+a+bCvCPl5/gCzwTLBPCX0@public.gmane.org
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr <Pharo-project-bM+ny+RY8h+a+bCvCPl5/gCzwTLBPCX0@public.gmane.org
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr <Pharo-project-bM+ny+RY8h+a+bCvCPl5/gCzwTLBPCX0@public.gmane.org
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
------------------------------
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project