On 30.05.2014, at 05:42, Dirk Hohndel <[email protected]> wrote: Dirk,
> On Thu, May 29, 2014 at 04:35:18PM -0700, Dirk Hohndel wrote:
>> I haven't spent any time looking into this, but I noticed that I cannot
>> change the duration of any segment of a dive plan in the data table. You
>> can change the depth, but not the duration.
>
> Interesting - Tomaz pointed out that this was intentionally implemented as
> such by Robert.
>
> I wonder why...
because I was lazy. And thinking more about it, my intention was based on a
wrong assumption.
I wanted to avoid dealing with points that change their order by typing in the
time field. So I though I let only the runtime be endurable, (so only absolute
times in the old sense) not the duration. But this does’t prevent stupid (and
then wrong things).
The problem comes from the fact that we display the same information twice once
as runtime (i.e. absolute time) once as duration (i.e. relative time). The
question is: When I change one (say the runtime of a waypoint) what about the
other waypoints? Shall we keep their runtime or their duration fixed? In the
profile representation, we always move a single point, so we keep the other
runtimes fixed. Is it the proper thing to do the same for the table? In that
case it’s simple: Editing one of the fields should only be interpreted as
having an influence on the runtime of that point, so adjust that, possibly
resort the table and then recompute all durations after that. But maybe the
user wants also a possibility to assume the durations of the other segments are
fixed. In that case the runtime of all the following points would be changed as
well.
Maybe a way out would be that editing the runtime column implies the first
behavior while editing the duration implies the second? This would at least
prevent us from the bad case when the endpoint of a segment is moved before its
start (by entering a value in the runtime column). What do you think?
Bonus question: Shall we offer to change the duration as well in the graphical
representation (e.g. when the shift key is pressed, not only the handle under
the mouse but alle the following ones as well are moved)?
Robert
--
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oO
Robert C. Helling Elite Master Course Theoretical and Mathematical Physics
Scientific Coordinator
Ludwig Maximilians Universitaet Muenchen, Dept. Physik
Phone: +49 89 2180-4523 Theresienstr. 39, rm. B339
http://www.atdotde.de
Enhance your privacy, use cryptography! My PGP keys have fingerprints
A9D1 A01D 13A5 31FA 6515 BB44 0820 367C 36BC 0C1D and
DCED 37B6 251C 7861 270D 5613 95C7 9D32 9A8D 9B8F
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ subsurface mailing list [email protected] http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
