# Local threshold : mouse cursor is never restored

**URL:** https://discourse.slicer.org/t/local-threshold-mouse-cursor-is-never-restored/24941
**Category:** Support
**Created:** [August 26, 2022, 7:39pm UTC](https://discourse.slicer.org/t/local-threshold-mouse-cursor-is-never-restored/24941 "2022-08-26T19:39:45Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [August 26, 2022, 7:39pm UTC](https://discourse.slicer.org/t/local-threshold-mouse-cursor-is-never-restored/24941/1 "2022-08-26T19:39:45Z")

</div>

‘Local threshold’ segment editor effect outputs the following in Python console :

```auto
Traceback (most recent call last):
  File "/home/user/programs/Slicer/bin/../lib/Slicer-5.1/qt-scripted-modules/SegmentEditorLocalThresholdLib/SegmentEditorEffect.py", line 242, in processInteractionEvents
    self.apply(ijkPoints)
  File "/home/user/programs/Slicer/bin/../lib/Slicer-5.1/qt-scripted-modules/SegmentEditorLocalThresholdLib/SegmentEditorEffect.py", line 481, in apply
    parameterSetNode.SetMasterVolumeIntensityMask(oldMasterVolumeIntensityMask)
AttributeError: 'vtkSlicerSegmentationsModuleMRML.vtkMRMLSegmentEdi' object has no attribute 'SetMasterVolumeIntensityMask'

```

It seems ‘SetMasterVolumeIntensityMask’ has been removed or renamed. The segmentation completes, but the mouse cursor is never restored.

FYI, hoping for a fix.

Thank you.

---

<div class="post-metadata">

### Author: ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [August 26, 2022, 8:35pm UTC](https://discourse.slicer.org/t/local-threshold-mouse-cursor-is-never-restored/24941/2 "2022-08-26T20:35:42Z")

</div>

Thank you, good catch, that’s due that we missed adding a backward-compatibility method when we changed `master` to `source` for DEI reasons in Slicer-5.1. I’ve [fixed it now](https://github.com/Slicer/Slicer/commit/b4fca2f83af7790c094b877f302c0578b5513298), so the latest Slicer Preview Release (Slicer-5.1) will work well from tomorrow.
