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.

Sign up for GitHub

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

Jump to bottom

Regression: Hard to drag constraint labels #405

Closed
rpavlik opened this issue May 15, 2019 · 4 comments
Closed

Regression: Hard to drag constraint labels #405

rpavlik opened this issue May 15, 2019 · 4 comments
Labels
duplicate

Comments

@rpavlik
Copy link
Contributor

rpavlik commented May 15, 2019

System information

SolveSpace version: 3.0~201e15e6

Operating system: Debian testing/buster

Expected behavior

When I hover over a newly-added constraint label (like a distance or an angle) and it turns color, I should be able to click and drag to move. (And could, in 2.3)

Actual behavior

I typically can't, at least not without zooming in or out. I think this is worse when the constraint happens to be near the origin, but not 100% sure. It's been this way on master for some time - since my earlier PR.

Additional information

Here's the file I used in the screencast below - add an angle constraint to the tip of the slot sketch group. Sometimes it works, sometimes it acts up.

sample.zip

Screencast showing two attempts: the first one, I was able to zoom a bit and get it to drag eventually. The second clip, I couldn't get it to drag no matter what I did.

slvs trouble dragging constraints.zip
@whitequark
Copy link
Contributor

Is this a duplicate of #161 ?

@rpavlik
Copy link
Contributor Author

rpavlik commented May 15, 2019

Hmm. Possibly - wonder if the fact that I can't move the origin is why clicking and dragging on a near-origin constraint causes failure. I'll pay attention and see if I can figure it out better.

@whitequark
Copy link
Contributor

Actually, I think it's a duplicate of #174.

@whitequark whitequark added this to the 3.0 milestone May 24, 2019
@rpavlik
Copy link
Contributor Author

rpavlik commented May 24, 2019

ah, yeah, that matches better, Sorry for missing the dupe.

@whitequark whitequark removed this from the 3.0 milestone May 24, 2019
@ruevs ruevs mentioned this issue Apr 5, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@whitequark @rpavlik