Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Fix editing of transform component values in spinbox #7942

Merged
merged 2 commits into from
Sep 18, 2024

Conversation

lassoan
Copy link
Contributor

@lassoan lassoan commented Sep 18, 2024

In Transforms module, when rotate-first mode was enabled and edited translation components and the number of digits changed, the value that was being edited was reset. The problem was that when number of digits change then sibling widgets get a notification and they update their number of digits, too, which results in value change, which leads to resetting of all values (including the one that is being edited). Fixed by preventing resetting of the slider+spinbox for the axis that is being edited using the spinbox.

fixes #7574


Draft pull request because it requires merging of commontk/CTK#1219
required CTK update was merged and git hash is updated in this pull request

@lassoan lassoan added this to the Slicer 5.7 milestone Sep 18, 2024
@lassoan lassoan requested a review from pieper September 18, 2024 04:27
@lassoan lassoan self-assigned this Sep 18, 2024
@jcfr jcfr added the Type: Bug Something isn't working correctly label Sep 18, 2024
pieper
pieper previously approved these changes Sep 18, 2024
Copy link
Member

@pieper pieper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Contains a single additional commit:

Revision: 76e21221f81a4483d58f99a4d63d76f13718fb57
Author: Andras Lasso <[email protected]>
Date: 2024-09-18 10:50:22 AM
Message:
ENH: Add method to check if double-spinbox value is being edited (Slicer#1219)
In Transforms module, when rotate-first mode was enabled and edited translation components and the number of digits changed, the value that was being edited was reset.
The problem was that when number of digits change then sibling widgets get a notification and they update their number of digits, too, which results in value change, which leads to resetting of all values (including the one that is being edited).
Fixed by preventing resetting of the slider+spinbox for the axis that is being edited using the spinbox.

fixes Slicer#7574
@lassoan lassoan force-pushed the fix-transform-editing-via-spinbox branch from 3e59d26 to 71abfd4 Compare September 18, 2024 16:49
@lassoan lassoan marked this pull request as ready for review September 18, 2024 16:50
@lassoan lassoan enabled auto-merge (rebase) September 18, 2024 16:51
@jcfr
Copy link
Member

jcfr commented Sep 18, 2024

required CTK update was merged and git hash is updated in this pull request

For future reference, see commontk/CTK@627842c...76e2122

@jcfr
Copy link
Member

jcfr commented Sep 18, 2024

I am building & testing locally ⏳

@jcfr
Copy link
Member

jcfr commented Sep 18, 2024

Local testing was ✅

Improvement of ci.yml to avoid failure like the one reported here will be suggested in a follow-up pull request.

In the meantime, I will bypass the check and move forward with the integration 🚀

@jcfr jcfr disabled auto-merge September 18, 2024 21:18
@jcfr jcfr merged commit 4a1a83d into Slicer:main Sep 18, 2024
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working correctly
Development

Successfully merging this pull request may close these issues.

Editing Decimal Values in Transform Fields Causes Introduction of Negative
4 participants