-
Notifications
You must be signed in to change notification settings - Fork 207
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
Up/Down Arrow Within Value Fields Resets to End When Keyframe Added #5335
Comments
There's another "jump to the end" behaviour when the number of integer digits decrease on the plug. It'd be worthwhile addressing this at the same time.
|
ericmehl
added a commit
to ericmehl/gaffer
that referenced
this issue
Jun 28, 2023
Previously, incrementing an animated numeric plug with the keyboard up / down keys would always reset the cursor to the end of the number. There also were intermittent "---" values appearing in the value when drag-changing the plug. This seems to come from `PlugValueWidget.__updateFromValuesInBackgroundPreCall()` where the value is set to `[]` before setting the real value. Fixes GafferHQ#5335
ericmehl
added a commit
to ericmehl/gaffer
that referenced
this issue
Jul 5, 2023
Previously, incrementing an animated numeric plug with the keyboard up / down keys would always reset the cursor to the end of the number. There also were intermittent "---" values appearing in the value when drag-changing the plug. This seems to come from `PlugValueWidget.__updateFromValuesInBackgroundPreCall()` where the value is set to `[]` before setting the real value. Fixes GafferHQ#5335
ericmehl
added a commit
to ericmehl/gaffer
that referenced
this issue
Jul 6, 2023
Previously, incrementing an animated numeric plug with the keyboard up / down keys would always reset the cursor to the end of the number. There also were intermittent "---" values appearing in the value when drag-changing the plug. This seems to come from `PlugValueWidget.__updateFromValuesInBackgroundPreCall()` where the value is set to `[]` before setting the real value. Fixes GafferHQ#5335
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: Gaffer 1.2.7.0-linux
Third-party tools: None
Third-party modules: None
Description
It appears as if the up/down arrow functionality to adjust values in different input fields is currently broken if one sets a keyframe.
Upon pressing up/down arrow, the cursor/input location will be flung to the end of the value.
This stops artists from using the up/down arrow functionality on numerical values if a keyframe is added since the cursor will always jump to the end.
Steps to reproduce
OSL/Surface/Constant
Set Key
to the numeric valueThe text was updated successfully, but these errors were encountered: