Thanks a lot for all the hard work, Camillo. You are improving Pharo a lot - often by just doing the hard work on your own. All these UX improvements are the icing on the internal cleanups.
On 06 Dec 2012, at 13:05, Camillo Bruni <[email protected]> wrote: > I promised to fix my partial refactoring for the ProgressBar. > Finally this evening I hacked on the whole progress mess :), now I am almost > done with one little bug left. > > - the progress bar is always responsive > - all processes showing a progress with priority <60 can be interrupted > - refreshes periodically 16 times per second > - only forces a manual refresh when blocking the UI > - no more out of bounds progress bars > - no more ugly display buffer pattern when resizing the screen during a > running progress > > this is a massive improvement for me :) For instance now you can simply > interrupt the test runner > with a click on the progress bar. > > I have one bug left, that is when I run the test runner, the UI event > handling gets > somehow disturbed. Windows no longer receive events, but everything is > directly forwarded > to the World. Opening the World menu is the only thing you can do :/ > > > Anyone has a clue? The slice is in the inbox, see issue > > http://code.google.com/p/pharo/issues/detail?id=7103 > > > best > cami
