digitizing become very slow when a (fair big) underlying vector has snapping activated

[lutra]

I believe that this is replicable with a sample data of yours, but in case you are not able to reproduce just ask and I'll attach a sample.

Steps:

add a polygon layer, with a fair big number of features and enable snapping for it.

then add another polygon layer or create a new one.

start editing the new polygon layer, you'll notice that the "capture polygon" tool is pretty slow. Depending on how big is the underlying layer it can be almost unusable.

remove the snapping for the underlying layer and editing the new polygon will work just fine

tested under trunk/1.4 under both linux and windows

[gespiel]

Create a spatial index on the big layer and it works fine (Layer properities, General, Button "Create Spatial Image". see ticket #1277

[jef]

Replying to gespiel:

Create a spatial index on the big layer and it works fine (Layer properities, General, Button "Create Spatial Image". see ticket #1277

sounds like a solution.