-
Notifications
You must be signed in to change notification settings - Fork 124
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
38063 sample transmission calculators DoubleSpinBoxes avoid commas #38247
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this.
I had a quick play around and it does seem to behave slightly differently when you use ,
instead of .
- say I want to set a value of 1.35
, if I type 1,35
the spin box is updated to 1.3
(i.e. misses the last digit). I wonder if that's because it editing mode if changed? can you reproduce this?
Could you try validating/cleaning the input after this slot instead (from the base class)?
https://doc.qt.io/qt-6/qabstractspinbox.html#editingFinished
It might not work...
Also thanks for fixing the coverity issues on |
Thanks for the review! After observing that handling with |
Description of work
Under
Single
wavelength mode, the spin boxes forLow
,Width
, andHigh
in the Sample Transmission Calculator interface had allowed its spin boxes to enter values such as 0,2.1 to include a blend of commas and decimal dot and this work is to avoid that.In addition, this includes fixing two coverity issues in RotateSampleShape.cpp
Summary of work
Fixes #38063.
Fixes #38268
Further detail of work
To test:
Low
,Width
, andHigh
fields ex: 2,3Reviewer
Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.
Code Review
Functional Tests
Does everything look good? Mark the review as Approve. A member of
@mantidproject/gatekeepers
will take care of it.Gatekeeper
If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.