[Qgis-developer] Digitizing behavior

[Andreas Neumann]

 I just tested with a new Shapefile - no difference before and after the 
 save.

 It seems that the newest feature always gets row id 0 and the other 
 features get incremented - this is very odd and against every behavior 
 of other spreadsheets and databases.

 But I am pretty sure that earlier versions did not show this behavior.

 Andreas

 On Tue, 20 Aug 2013 11:10:40 +0200, Denis Rouzaud wrote:
> not sure but to-be-commited features have negative IDs. It might be a
> reason they are rendered first.
>
>
> On 08/20/2013 11:07 AM, Andreas Neumann wrote:
>> Hi Salvatore,
>>
>> I think you described it wrong: the former is on the top and not the 
>> latter. If the latter were at the top it would be more logical and 
>> like the other GIS.
>>
>> I agree that the current QGIS behavior is strange and I wonder why 
>> this happens. Aren't objects rendered by its order in a table unless 
>> there are other rules?
>>
>> Andreas
>>
>> On Mon, 19 Aug 2013 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.
>>>
>>> I was wondering if this was the correct behavior since other GIS
>>> software have a different behavior.
>>>
>>> Do you think we can change this for the upcoming 2.0?
>>>
>>> Best Regards
>>
>> _______________________________________________
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer