-
-
Notifications
You must be signed in to change notification settings - Fork 468
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
add option to disable keyboard focus being set on mouse move #1174
add option to disable keyboard focus being set on mouse move #1174
Conversation
currently all mouse events get forwarded to onRenderWindowMouseEvents, there keyboard focus is requested (setFocus) unconditionally. This commit adds a new property "focus_on_mouse_move_" that enables setting keyboard focus on mouse move events. Setting focus on click or wheel is handled by QObject::setFocusPolicy Subclasses/Users of rvis::RenderPanel can disable either setting focus on mouse move by using the boolean property and disable keyboard focus on click, on wheel or totally via setFocusPolicy
ping? |
thanks for the PR, we'll take a look at it as soon as possible |
Since this is an ABI breaking change I had to target to the |
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.
The change looks reasonable to me.
@simonschmeisser if you want/need this in |
@wjwwood thanks for merging it to melodic. I'm fine that way. We will upgrade asap anyway and have a workaround for the time being |
currently all mouse events get forwarded to onRenderWindowMouseEvents,
there keyboard focus is requested (setFocus) unconditionally. This commit
adds a new property "focus_on_mouse_move_" that enables setting keyboard
focus on mouse move events. Setting focus on click or wheel is handled by
QObject::setFocusPolicy
Subclasses/Users of rvis::RenderPanel can disable either setting focus on
mouse move by using the boolean property and disable keyboard focus on click,
on wheel or totally via setFocusPolicy