-
Notifications
You must be signed in to change notification settings - Fork 61
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
ROAM 3 - Making it more obvious when cursor is within snapping radius #469
Comments
Yeah I haven't addressed this one yet. WIll do it in the next release.
Just had to make 3.0.6 low impact release until we have more testing done
on it.
…On Fri, Sep 25, 2020 at 11:45 AM she-weeds ***@***.***> wrote:
Just by way of an update this is still an issue with ROAM 3.0.6 regardless
of device, this is a screenshot taken from a desktop computer:
[image: snapping]
<https://user-images.githubusercontent.com/41975056/94217104-85fbd200-ff24-11ea-8787-1ecb261552c7.gif>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#469 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC5FXH766GNNVA34KWDOJDSHPY2XANCNFSM4Q5YQUTA>
.
|
Thanks Nathan, totally understand the need to get something working out first. Snapping visibility is not a huge deal at this point in the grand scheme of things. Looking forward to testing out subsequent releases, thanks for keeping Roam going all these years. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Updated because I tested a bit more and realised what was happening. This is in Roam 3.0 beta 3.
The issue is that you can't turn snapping off regardless of toggling it in ROAM.
One consequence is the display of the blue halo (normally indicating cursor within snapping radius) is on the whole time, then turns off after the first feature is digitised, until the form is selected again.
I'm guessing this is just part of ongoing work to connect with way snapping was overhauled in QGIS 3. Disregard if this is currently being worked on...
The text was updated successfully, but these errors were encountered: