Re: importing smarttrak slg logs

2017-02-03 Thread Willem Ferguson
On 04/02/2017 01:38, Alessandro Volpi wrote: Forwarded Message Subject:Re: Fwd: importing smarttrak slg logs Date: Fri, 3 Feb 2017 23:15:55 + From: Alessandro Volpi To: Salvador Cuñat

Re: Building on macOS error

2017-02-03 Thread Benjamin
On 4 February 2017 at 00:42, Dirk Hohndel wrote: > > ... > Webkit is no longer included by default. You can build it from source, or > you can use -DUSE_WEBENGINE=ON on the cmake command line. That disables > printing as that hasn't been ported to WebEngine, yet > > /D > > Is

Re: Subsurface deco calculations

2017-02-03 Thread Rick Walsh
On 4 February 2017 at 15:53, Miika Turkia wrote: > Hello, > > I cannot currently log into my gmail account due to 2-factor > authentication challenges (cannot receive SMS at the moment), so using > my private email, with hopefully correct addresses see-and-pasted from > my

Re: doing a 4.6.1 release

2017-02-03 Thread Miika Turkia
I noticed 2 things when testing: - Automerge is not triggered when importing additional dc from a Subsurface xml file (I fixed date and time manually for one dc on a separate xml that I then imported to my main log) - I have quite different deco calculations for different DCs on same dive.

Re: Problems building Subsurface for Android

2017-02-03 Thread Dirk Hohndel
Because clearly I like pain, I went through this whole thing again. And tried to make it even more self contained, even more automatic. And because clearly I was bored, I tested the whole thing on a freshly installed Ubuntu 16.10. Here are the complete steps it took me to get a working

Re: Building on macOS error

2017-02-03 Thread Dirk Hohndel
> On Feb 3, 2017, at 2:34 PM, Federico Masias wrote: > > Hi all, > > I'm having some issues trying to build on mac, while following the > instructions on the Building part of the website. The following error gets > spit out: > > CMake Error at

Building on macOS error

2017-02-03 Thread Federico Masias
Hi all, I'm having some issues trying to build on mac, while following the instructions on the Building part of the website. The following error gets spit out: CMake Error at /Users/fede/Qt/5.6/clang_64/lib/cmake/Qt5/Qt5Config.cmake:26 > (find_package): > > Could not find a package

Re: Diveplan line breaks in UI and printing - vs. - Linux vs. Windows

2017-02-03 Thread Federico Masias
> > Fixed it by deleting the printing templates in ~/.subsurface > Now Linux and Windows result is the same. > Looks like an update to the FAQ is in order, then. Dirk, I sent changes via github for English and Spanish. ___ subsurface mailing list

[PATCH] Re: Crash when saving dive in planner after latest commits

2017-02-03 Thread Robert Helling
> On 03 Feb 2017, at 21:55, Stefan Fuchs wrote: > > Hallo Dirk, hi All, > > very short note: > > Latest git (SHA f563f736078ac3dfbb999b6c2e2352defd729f62) crashes when saving > a planned dive under linux. Even didn't try windows. > > Did a "git reset --hard" to some older

Re: Diveplan line breaks in UI and printing - vs. - Linux vs. Windows

2017-02-03 Thread Stefan Fuchs
Hi All, Am 03.02.2017 um 21:51 schrieb Lubomir I. Ivanov: > On 3 February 2017 at 22:22, Stefan Fuchs wrote: >> Now I found out there is one issue left concerning printing. I attached 4 >> screen shots: >> >> - Output in UI in planner looks good >> - Output in UI in main window in

Crash when saving dive in planner after latest commits

2017-02-03 Thread Stefan Fuchs
Hallo Dirk, hi All, very short note: Latest git (SHA f563f736078ac3dfbb999b6c2e2352defd729f62) crashes when saving a planned dive under linux. Even didn't try windows. Did a "git reset --hard" to some older point on a copy of master and applied my patches (surface pressure, SAC) again: works ok

Re: Diveplan line breaks in UI and printing - vs. - Linux vs. Windows

2017-02-03 Thread Lubomir I. Ivanov
On 3 February 2017 at 22:22, Stefan Fuchs wrote: > Hi All, > > you may know me as a complete newbie managed to do my first small change to > the Subsurface planner: Adding surface pressure and SAC to the planner > results. > > Now I found out there is one issue left concerning

Re: Problems building Subsurface for Android

2017-02-03 Thread Dirk Hohndel
> On Feb 3, 2017, at 12:41 PM, Willem Ferguson > wrote: > > On 03/02/2017 19:41, Dirk Hohndel wrote: >> >> It should still create a working .apk - did you check that? >> >> /D > I assume the apk should be in ~src/subsurface-build-arm/ ?? > There is no bin

Re: Diveplan line breaks in UI and printing - vs. - Linux vs. Windows

2017-02-03 Thread Dirk Hohndel
> On Feb 3, 2017, at 12:22 PM, Stefan Fuchs wrote: > > Hi All, > > you may know me as a complete newbie managed to do my first small change to > the Subsurface planner: Adding surface pressure and SAC to the planner > results. > > Now I found out there is one issue left

Re: Problems building Subsurface for Android

2017-02-03 Thread Willem Ferguson
On 03/02/2017 19:41, Dirk Hohndel wrote: It should still create a working .apk - did you check that? /D I assume the apk should be in ~src/subsurface-build-arm/ ?? There is no bin directory in the above one and I see no apk file. ~/src/subsurface-build-arm$ ls -l total 45752 drwxrwxr-x 3

Re: Problems building Subsurface for Android

2017-02-03 Thread Dirk Hohndel
> On Feb 3, 2017, at 9:24 AM, Willem Ferguson > wrote: > > When running android-build.sh, I had to install parts of the android SDK. > When running the script a second time I get: > > Copying gdbserver into package. > -- Copied >

Re: Problems building Subsurface for Android

2017-02-03 Thread Willem Ferguson
When running android-build.sh, I had to install parts of the android SDK. When running the script a second time I get: Copying gdbserver into package. -- Copied /home/willem/src/subsurface-mobile-build-arm//libs/armeabi-v7a/gdbserver -- Copied

Re: Problems building Subsurface for Android

2017-02-03 Thread Anton Lundin
On 03 February, 2017 - Joakim Bygdell wrote: > On 3 February 2017 at 10:49, Willem Ferguson < > willemfergu...@zoology.up.ac.za> wrote: > > > On 03/02/2017 08:25, Joakim Bygdell wrote: > > > > Remove the quotations on line 383 and try again, that fixed it for me. > > -- > > Jocke > > > > > > > >

Re: Problems building Subsurface for Android

2017-02-03 Thread Dirk Hohndel
On Fri, Feb 03, 2017 at 12:51:21PM +0200, Willem Ferguson wrote: > > > On 03/02/2017 12:27, Dirk Hohndel wrote: > > So did you run the scripts/android-build.sh that I wrote pretty much > > specifically for you to help you through all these things? > > > > I should have realized yesterday that

Re: Problems building Subsurface for Android

2017-02-03 Thread Willem Ferguson
On 03/02/2017 12:27, Dirk Hohndel wrote: So did you run the scripts/android-build.sh that I wrote pretty much specifically for you to help you through all these things? I should have realized yesterday that you didn't because THAT one downloads and installs libdivecomputer and does the

Re: Problems building Subsurface for Android

2017-02-03 Thread Willem Ferguson
On 03/02/2017 12:27, Dirk Hohndel wrote: So did you run the scripts/android-build.sh that I wrote pretty much specifically for you to help you through all these things? I should have realized yesterday that you didn't because THAT one downloads and installs libdivecomputer and does the

Re: Problems building Subsurface for Android

2017-02-03 Thread Dirk Hohndel
> On Feb 3, 2017, at 1:49 AM, Willem Ferguson > wrote: > Scanning dependencies of target subsurface.apk > [ 89%] Generating run_android_deploy_qt > Directory /home/willem/src/android-sdk-linux/platforms does not exist > make[2]: *** [run_android_deploy_qt] Error

Re: Problems building Subsurface for Android

2017-02-03 Thread Joakim Bygdell
On 3 February 2017 at 10:49, Willem Ferguson < willemfergu...@zoology.up.ac.za> wrote: > On 03/02/2017 08:25, Joakim Bygdell wrote: > > Remove the quotations on line 383 and try again, that fixed it for me. > -- > Jocke > > > > I think your suggestions were extremely helpful. Thank you very much.

Re: Problems building Subsurface for Android

2017-02-03 Thread Willem Ferguson
On 03/02/2017 08:25, Joakim Bygdell wrote: Remove the quotations on line 383 and try again, that fixed it for me. -- Jocke I think your suggestions were extremely helpful. Thank you very much. The problem below is due to a totally different reason. It almost completes the