-
Notifications
You must be signed in to change notification settings - Fork 595
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
Draw should not interfere with dragPan.disable() #1216
Conversation
…hen direct_select has disabled it
…hen direct_select has disabled it
@stepankuzmin PTAL :D |
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.
Looks good to me, thanks for the contribution @itoxiq 👍
@itoxiq @stepankuzmin hey guys, after clicking the same feature multiple times without moving the mouse, doesn't it happen to you that dragPan remains disabled, regardless of whether it was initially enabled? I just updated to version 1.5.0, and this issue started happening. E.g.: If you manage to fire 2 consecutive startDragging, any stopDragging after that won't turn on the dragPan again EDIT: Created this issue: #1328 |
Continuation of #1191
The issue is that Draw assumes that dragPan is enabled and simply enables it without question after certain operations (when dragpan is temporarily disabled). This change would set a variable called initialDragPanState and only re-enables when it was originally enabled.