On 2012-12-06, at 18:14, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
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.
ok, that looks fine :) separate packages should clarifiy things a bit :) Maybe I have time to look into it, today. Otherwise I won't touch the computer for 7 days :P and enjoy the georgious argentinian country side!
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
there should be no more min-max, hence no more 0 divide possible. But yeah, I got a bit lost in fixing the UI part ;) so I still have to do the proper transformations on the rest of the image.