Finally, FALSE INFORMATION, sorry... switching to correct VM DID NOT SOLVE MY PROBLEM... It must be that I took a different path second time I tried... Here is a recipe to re-create the problem: 1) Download a fresh image 2) Open a TestRunner 3) Run the CompilerTests I then get the bogus Dialog behavior... Strange thing, if I interrupt with cmd+. then select and execute code for AuthorNameRequest defaultAction, the second dialog box works... I don't want to dig further, raising some notification to invoke a dialog sounds weird, and soon on the stack you find this awfull method: MorphicUIManager>>modalMorph which scans thisContext send stack... Hmmm encapsulation they said... Superpowers for evil? Nicolas 2012/12/8 Ben Coman <btc@openinworld.com>:
Nicolas Cellier wrote:
This is a long time since I did not contribute to Pharo, so I tried with something easy... http://code.google.com/p/pharo/issues/detail?id=7108
I downloaded latest successful build, Pharo2.0a Latest update: #20433
Then I updated the 5 methods from a MC merge, and... Err... I cannot type my initials ^H^H^H^H^H^H^H^H full name The dialog insists on selecting any letter I type and next letter will override the previous one. I finally published anonymously, that does not matter...
But you know the impact of a first bad UI impression... It would ruin tons of efforts I know you spent cleaning the infrastructure. I believe such cleaning is very ambitious and rarely rewarding in the short term... But I'd really like to be more supportive, it's so essential for building the future.
So before ranting loud, I digged a bit further: could it be this warning I had at startup about obsolete VM, yes that was it! So if you are episodic user like me :
******** DON'T FORGET TO DOWNLOAD A PHARO SPECIFIC VM *************
I already spent way more time on this than I wished, hope my mistake helps someone else. ( over-estimating pharo planned obsolescence period is indeed a mistake ;) why would the VM be handled differently ? )
Last thing, maybe you should insist on the download page that 2.0 REQUIRES a pharo specific VM. Not sure I would have read it, but then it would be entirely my fault.
Nicolas
Or... for 2.0 Beta and 2.0 Release provide only a one-click package. If anyone wants just the image, they can get it from the CI server.