You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: tms13 [Submitted to the original trac issue database at 1.00pm, Sunday, 2nd May 2010]
I'm working on the shapefile importer to read polygons with holes in. I've got it working (and will submit a patch soon), but it's not as useful as I'd like because the multipolygons generated don't get shifted to the dirty layer when Feature/Force Upload is used. I'd expect the relation and all its members to be moved to the dirty layer.
The text was updated successfully, but these errors were encountered:
Author: tms13 [Added to the original trac issue at 11.43am, Monday, 3rd May 2010]
Forgot to mention: the patch also improves performance of commit, because of the log(N) QList<>.contains() call in the inner loop; we now use a much more efficient QSet<> for that. That's why I ripped out the innards entirely. I have to admit, I don't understand what it's doing with the Properties dock - have I maintained the right behaviour there?
Reporter: tms13
[Submitted to the original trac issue database at 1.00pm, Sunday, 2nd May 2010]
I'm working on the shapefile importer to read polygons with holes in. I've got it working (and will submit a patch soon), but it's not as useful as I'd like because the multipolygons generated don't get shifted to the dirty layer when Feature/Force Upload is used. I'd expect the relation and all its members to be moved to the dirty layer.
The text was updated successfully, but these errors were encountered: