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

Use a "text field" cursor for EditorSpinSliders in the animation editor #31620

Closed

Conversation

Calinou
Copy link
Member

@Calinou Calinou commented Aug 24, 2019

This makes them easier to recognize as fields that can be edited.

This makes them easier to recognize as fields that can be edited.
@akien-mga
Copy link
Member

Why do this only for specific controls and not for all input fields though?

Currently EditorSpinSlider seems to use the IBEAM cursor when the text field is clicked. It's the same for all input fields in the inspector and those in the AnimationPlayer editor, so I don't think one should be treated differently from the others.

I'm not against making so that all EditorSpinSlider fields have an IBEAM cursor on hover, though we'd have to make sure that it properly reverts to the normal default cursor when out of bounds.

@Calinou
Copy link
Member Author

Calinou commented Aug 28, 2019

@akien-mga I've tried enabling this for all EditorSpinSliders, but it feels strange when there's a grabber below because the cursor will suddenly switch from CURSOR_IBEAM to CURSOR_ARROW when hovering the grabber.

Maybe this should be done only when set_hide_slider(true) has been called on the EditorSpinSlider? This would still be more "generic" than doing it just for the EditorSpinSliders in the animation track editor.

@akien-mga
Copy link
Member

I don't know, it seems a bit too magic to me if something like this depends on the presence of a slider. The text input field is the same regardless of the presence of the slider, so it would be weird if hovering it produces different behavior.

@aaronfranke
Copy link
Member

@Calinou Is this still desired? If so, it needs to be rebased on the latest master branch. While there are no conflicts, rebasing is important so that reviewers can easily test the PR.

@akien-mga
Copy link
Member

I'm still not convinced that this is a good idea, I don't think those two fields should get special treatment. We could change things in EditorSpinSlider directly if we reach a consensus on what would be better UX.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants