Track Editor semantics and operation

[roth]

Hi,

I am trying to get acquainted with the track editor to trim workouts
before importing them.

THE COMMANDS

Remove selection
I do understand the semantics of this one: Remove any points selected.
No further question about that one.

Trim selection
I do not understand the semantics of this one. For Trim selection
(without reading the docs) I'd expect to get everything removed
*except for* the selection. This would be great because I select all
what I want to keep, i.e. the actual workaout, then use one single
command (trim) and I am done. However, according to the docs and to
the implementation, Trim selection is essentially the same as remove
selection, just that it (in addition to the selected points) also
deletes further to the nearest end. First, I am not sure whether
"nearest" is meant in terms of remaining data points or actual
distance (in e.g. km) to one or the other end of the recording.
Second, for trimming from either side, I still need two command
invocations. Is there a reason why Trim selection works as it does
now? The difference to Remove selection seems minor, whereas the
semantics of "keep everything selected, trim the rest" would be
actually a time saver feature.


THE IMPLEMENTATION
1) It seems I cannot delete the last point of a recording. When I
select the last data point in my workout and call Remove selection,
nothing is actually removed. Why is this?
I have found the following workaround: To remove the last data point,
I have to select the last two data points, then call Remove selection.
This actually just removes the last data point (not the second-to-last
also selected), giving me the desired result.

2) The same as in 1) holds true for the beginning of the data: To
remove the first data point, one has to select the first two, then
call Remove selection. This makes the formerly second (also selected)
data point the first one.

3) In contrast to 1) and 2), selecting any single data point *except*
for the first or the last one, Remove selection works as expected and
removes that single data point.

Might the behaviour of 1) and 2) be actually just a bug in corner
cases? :-)

cu
Christian

[Wolfgang Berberich]

Hi,

good point. I'll put this on the list. What you describe below about
the trim command is more or less cropping. Might be more what users
expect.

cheers,
- berbie.