Follow-up from "fix(ui): deadlock when exporting transfer function"
The following discussion from !781 (merged) should be addressed:
-
@aancel1 started a discussion: (+2 comments) Ok, this is a bit strange and probably a byproduct of using locks with the previous VTK-like model.
So if I understand well, what is being done is alock
to set the input then re-lock again when the actual write is happening in theupdate()
method ?
Wouldn't it be better to pass the originalm_currentTF
object and let the update handle the lock ? This would prevent requiring the lock here.
This can be of course solved as an issue as it expands the scope of the fix