2015-03-25 22:04 GMT-03:00 Long, Martin :
>
>>> That sounds good. The specification uses the word "groups", but I don't
>>> really like this because groups seems to imply that an item belongs to a
>>> single group. I prefer "sets". My Suunto dive computer, for example would
>>> be part of both my
>
>
>> That sounds good. The specification uses the word "groups", but I don't
>> really like this because groups seems to imply that an item belongs to a
>> single group. I prefer "sets". My Suunto dive computer, for example would
>> be part of both my "UK Cold Water" set, and my "Tropical" set, a
On 26 March 2015 at 02:43, Lubomir I. Ivanov wrote:
>>
>> -
>> MainWindow::instance()->editCurrentDive();
>
> and the exemplary whitespace noise...noticed only after the patch has
> been sent, of course.
> i knew it will get back to be...
>
anyway, here is the update.
let me know
>
> -
> MainWindow::instance()->editCurrentDive();
and the exemplary whitespace noise...noticed only after the patch has
been sent, of course.
i knew it will get back to be...
lubomir
--
___
subsurface mailing list
subsurface@subsurface-
From: "Lubomir I. Ivanov"
Once a manually added dive is part of a trip and this trip
is edited, applying the modifications leaves the dive profile
in edit mode (e.g. points can be dragged and gas swapping can
be applied).
The issue can be viewed from another angle. Why enable
profile edits of a
2015-03-25 21:20 GMT-03:00 Thiago Macieira :
> On Monday 23 March 2015 05:51:26 Dirk Hohndel wrote:
> > > *ClassName::ClassName() :*
> > > *x(1),*
> > > *y(2),*
> > > *z(3)*
> > > *{*
> > > *}*
> >
> > This isn't readable for me. Possibly a mail formating issue.
>
> I thought it was just me...
>
>
On Saturday 21 March 2015 16:05:44 Lubomir I. Ivanov wrote:
> On 20 March 2015 at 22:40, Abhinav Agarwal wrote:
> > While exporting a divelog to xml/ssrf, if given filename contains a dot it
> > doesnt get saved as intended. for eg: if given filename is
> > 'divelog.first' it should get saved as '
On Monday 23 March 2015 05:51:26 Dirk Hohndel wrote:
> > *ClassName::ClassName() :*
> > *x(1),*
> > *y(2),*
> > *z(3)*
> > *{*
> > *}*
>
> This isn't readable for me. Possibly a mail formating issue.
I thought it was just me...
The original in HTML is:
ClassName::ClassName() :
x(1),
On Monday 23 March 2015 16:03:28 Lubomir I. Ivanov wrote:
> > 18 March 2015 at 02:22, Lubomir I. Ivanov wrote:
> > From: "Lubomir I. Ivanov"
> >
> > The extra call "dosomethingelse()" is added with the
> > intention that user will not be confused to add braces
> > around single lined "if" condit
2015-03-25 5:24 GMT-03:00 Long, Martin :
>
>>>
>> *MANY* thanks for your powerful explanation. =D
>>
>
> You're welcome :)
>
>
>> I have many ideas about how it should looks like and work... I'm doing
>> some mockups and I will let you see it soon.
>>
>
> Great, I'd love to see them.
>
>
>>
>> I'm
Ok, then I will update the version from melange with this one and I will
continue my research.
Thanks for your time and for your suggestions.
If anyone else has other comments or observations please don't hesitate to
express them.
Best wishes,
Claudiu
__
[2015-03-25 14:32:36 +0200] Lubomir I. Ivanov:
> it's usually best to put a sentence or two in the commit message about
> such side changes s well, because as you can see i though it's some
> sort of residue from a test case. :-)
Fair enough.
Here is the patch with a better commit message.
--
G
Am 25.03.2015 um 14:18 schrieb Anton Lundin:
> On 17 March, 2015 - Thomas Schrein (mailinglists) wrote:
>
>>
>>
>> Betreff: HighPressureLogger ... Re: Which protocol to implement on a home
>> brewed diving computer ?
>> Datum: Tue, 17 Mar 2015 15:58:09 +0100
>> Von: Thomas Schrei
On Wed, Mar 25, 2015 at 2:18 PM, Anton Lundin wrote:
>
> The problem comes when you try to use the second hp-port on a stage
> bottle. That one is in a really exposed position:
> http://dir-diver.com/en/equipment/reg_config_stages.html
>
> I don't really know how to do something sane there...
I
On 25 March 2015 at 13:59, Claudiu Olteanu wrote:
> Hi there,
>
> After I did a research about the Qt Bluetooth API, I updated the
> implementation
> section with a second approach which implies the Qt module. Please take a look
> over the Implementation and Plan sections and tell me if you belie
On 17 March, 2015 - Thomas Schrein (mailinglists) wrote:
>
>
> Betreff: HighPressureLogger ... Re: Which protocol to implement on a home
> brewed diving computer ?
> Datum:Tue, 17 Mar 2015 15:58:09 +0100
> Von: Thomas Schrein (mailinglists)
> An: Robert Helling
>
>
>
> Am 17
Hi there,
After I did a research about the Qt Bluetooth API, I updated the implementation
section with a second approach which implies the Qt module. Please take a look
over the Implementation and Plan sections and tell me if you believe that they
should be improved [1].
In the remained time
On 25 March 2015 at 02:34, Gaetan Bisson wrote:
> [2015-03-24 14:30:57 -1000] Gaetan Bisson:
>> The new code in subsurfacestartup.c takes care of initializing those
>> settings, so there is no need to set default values for the widgets in
>> plannerSettings.ui .
>
> Note that only two of those fiv
1) yes, I know.
2) I think that we can modify the algorithm a little bit so it will
give the same results as the original one, without strictly specifying
phases of the dive. In fact, there are a few factors modifying
compartments state and we can apply them through all the dive. Just
some of them
>
>
>>
> *MANY* thanks for your powerful explanation. =D
>
You're welcome :)
> I have many ideas about how it should looks like and work... I'm doing
> some mockups and I will let you see it soon.
>
Great, I'd love to see them.
>
> I'm thinking about structures where users could add or/and gr
20 matches
Mail list logo
