[Qgis-developer] Digitizing behavior

[Matthias Kuhn]

Agreed,

There is no order promissed by the iterators (and if there was, there
should be a explicitly stated z-index / an ORDER BY clause specified to
the iterator).

But if these patches make the usage feel more natural, I think they
should be applied. As they affect a rather central part of QGIS, a
review would be much appreciated.

Matthias


On 08/20/2013 11:47 AM, Jürgen E. Fischer wrote:
> Hi Salvatore,
>
> On Mon, 19. Aug 2013 at 23:48:16 +0200, Salvatore Larosa wrote:
>>    I'm noticing that while digitizing a new feature which overlaps another,
>>    the latter is at the top although I expect to see it at the bottom, so the
>>    new feature should overlap to the existent one.
> IMHO the render order should be considered arbitrary. The provider doesn't
> return the features in a particular order later anyway.
>
> Currently (w/o Matthias patch) while the layer is edited feature with changed
> geometries are rendered first (ie. bottom), then added features and then
> features from the provider (- those that are going to be deleted).
>
> I don't think that this must be changed.  If a layer can have overlapping
> features, it probably should be configured to show them transparently already.
>
>
> Jürgen
>