Merged
Conversation
zicklag
force-pushed
the
camera-pan-threshold
branch
from
6e6458a to
cb55df8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It was annoying while using the editor to keep accidentally panning the screen accidentally when I was trying to click the toolbar buttons on the left, so I reduced the camera pan threshold a little bit.
I would actually argue that the camera pan features is actually unnecessary, because you can use the middle mouse button to pan, and if you don't have a three button mouse, a common strategy is to allow you to hold
altorctrlwhile click and dragging.Having the screen start panning around as I move my mouse out of the window to another application and things like that is pretty annoying in my opinion, but it's your guys's call whether or not this is a commonly used or otherwise useful feature.