2015-12-08 10:29 GMT+01:00 Denis Kudriashov <dionisi...@gmail.com>: > > 2015-12-08 10:16 GMT+01:00 Thierry Goubier <thierry.goub...@gmail.com>: > >> Wishfull thinking: >> >> you have a tradeoff when you do that, you interrupt running code and so >> changes timings and synchronisations, your scan takes time, and things >> below your sampling frequency are not visible. >> >> That being said, and if you take those factors into account, then your >> approach is sound. Just don't say it is a miracle solution. >> > > Yes, of course. I mean that such approach should not has so big impact on > performance as direct announcing inside loop. Most time it will spend on > updating/drawing progress bar. And it is not comparable to time which > required to scan call chain. In most cases call chain has very small deep. > And retrieving information about progress looks like trivial operation. > Besides this analysing happens only when track process wake up. So It gives > seconds to run code without interruption. >
Hum you give interesting insights into it, like that the call chain isn't very deep. Good to know :) > > I will try find code. But it was not ready to use solution. Just very > little experiment for my UI framework Presenty. > It could be very nice to have for many long-running computations. I think the models used by Serge in SciSmalltalk / Kendrick? could benefit a lot from that. Thierry
