https://bugs.kde.org/show_bug.cgi?id=409580
vialav <d...@bk.ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO |FIXED
--- Comment #3 from vialav <d...@bk.ru> ---
Thank you, yes, the behaviour has definitely improved under both Pythons 2/3.
There is no crash either if I interrupt the backend prematurely, as it has been
the reported case (see also below), or after auto-moving the data to the
Variable Manager window has been finalized.
There is a lag, indeed, between closing the VTK/Mayavi window and Cantor
returning to its original readiness, which I had wrongly assumed as a hang on
'Calculating…'. If I had waited for longer, possibly, I wouldn't have hit the
present bug :)
Auto-reloading the Var Manager, also upon walking over the tabs, contributes to
a lag, especially with such big data, see to this my comment in Bug 409520 #3
in the past. There may be a room for rethinking the Var Manager implementation,
as a suggestion.
Closing as resolved, and thank you for looking into this matter.
--
You are receiving this mail because:
You are watching all bug changes.
