Skip to content

Topic/avoid separate mouse state #2

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

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

eirikblekesaune
Copy link

Sliders does not update when rotation and tumble is set by mouse event from userView. This change cleans up the design a bit by having the mouse event callback call the model setters instead of the hidden mouse rotation/tumble state.

In order to have the rotation and tumble wrap naturally I have changed the ranges for the rotation and tumble sliders (PointViewRadianCtl instances in PointViewUI.sc.)

@mtmccrea
Copy link
Member

mtmccrea commented Oct 1, 2018

Thanks for looking at this @blacksound, this was on my todo list. I'll have to review some different cases, I remember there were some caveats related to how the mouse interaction behaved while animating. I should be able to get to this in a day or two.

@eirikblekesaune
Copy link
Author

I have a different suggestion with the animation part. Not ready to push yet, but in short you could put the timed cycling outside i a separate routine that calls the model setters and manually refresh the userView.

Will make a PR for that tomorrow.

@mtmccrea mtmccrea force-pushed the master branch 2 times, most recently from d6925f7 to 56dd45f Compare January 10, 2019 04:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants