15 Sep
2010
15 Sep
'10
11:25 a.m.
I know about this problem. As I understand it goes like this: the custom task somehow
spawns another process besides the rendering, and thus the rendering needs the result.
I do not quite know how to solve this one, but I think we can solve it with the same
effort of adding parallelized rendering in Glamour:
http://code.google.com/p/moose-technology/issues/detail?id=218
It would cool to get some help.
Cheers,
Doru
On 14 Sep 2010, at 17:38, Simon Denier wrote:
Hi
It seems I have some problems to mix progress bars (using MooseCustomTask) and Glamour
browser (it's related to Arki more precisely).
I mean, I select some items in a browser, which then compute lazily their state. Some
long computations are done in a Moose custom task to give feedback. But it gives errors or
incorrect results in Glamour/Arki when it is done this way, generally because some data
are incomplete when the browser is rendering the widget.
I'm puzzled by how this happens, because it seems it should be managed by the UI
thread.
Any hacker willing to take a look at Esug?
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing should have the right to be different."