Camillo I do not know.
Now I will have a look at your change because I was also fixing a bit the
progressBar class. Removing some useless methods
and I grouped all the job class under
kernel-job
and progressbar under
morphic progress bar because I was fed up to see them in process and
system support mixed with other.
> 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.\\
Cool you are addicted!
> - 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.
Did you check that it works with 1 to: 1 because in the past I got a zeroDivide
> 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
