Oliver,
On Wednesday, 2016-11-30 09:15:15 +0100, you wrote:
> ...
> The first sentence in the Wiki:
>
> " As the software is subject to a constant development progress, this
> manual will always reflect just a snapshot of the current state.
> Screenshots seen in this manual might not reflect the
Am 29.11.2016 um 14:26 schrieb Dr Rainer Woitok:
> 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
>>
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 no
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 comboboxe
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
>
> * auto
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 specificati
Oliver,
On Wednesday, 2016-11-23 18:52:35 +0100, you wrote:
> ...
> Right. The core idea and expectation of open source is that the users
> find the bug, fix it and send a patch. But personally I wouldn't go that
> far.
Wrong. While I'm accepting that you "wouldn't go that far", I heartily
dis
>> 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 t
Oliver,
On Tuesday, 2016-11-22 18:24:29 +0100, you wrote:
> ...
> First, QMS is open source licensed under GPL3. This is not public domain
> at all.
You're perfectly right. Being in this software business for umpteen
years now I do in fact know the difference, even if I off and on happen
t
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 i
>> ...
>> 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 an ERROR), fits well with the ideas behind public dom
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 a
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 th
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
actio
On 21/11/16 06:47, Oliver Eichler wrote:
you are right, In QMS the trackpoint list is more or less informative without
a real function. Historically the list was the first way to manipulate
trackpoints in QLGT. A range selection with the mouse was introduced at a much
later deleopment stage. And
Hi Ivo,
you are right, In QMS the trackpoint list is more or less informative without
a real function. Historically the list was the first way to manipulate
trackpoints in QLGT. A range selection with the mouse was introduced at a much
later deleopment stage. And it never worked well.
In QMS c
19 matches
Mail list logo
