# LineProfile : following proportional distance PR

**URL:** <https://discourse.slicer.org/t/lineprofile-following-proportional-distance-pr/14219>\
**Category:** Development\
**Created:** [October 24, 2020, 7:12am UTC](https://discourse.slicer.org/t/lineprofile-following-proportional-distance-pr/14219 "2020-10-24T07:12:01Z")\
**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:** [October 24, 2020, 7:12am UTC](https://discourse.slicer.org/t/lineprofile-following-proportional-distance-pr/14219/1 "2020-10-24T07:12:01Z")

</div>

@lassoan

Following commit and merge of that [PR](https://github.com/PerkLab/SlicerSandbox/pull/7), an inconveniant behaviour of the ‘Apply button’ appeared by introducing

self.applyButton.checkBoxControlsButtonToggleState = True

It seems to be a [desired](https://github.com/Slicer/Slicer/issues/4717) button behavior.

The check status of the checkbox controls the state of the toggle button. The problem is that whenever the button is clicked, the checkbox always gets unchecked. The button is no longer a toogle button (as it was before), but a simple button.

Now we can all live with that. Just in case you might deem it useful to restore back the previous parameter of the ‘Apply button’.

Thanks to the commit and its optmization.

---

<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:** [October 24, 2020, 1:10pm UTC](https://discourse.slicer.org/t/lineprofile-following-proportional-distance-pr/14219/2 "2020-10-24T13:10:25Z")

</div>

This how all the checkable pushbuttons work in Slicer when they control manual/automatic update. The problem with the previous behavior was that users were confused when the button was in a contradicting state: having the checkbox checked but the button not being pressed.

The current behavior avoids this possibility of misunderstanding and you can always enable auto-update the same way, with a single click (clicking on the checkbox).