Re: reverted marble mess

Am 18.07.2017 um 18:59 schrieb Dirk Hohndel: On Jul 18, 2017, at 9:41 AM, Axel Richter wrote: Am 15.07.2017 um 07:53 schrieb Dirk Hohndel: Since Tomaz hasn't had the time to fix the broken marble source (and currently builds from source were failing) I reverted the

Re: QML custom style

On 18 July 2017 at 22:10, Rick Walsh wrote: > Dirk and Jocke (especially), > I can see you've done a lot over the past few weeks to make the mobile UI > much more attracted. Have you considered using a custom Subsurface style > (falling back to Material) to make it more

QML custom style

Dirk and Jocke (especially), I can see you've done a lot over the past few weeks to make the mobile UI much more attracted. Have you considered using a custom Subsurface style (falling back to Material) to make it more efficient to theme the QML controls? It would be easier to customize the

Re: Pull request

On 18/07/2017 21:43, Dirk Hohndel wrote: The manual that you get when you click the link is the one posted on the website - which is the "old' one indeed. But the sources already contain a much updated manual. I could try and post a Subsurface-mobile-v2 user manual on the website (built from

Re: Pull request

> On Jul 18, 2017, at 12:24 PM, Willem Ferguson > wrote: > > On 18/07/2017 18:10, Dirk Hohndel wrote: >> Hmm, I don't even understand the question. >> >> I haven't seen a pull request, but you sent me email to pull from the >> separate git repo that you >>

Re: Issues with SAC terminology

On Tue, Jul 18, 2017 at 2:14 PM, Dirk Hohndel wrote: > Remember, we always show the unit (l/min or cuft/min), so it's clear that SAC > isn't a pressure drop. Side note - In the mobile app, I see only "cuft", not "cuft/min". Clearly, the numbers being shown are "cuft/min" - I

Re: Pull request

On 18/07/2017 18:10, Dirk Hohndel wrote: Hmm, I don't even understand the question. I haven't seen a pull request, but you sent me email to pull from the separate git repo that you shared with me a while ago. Are there other changes I need to pull? Where are they? I will sort out the pull

Re: Issues with SAC terminology

> On Jul 18, 2017, at 11:11 AM, Willem Ferguson > wrote: > > On 18/07/2017 19:14, Linus Torvalds wrote: >> >> Absolutely *everybody* knows what we mean by SAC rate. And the ones >> that are offended by our use of standard terminology can be offended. >> >>

Re: Issues with SAC terminology

On 18/07/2017 19:14, Linus Torvalds wrote: Absolutely *everybody* knows what we mean by SAC rate. And the ones that are offended by our use of standard terminology can be offended. It's their problem, not ours. Let's not take on their mental baggage. Linus Part of this

Re: [Subsurface-divelog/subsurface] [idea] Mobile UI #5: sidebar (#430)

Sorry for too quoting. I'm with Dirk here. I would trilled to see a planner and maybe a gas mixer but as a standalone app planner+mixer. As on the stats feature I would prefer a more KISS approach. I don't like a swiss knife approach aka do it all. On menu size. Don't worry we can scroll it.

Re: [Subsurface-divelog/subsurface] [idea] Mobile UI #5: sidebar (#430)

I am very intentionally moving this small part of the discussion around Davide's Mobile UI ideas back to the developer mailing list because I think it is important - and not a lot of the people here tend to look at the issues on github (that's the eternal problem... it's hard to discuss these

Re: Issues with SAC terminology

On Tue, Jul 18, 2017 at 9:54 AM, Willem Ferguson < willemfergu...@zoology.up.ac.za> wrote: > This is in some ways a sensitive issue and maybe reflect existing > discussion on this mail list that I am not aware of. The term "Surface Air > Consumption" (SAC) is probably used wrongly most of the

Re: Issues with SAC terminology

> On Jul 18, 2017, at 10:18 AM, Linus Torvalds > wrote: > > On Tue, Jul 18, 2017 at 10:14 AM, Linus Torvalds > wrote: >> >> Absolutely *everybody* knows what we mean by SAC rate. And the ones >> that are offended by our use of

Re: Issues with SAC terminology

On Tue, Jul 18, 2017 at 10:14 AM, Linus Torvalds wrote: > > Absolutely *everybody* knows what we mean by SAC rate. And the ones > that are offended by our use of standard terminology can be offended. The takeaway here really is that even the people who have have

Re: Issues with SAC terminology

On Tue, Jul 18, 2017 at 6:54 AM, Willem Ferguson wrote: > > Shouldn't we at some stage get the terminology accurate and replace SAC in > the UI throughout with RMV? No, I really don't think so. The scuba world has a lot of random terminology that may be

Re: QML UI theming

Patches sent to upstream Kirigami. -- Jocke ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Issues when editing a downloaded dive from DC

On 18-07-17 18:41, Chirana Gheorghita Eugeniu Theodor wrote: Does anyoane here has the same issue or I am the only one? On Jul 17, 2017 23:30, "Chirana Gheorghita Eugeniu Theodor" > wrote: Ahoy list, This is my first message here so I

Re: reverted marble mess

> On Jul 18, 2017, at 9:41 AM, Axel Richter wrote: > > Am 15.07.2017 um 07:53 schrieb Dirk Hohndel: >> Since Tomaz hasn't had the time to fix the broken marble source (and >> currently builds from source were failing) I reverted the merge of his >> changes. Of course

Re: reverted marble mess

Am 15.07.2017 um 07:53 schrieb Dirk Hohndel: Since Tomaz hasn't had the time to fix the broken marble source (and currently builds from source were failing) I reverted the merge of his changes. Of course that means I need to be extra careful to handle this branch moving forward, because if we

Re: reverted marble mess

Am 15.07.2017 um 07:53 schrieb Dirk Hohndel: Since Tomaz hasn't had the time to fix the broken marble source (and currently builds from source were failing) I reverted the merge of his changes. Of course that means I need to be extra careful to handle this branch moving forward, because if we

Re: Issues when editing a downloaded dive from DC

Does anyoane here has the same issue or I am the only one? On Jul 17, 2017 23:30, "Chirana Gheorghita Eugeniu Theodor" < off...@adaptcom.ro> wrote: > Ahoy list, > This is my first message here so I wish to say hello to all users and a > big thank you to developers. > I recently downloaded a dive

Re: mysterious code (qtserialbleutooth.cpp)

On Jul 18, 2017 06:49, "Jan Mulder" wrote: Is the typo in the #define intentional? Nope, absolutely not intentional. And where is the actual value defined? I have no idea. Apparently BUFSZ we just too randomly generic of a name that it matched some other common

Re: Mobile UI Sidebar and Settings

> On Jul 18, 2017, at 6:53 AM, Davide DB wrote: > > I worked on two of the three parts of the current Subsurface that IMHO > I feel need more work. > > - Sidebar > - Settings > > I left the "edit dive details" as next last effort. > >

RE: BLE on iOS

> -Original Message- > From: Dirk Hohndel [mailto:d...@hohndel.org] > I don't want to sound like a downer... but I must have missed that > explanation in > the documentation. It would be kinda neat if the classes had a little warning > that > said "this doesn't work on iOS -

Re: BLE on iOS

Hello, > Excellent. So we can bug him for both iOS and Mac? :-) Yes  > That's one of the things that puzzle me. It says the same about macOS in the > documentation, yet we do get Bluetooth addresses on macOS - just not 100% > reliably. Apple has two frameworks actually - IOBluetooth (to

Issues with SAC terminology

This is in some ways a sensitive issue and maybe reflect existing discussion on this mail list that I am not aware of. The term "Surface Air Consumption" (SAC) is probably used wrongly most of the time, including by myself. This is because it is conflated with the Respiratory Minute Volume

Mobile UI Sidebar and Settings

I worked on two of the three parts of the current Subsurface that IMHO I feel need more work. - Sidebar - Settings I left the "edit dive details" as next last effort. https://github.com/Subsurface-divelog/subsurface/issues/430#issuecomment-316069183 Please Dirk, be calm with your Hattori

mysterious code (qtserialbleutooth.cpp)

Struggling with BLE for OSTC I see a little mysterious code fragment: #define BUFSZ 1024 static struct { unsigned int out_bytes, in_bytes, in_pos; unsigned char in[BUFSIZ]; unsigned char out[BUFSIZ]; } buffer; As it is from Linus, I do not dare to change it right away

Re: QML UI theming

On 18 July 2017 at 15:39, Dirk Hohndel wrote: > > > On Jul 18, 2017, at 2:16 AM, Davide DB wrote: > > > > On 17 July 2017 at 22:14, Davide DB wrote: > >> > >> My last try: we could just color dive number of those dives with five > stars

Re: QML UI theming

On 18 July 2017 at 15:39, Dirk Hohndel wrote: > We actually modify the theme immediately... I'm ok with modifying > all the settings immediately. But then we need a different paradigm > that gets us out of there. I guess the back button on Android and > throwing the phone

Re: QML UI theming

> On Jul 18, 2017, at 2:16 AM, Davide DB wrote: > > On 17 July 2017 at 22:14, Davide DB wrote: >> >> My last try: we could just color dive number of those dives with five stars >> ;) >> >> davide@mobile >> > > While working with the latest APK I

Re: BLE on iOS

Hi Alex, Timur, > On Jul 18, 2017, at 4:09 AM, Alex Blasche wrote: >> Nor sure if you are the right person for this on iOS - but if not, maybe you >> can >> point me to the right person. > > Timur (in cc) is the Apple master for QtBluetooth. Excellent. So we can bug

RE: BLE on iOS

Hi Dirk, > -Original Message- > From: Dirk Hohndel [mailto:d...@hohndel.org] > Nor sure if you are the right person for this on iOS - but if not, maybe you > can > point me to the right person. Timur (in cc) is the Apple master for QtBluetooth. > When compiling Subsurface-mobile for

RE: OSTC over BLE experiences and questions

> -Original Message- > From: Jan Mulder [mailto:jlmul...@xs4all.nl] > Sent: Tuesday, 18 July 2017 10:04 > To: Alex Blasche ; Dirk Hohndel > Cc: Subsurface Mailing List > Subject: Re: OSTC over BLE experiences

BLE on iOS

Hi Alex, Nor sure if you are the right person for this on iOS - but if not, maybe you can point me to the right person. When compiling Subsurface-mobile for iOS with BT_SUPPORT enabled, we don't appear to get a valid QBluetoothLocalDevice at all. Asking for isValid() returns false, asking for