Bug report #7353
Snapping is always on in current master
|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 #:||16330|
In current master (2c4ac08 from 2013-03-13) snapping is always active, even it is turned off in the snapping options.
#3 Updated by Andreas Neumann over 6 years ago
Things are even worse:
once I start changing snapping settings - I cannot digitise anymore - I always get the error message:
Could not snap segment - did you set the snap tolerance in Settings > Project Settings > General?
So - there seems to be something quite messed up with snapping currently.
#5 Updated by vinayan Parameswaran over 6 years ago
- snapping is on even though the settings->snapping option is not checked for the layer when qgis starts up.
- if you just click the apply without changing anything snapping is really disabled.
- From then on, everything works as normal
#9 Updated by Andreas Neumann over 6 years ago
hm - but there is no way to disable snapping by default.
In "Options" one can only set the default snap mode, the snapping tolerance and search radius. No way to turn it on/off globally.
Also - if it were turned on by default - the snap option dialogue needs to indicate that by having the checkbox turned on - but it is turned off. So it seems the checkboxes are out of sync with the setting.
I do not think the current behaviour is satisfying.
#11 Updated by Andreas Neumann over 6 years ago
- Status changed from Closed to Reopened
Thank you for working on this problem.
I can see the Default Snap Mode "Off" option now - this is good.
However, if this option is on (e.g. vertex), and a user adds a new layer, the snapping is on (correct) but shown as "off" in the snapping options dialogue (incorrect). So this part of the bug is not yet fixed. The disconnectedness of the Snapping options dialogue. This dialogue should always reflect the current state - but it doesn't. Do you understand my problem?
I re-opened the bug therefore again. Or should I open a new bug?