Oliver,
On Sunday, 2016-11-27 19:47:52 +0100, you wrote:
> ...
> From the user's point of view extensions are not different to the other track
> properties. They will just append the list of the normal ones. Nothing
> special
> to know about them.
But how the specifiable limits affect the
Am Sonntag, 27. November 2016, 14:12:08 CET schrieben Sie:
> Oliver,
>
> On Saturday, 2016-11-26 13:14:33 +0100, you wrote:
> > My experience with novice users is, that they do not expect stuff anywhere
> > at all. They do not search the menus for usefull content. Nor do they
> > look at
Oliver,
On Saturday, 2016-11-26 13:14:33 +0100, you wrote:
> My experience with novice users is, that they do not expect stuff anywhere at
> all. They do not search the menus for usefull content. Nor do they look at
> comboboxes in detail.
While I'm aware that this type of novice user does in
My experience with novice users is, that they do not expect stuff anywhere at
all. They do not search the menus for usefull content. Nor do they look at
comboboxes in detail. Just remember, you asked for colorizing activities and
it was right in front of you nose.
Why are the global settings
Oliver,
On Friday, 2016-11-25 10:44:58 +0100, you wrote:
> ...
> As the buttons are in the track details dialog the selection is for the
> track only.
Erm, except when you change some global default values.
> You can either choose:
>
> * user defined limits or values for this track
>
> *
And what precisely happens, when I specify a track width for "all"
>tracks?
>
> * Is it understood as a default
>
>- just for new tracks?
>
>- for all tracks which don't explicitly specify otherwise?
>
>* Or does it override older track specific
>> And open source does not mean: Everybody wishes and one has to
>> implement the stuff.
> You're perfectly right again. But as well "open source" does not mean:
> The developers develop software just for their own purposes and the sole
> task of the users downloading the software is
And the new zoom function makes it really easy to "dive" into speed or
elevation profiles and to catch any point with range select tool
zero
Le 22/11/2016 à 18:24, Oliver Eichler a écrit :
>
>>> ...
>>> And when I started with QMS I made a list of errors I will not make
>>> again. One of them
Oliver,
On Tuesday, 2016-11-22 09:52:15 +0100, you wrote:
> ...
> And when I started with QMS I made a list of errors I will not make
> again. One of them is implementing features I personally do not need.
I somehow doubt that this attitude (implementing features one personally
doesn't need is
FYI the Douglas-Peucker in QMS is 3D. Thus it's limit also applies for
the change in elevation.
Am 22.11.2016 um 14:05 schrieb Ivo Reano:
> Thanks for your answer, Oliver.
> The Douglas-Peucker filter I do not like! It takes away important
> points on important traits and safe, as the ridges of
Hi Ivo,
Even with version 1.7.1 you can select a single point. No need to select
3 points. The only caveat right now is that range selection returns to
default cursor after an operation. As all other functions do the same it
is just consistent. However I often reason with myself that it might be
Hi John,
I doubt it. That feature caused a bit of a headache in QLGT. And I would
like to avoid that in QMS. In general that list widget is quite slow for
a large number of entries. The fun part about tracks is that you can
present them in all kinds of views. And the user expects to see the
Health to all!
As I do in QMS to clean a track?
I mean, in QLGT:
Enlarge the map to the maximum
They select the track
right click -> Edit
At the bottom select "Track List"
They select the first point
It highlights the point in the center of the map and at each shift
with the arrow
keys I have
13 matches
Mail list logo
