Bug report #5318
Snapping options dialog broken
Status: | Closed | ||
---|---|---|---|
Priority: | High | ||
Assignee: | - | ||
Category: | Vectors | ||
Affected QGIS version: | master | Regression?: | No |
Operating System: | Easy fix?: | No | |
Pull Request or Patch supplied: | No | Resolution: | |
Crashes QGIS or corrupts data: | No | Copied to github as #: | 15021 |
Description
When accessing the snapping options menu, the vector layers from the project are not shown in the dialog so I cannot set up snapping.
A project that I set up yesterday with snapping turned on still recognises the snapping options that were set up, I just cannot edit them.
See attached screenshot.
QGIS Master Windows 7 64bit
Associated revisions
Remove/Add layers to snapping dialog. Fixes #5318
History
#1 Updated by Giovanni Manghi over 12 years ago
- Target version set to Version 1.8.0
- Subject changed from Setting up snap not possible to Snapping options dialog broken
- Category set to Vectors
- Priority changed from Normal to 6
Confirmed also on linux. No layers do show in the "snapping options" dialog.
#2 Updated by Nathan Woodrow over 12 years ago
- Assignee set to Jürgen Fischer
#3 Updated by Jürgen Fischer over 12 years ago
- Assignee deleted (
Jürgen Fischer)
#4 Updated by Nathan Woodrow over 12 years ago
I found what has caused this. Tim made a commit that added layersAdded and layersRemoved to the MapLayerRegistry which are the new signals.
Working on a fix now.
#5 Updated by Salvatore Larosa over 12 years ago
Nathan Woodrow wrote:
I found what has caused this. Tim made a commit that added layersAdded and layersRemoved to the MapLayerRegistry which are the new signals.
Working on a fix now.
Is this also related to that commit?
Warning: Object::connect: No such signal QgsMapLayerRegistry::layersAdded( QgsMapLayer * ) Warning: Object::connect: (receiver name: 'MainWindow') Warning: Object::connect: No such slot QgisApp::removingLayer( QString ) Warning: Object::connect: (receiver name: 'MainWindow')
I get that when I start QGIS!
#6 Updated by Nathan Woodrow over 12 years ago
I suspect so
#7 Updated by Nathan Woodrow over 12 years ago
- Status changed from Open to Closed
Fixed in changeset a82a2438e1b9bb4656d2a63ef21800d1d2a01ff2.