I really think that for the process of polishing 2.0 from beta to release we need a new label for issues.
Bugs like the one below are really important, they might be silly or easy to fix, but they leave a bad impression. We want as many people as possible to help, but UX failures like this will scare away many users, most won't be as helpful as Andy to even report the issue. We as developers know that 2.0 is OK because we use it every day, but occasional users who just try 2.0 for the first time can't know that. So not HorribleErrorBlockingEverything but maybe HorribleUXQualityBugScaringAwayNormalPeople as label ? Sven On 23 Jan 2013, at 02:43, Camillo Bruni <[email protected]> wrote: > that is/was a bug: > > https://code.google.com/p/pharo/issues/detail?id=6608 > > looks like it is still there in a newer image! > > On 2013-01-23, at 02:05, Andy Burnett <[email protected]> wrote: > >> I am running the Pharo 2.0 beta, and I am getting a lot of System Error >> Handling Failed events. Is this simply a product of the beta status, or >> have I somehow enabled some kind of debug switch? >> >> For example, in a workspace I execute a doit on: >> >> fd := FileDialogWindow new. >> fn := fd openInWorld. >> >> When I click OK in the dialog box, I get the System Error screen. On other >> occasions I get the screen, press space to continue, then I get the debug >> window, and when attempting to debug it bounces me back to the System Error >> screen. >> >> Normal behaviour for the beta, or operator error on my part? >> >> Cheers >> Andy -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
