Pushed CTK topic: https://github.com/commontk/CTK/pull/284/files

Kindly review and merge. I can then update the CTK tag to checkout for Slicer.

Pushed additional changes to CTK topic: https://github.com/commontk/CTK/pull/284

This problem is not localized but is widespread to Slicer.
I don't think CTK pull request 0000284 is the correct(unique) solution to this problem.
For instance, it won't help when pressing down the up arrow in the spinboxes (it should increase the value as long as the button is down).
0000284 is not enough as it targets only ctkCoordinatesWidgets.
One should think of a more generic solution.
Here the root of the problem is that:
1) a value is being changed by the user in a spinbox.
1b) the spinbox enters in an "interactive" mode
2) the module is notified
3) the module sets the MRML node property accordingly
4) the node fires a Modified event and the module is notified
5) the module sets the new value to the spinbox.
6) setting the value (sometime slightly different because of some rounding) stops the "interactive" mode of the spinbox ( e.g. a) despite the arrow button being down, it won't trigger any new value change on timer, b) typing a new digit in the spinbox doesn't change the following digit).

We need to think of some generic solution. So far, I can think of:
a) add a custom ctkSpinBox::setValueInteractively(double val ) which tries to not stop the "interactive" mode (to investigate)
b) add a custom ctkSpinBox::setValueIfDifferent(double) which doesn't do anything if the value is the same (or close), this would prevent the interactive mode from being stopped.
c) have a custom ctkSpinBox edition mode that replaces the next digit (same behavior as if "Insert" keyboard key is not active).
There might be other ideas, feel free to post.

@Julien,

Thanks for reviewing.
I gave a little thought to the suggested changes. However, I am not sure if I understand how exactly would the spinbox end the "interactive mode" and why would the module set a new value on the spinbox while the user is entering a value? Shouldn't leaving focus or pressing return key trigger the interactive mode to end?

Pressing either the "up" button or the "down" button emits editingFinished() signal at each increment. I checked the behavior and it seems to work fine with ctkCoordinatesWidget and ctkMatrixWidget.

Hi Guys - any further thoughts on this? Typing new values into these spin boxes is still very confusing...

It's in progress, we are discussing ways of doing it.

Fixed in r22151

Closing resolved issues that have not been updated in more than 3 months