[GRASS-dev] [bug #2969] can wxPython GUI handle order of options for v.type and alike?

[Maciej Sieczka]

Hamish wrote:
> Maciej Sieczka wrote:
>> Hamish wrote:
>>> Maciej Sieczka wrote:
>>>> Is:
>>>>
>>>> $ v.type from=point to=centroid; v.type from=line to=boundary;
>>>>
>>>> as fast as:
>>>>
>>>> $ v.type type=point,centroid,line,boundary
>>>>
>>>> ?
>>> No. But it's a very quick operation, so twice as long is still not
>>> very long.
>> ???
>>
>> This is a regression. If I was to suggest something I'd suggest
>> reverting this change.
> 
> 
> two points:
> 
> 1) this hasn't been enacted anywhere in the (active) code. This is
> just proposal/preparation for GRASS 7. v.type in 6.3 still does type=,,,

Yes I know.

> 2) It is a balance of cost vs benefit. To me, clarity and ease of use
> is more important than ability to do two things at once. The speed hit
> is minimal (I expect you could retype a massive 1 million point LIDAR
> map in a second or two);

OK. So we need a benchmark. Will the:

$ v.type type=point,centroid,line,boundary
$ v.type type=point,centroid; v.type type=line,boundary

on 1 mln vector fetures suffice to draw conclussion?

Will do in the afternoon if so. Now have to run to work :).

Maciek