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

Snapping not possible in new project with new layer #32969

Closed
Bernd-Vogelgesang opened this issue Nov 20, 2019 · 13 comments
Closed

Snapping not possible in new project with new layer #32969

Bernd-Vogelgesang opened this issue Nov 20, 2019 · 13 comments

Comments

@Bernd-Vogelgesang
Copy link

@Bernd-Vogelgesang Bernd-Vogelgesang commented Nov 20, 2019

When opening a new project and adding an existing or creating a new layer, it is not possible to snap to existing features while digitizing, no matter which snapping options are chosen.

The only way to get snapping activated is saving the project and restarting QGIS.

QGIS version 3.11.0-Master QGIS code revision 129165a
Compiled against Qt 5.9.5 Running against Qt 5.9.5
Compiled against GDAL/OGR 2.4.2 Running against GDAL/OGR 2.4.2
Compiled against GEOS 3.7.1-CAPI-1.11.1 Running against GEOS 3.7.1-CAPI-1.11.1 27a5e771
Compiled against SQLite 3.22.0 Running against SQLite 3.22.0
PostgreSQL Client Version 10.10 (Ubuntu 10.10-0ubuntu0.18.04.1) SpatiaLite Version 4.3.0a
QWT Version 6.1.3 QScintilla2 Version 2.10.2
Compiled against PROJ 5.2.0 Running against PROJ Rel. 5.2.0, September 15th, 2018
OS Version Linux Mint 19.2 This copy of QGIS writes debugging output.
Active python plugins joinmultiplelines; OSMDownloader; quick_map_services; qNote; processing_saga; QNEAT3; processing_r; MemoryLayerSaver; refFunctions; ClusterPoints; db_manager; processing
@gioman

This comment has been minimized.

Copy link
Contributor

@gioman gioman commented Nov 20, 2019

I just tested on master on a clean Windows installation and I can't confirm.

@denchat

This comment has been minimized.

Copy link
Contributor

@denchat denchat commented Dec 30, 2019

Confirm this #33553

QGIS and OS versions
3.11.0-43 (OSGeo4W) 64-bit 578f32a
Windows 10 64-bit

QGIS version 3.11.0-Master
Compiled against Qt 5.11.2
Compiled against GDAL/OGR 3.1.0dev
Compiled against GEOS 3.8.0-CAPI-1.13.1
Compiled against SQLite 3.29.0
PostgreSQL Client Version 11.5
QWT Version 6.1.3
Compiled against PROJ 6.3.0
OS Version Windows 10 (10.0)
QGIS code revision 578f32a9b6
Running against Qt 5.11.2
Running against GDAL/OGR 3.1.0dev
Running against SQLite 3.29.0
SpatiaLite Version 4.3.0
QScintilla2 Version 2.10.8
Running against PROJ Rel. 6.3.0, January 1st, 2020
This copy of QGIS writes debugging output.
@denchat

This comment has been minimized.

Copy link
Contributor

@denchat denchat commented Dec 30, 2019

It affects only

  • memory layers.
  • newly created layers.
  • all zero-counted feature layers. In this case, there is a workaround by "unzeroing" (create a feature and reopen project)
@denchat

This comment has been minimized.

Copy link
Contributor

@denchat denchat commented Jan 2, 2020

I can confirm that complete purging the user folder
%AppData%\QGIS
or a fresh installation on the machine both fixes this issue.

*** Or just renaming old QGIS folder is better. This way you can always restore to retrieve what you forget. ***

I guess this can be closed in some degree.

Anyway I'm not sure taking this workaround is the way to go. Because there will be most users migrate directly from v3.10.1 to v3.11.0 on the next three weeks. I'm not sure this will affect how much proportion of users.

Purging %AppData%\QGIS seems not to be working still.

@denchat

This comment has been minimized.

Copy link
Contributor

@denchat denchat commented Jan 3, 2020

@gioman

I just tested on master on a clean Windows installation and I can't confirm.

Follow these steps to see whether you can reproduce with fresh installation:-

  1. New project
  2. Create 2 polygon memory layers
  3. Turn on snapping all layers
  4. See whether both layers can snap to one another.
@gioman

This comment has been minimized.

Copy link
Contributor

@gioman gioman commented Jan 3, 2020

See whether both layers can snap to one another.

they do, I have tested on 3.10.1 (not master) on Linux.

@denchat

This comment has been minimized.

Copy link
Contributor

@denchat denchat commented Jan 3, 2020

@gioman

they do, I have tested on 3.10.1 (not master) on Linux.

If you still have access to master on a clean Windows installation, please try it again with those 2 memory layers.

@gioman

This comment has been minimized.

Copy link
Contributor

@gioman gioman commented Jan 3, 2020

If you still have access to master on a clean Windows installation, please try it again with those 2 memory layers.

@denchat it works as expected.

@denchat

This comment has been minimized.

Copy link
Contributor

@denchat denchat commented Jan 4, 2020

@gioman

it works as expected.

Other than %APPDATA%\QGIS, where else can I delete remnants of previous installed QGIS to simulate a fresh installation?

@denchat

This comment has been minimized.

Copy link
Contributor

@denchat denchat commented Jan 13, 2020

@gioman Please test this file to see whether or not node tools and snapping tools work on memory layers?

test.zip

@gioman

This comment has been minimized.

Copy link
Contributor

@gioman gioman commented Jan 14, 2020

@gioman Please test this file to see whether or not node tools and snapping tools work on memory layers?

@denchat works as expected. Please not that in the project you attached snapping was not active.

@denchat

This comment has been minimized.

Copy link
Contributor

@denchat denchat commented Jan 19, 2020

OSGeo4W QGIS 3.11.0-59 Nightly seem not to have this issue.

You may close this.

@troopa81

This comment has been minimized.

Copy link
Contributor

@troopa81 troopa81 commented Jan 20, 2020

Duplicate of #33449

@troopa81 troopa81 marked this as a duplicate of #33449 Jan 20, 2020
@troopa81 troopa81 closed this Jan 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.