-
Notifications
You must be signed in to change notification settings - Fork 31
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
[QGIS] Snapping on invisible feature #193
Comments
Hi @dsavary
For unchecked classes, that would make sense not to have a snapping index. For the others, we'll need to discuss this largely with the community. |
I tested with QGIS 2.99 3 week ago. The bug is still not fixed. |
Ok, this case is probably an issue. Let's raise the issue on the mailing list. |
About snapping in QGIS 3 QGEP/QGEP#330 |
For Lausanne, this issue is important. In the priority, it should be fix for QGIS 3.0 , ideally for QGIS 2.18 LTR if it's still possible. I don't understand the use cases where you would snap the new feature to invisible features on the map ... |
ticket created upstream https://issues.qgis.org/issues/16838 My guess is that the whole snapping workflow deserves something consistent. |
@dsavary backporting a change to 2.18 seems not possible according to @wonder-sk, it's a little bit more than only a bugfix.
|
IMHO, Snapping on invisible features is a feature. Removing it completely would be wrong. I suggest to set it optionnal in the same way that snapping on intersections is optionnal. Default could be set to visible only. |
@wonder-sk Hi Martin, |
@wonder-sk Hi in case you had some time left, We are out of budget for 2017. Would you be interested in that for 2018 ? |
Sorry for the delayed response... Sure we can do it in 2018 if you are interested in this feature. |
@wonder-sk well, let's keep that in standby that until I get a clearance for the 2018 actions. Any time estimate on that task? |
Cool... My estimate for this is ~2 days |
We have an external contributor funding that fix. Work starting soon, thanks! |
Good news ! planned for QGIS 3.1 (2018) ? I think not for QGIS 2.18 :) ... |
Planned for 3.2. 2.18 was investigated by Martin and needed API changes >> NoGO |
@lbartoletti hub cleanup, I assign you to the task you are already working on |
PR Merged qgis/QGIS#6750 |
Please keep it opened until we have a green light from the testers :) |
Could be closed now? |
The main bug was fixed one year ago. I fixed a related bug for tracing. FYI, there is a last related bug qgis/QGIS#26733 Do you want me to take care of it? |
are you talking to me? ;-) Please go ahaed and close qgis/QGIS#26733 and #193 if everything is OK: |
In QGIS, we can snap on invisible features even if the snapping options have been defined as "snap on all visible layers". The snapping options don't take into accoount the layer style.
Will this be fixed for QGIS 3.0 ?
Démo GIF : https://share.oslandia.net/public/b91c8e
The text was updated successfully, but these errors were encountered: