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

Selecting objects is not smooth #557

Closed
arjxn-py opened this issue Nov 4, 2024 · 8 comments · Fixed by #569
Closed

Selecting objects is not smooth #557

arjxn-py opened this issue Nov 4, 2024 · 8 comments · Fixed by #569
Assignees
Labels
bug PR that fixes a bug
Milestone

Comments

@arjxn-py
Copy link
Member

arjxn-py commented Nov 4, 2024

Sometimes even after clicking on an object 2-3 times the objects are not selected.
Potentially related to #542

@arjxn-py arjxn-py added the bug PR that fixes a bug label Nov 4, 2024
@arjxn-py arjxn-py added this to the 3.0.0 milestone Nov 4, 2024
@SylvainCorlay
Copy link
Member

I think that the system often confuses a simple 'click' with a 'click and hold'.

@arjxn-py
Copy link
Member Author

arjxn-py commented Nov 5, 2024

I think that the system often confuses a simple 'click' with a 'click and hold'.

Currently the very next click after panning is disabled, so when we want to select but it is also very likely that a very small panning/mouse movement has happened while or before clicking - it is leading one to click 2-3 or more times to select the object
We'll be on it how we can carve the logic to be smoother :)

@martinRenou
Copy link
Member

Yeah it looks like my PR #542 is not handling that correctly in some cases.

@SylvainCorlay
Copy link
Member

Yeah it looks like my PR #542 is not handling that correctly in some cases.

It does not seem to be a question of time between the mousedown and mouseup, but rather than any (tiny) change of mouse position between when the mouse button is pressed and release prevents it to be considered as a click.

@martinRenou
Copy link
Member

martinRenou commented Nov 6, 2024

any (tiny) change of mouse position between when the mouse button is pressed and release prevents it to be considered as a click

That's exactly what the implementation does in #542

Maybe we should count the number of pixels it has moved, and if it's less than a small amount of pixels (say 4), we consider it's a click.

@martinRenou
Copy link
Member

Maybe we should count the number of pixels it has moved, and if it's less than a small amount of pixels (say 4), we consider it's a click

I'm not even convinced this is the only issue though.

There seems to be a wrong order of events that breaks the logic introduced in #542

@arjxn-py arjxn-py self-assigned this Nov 6, 2024
@arjxn-py
Copy link
Member Author

arjxn-py commented Nov 6, 2024

Assigned this to myself to give a try (I might just be shooting in the dark at first 😅)

@martinRenou
Copy link
Member

martinRenou commented Nov 6, 2024

Adding a note that the introduction of the transform controls for object now brings another point of complexity.

The transform controls deselects the selected object after transform. We should try to prevent that.

The mambo-jambo with all those events is starting to get very difficult to track this clicking behavior. We need to think of a robust approach for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug PR that fixes a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants