Re: 4.8.1 planning

[Anton Lundin]

On 12 July, 2018 - Dirk Hohndel wrote:

> > Hooray, this seems to work.
> 
> Excellent!
> 

It did it for me to. I guess its some sort of delay for the bt chip to
init and propperly talk to the main cpu.


//Anton


-- 
Anton Lundin+46702-161604
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [Subsurface-divelog/subsurface] Cannot connect on first launch after update on Windows (#1499)

[tormento]

May I ask which is the sense of your hint?

I don't use installer, thus the registry is not touched after every update.
It seems very strange that you have to reenter credentials every time too.

I keep on being convinced that the update check window is the culprit of
the problem. If some of the developers could disable it for nightly, we
would have a proof or not of what I am saying.

Il giorno ven 13 lug 2018 alle ore 14:37 Lubomir I. Ivanov <
notificati...@github.com> ha scritto:

> No need to re-enter credentials. And yes, the error is red.
>
> in my case i always have to re-enter credentials.
>
> you can try this:
>
>- close subsurface
>- open the start menu and enter "regedit" to start it
>- in regedit open HKEY_CURRENT_USER / Software
>- rename the Subsurface folder to Subsurface_ (this will backup your
>settings)
>- start subsurface
>
> see if the error happens again.
>
> NOTE: you can always rename your old settings Subsurface_ in regedit back
> to Subsurface, but make sure any new Subsurface folders are deleted in
> there first.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> ,
> or mute the thread
> 
> .
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [TEST REQUEST] Windows Bluetooth LE build

[Lubomir I. Ivanov]

On 25 June 2018 at 23:05, Dirk Hohndel  wrote:
>
>> On Jun 25, 2018, at 10:43 PM, Lubomir I. Ivanov  wrote:
>>
>> got a confirmation today that the only way to communicate with GATT
>> services on Windows / Qt (native API, not the the UWP) is to first go
>> to the Control Panel and ***manually pair the BLE devices via the
>> UI***.
>> there could be hacks for that, that we are not aware of, but Google
>> shows nothing.
>>
>> this means that DC users that have not paired their devices will
>> experience errors in Subsurface.
>>
>> if BLE is to be eventually supported on Windows, this has to be
>> documented and/or possibly a message has to be shown in the "Download
>> from DC" dialog in the lines of "please, pair your DC devices in
>> Control Panel first".
>

so i was finally able to connect the OSTC+ (BLE) on Windows with Qt,
but now a Win32 developer introduced new functionality in the windows
branch for QtConnectivty and the moment i synced with the remote
branch it required me to build against a newer version of qtbase,
which completely messed up by Qt build.

...and now i cannot build Qt because of a weird qmake issue which is
present in 5.10 and 5.11. maybe it's my compiler.
when i get this sorted i will deploy new test binaries for people to test.

lubomir
--

PS: i would like the point out that the qt build system is a peace of
cra*p that only works in theory.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: smtk2ssrf windows installer not in downloads

[Dirk Hohndel]

> On Jul 12, 2018, at 11:41 PM, Salvador Cuñat  wrote:
> 
> Hi Dirk
> 
> I have just sent a PR updating the user-manual in the part related to
> SmartTrak import, and noticed there are no windows installers for
> smtk2ssrf in the downloads page.
> 
> Tnere are appimages, but no .exe files, which used to be there.
> 
> May be this has something to do with the issue reported by Matt and
> Davide on 4.8 release about the link pointing erroneously to the
> smtk2ssrf installer.

Indeed - the way we create the response back to the user is insanely braindead
and needs to be fixed. The easiest solution was to remove the smtk2ssrf exe.

There are just too many things on my TODO list right now. I'll get to it.

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: 4.8.1 planning

[Linus Torvalds]

On Thu, Jul 12, 2018 at 9:59 PM Dirk Hohndel  wrote:
>
> Can I get a commit for this, Linus? :-)

Pull request done.

  Linus
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

4.8.1

[Dirk Hohndel]

Last call, I guess...

We have the Mac problems fixed, the OSTC download and configuration issues 
fixed (big thanks to 
Linus and Anton... - I'm only waiting for Travis before merging Linus' fix), 
and we don't appear to 
have broken too many things with the other changes that went in so far, so 
ideally I'd like to release 
4.8.1 today or tomorrow.

Currently the CHANGELOG looks like this:

- Mac: fix crashes when opening the user manual or connecting to Facebook
- BT support: fix downloading / configuring some OSTC models
- BLE support: fix recognition of Heinrich Weikamp OSTC 2 and OSTC Plus
- Cloud storage: fix potential issue with credentials on Linux [#1346]
- Profile: Context menu entry to manually split a dive
- Dive media: support addition of videos
- Dive media: locate moved files based on filename and path
- Mobile/iOS: fix missing translations

(I guess technically that's a lie because I haven't pushed that edited 
CHANGELOG, yet, waiting to first
merge Linus' PR)

Anything missing from the CHANGELOG? Anything else that we need to add?

Thanks

/D___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [TEST REQUEST] Windows Bluetooth LE build

[Lubomir I. Ivanov]

On 13 July 2018 at 18:29, Lubomir I. Ivanov  wrote:
> On 25 June 2018 at 23:05, Dirk Hohndel  wrote:
>>
>>> On Jun 25, 2018, at 10:43 PM, Lubomir I. Ivanov  wrote:
>>>
>>> got a confirmation today that the only way to communicate with GATT
>>> services on Windows / Qt (native API, not the the UWP) is to first go
>>> to the Control Panel and ***manually pair the BLE devices via the
>>> UI***.
>>> there could be hacks for that, that we are not aware of, but Google
>>> shows nothing.
>>>
>>> this means that DC users that have not paired their devices will
>>> experience errors in Subsurface.
>>>
>>> if BLE is to be eventually supported on Windows, this has to be
>>> documented and/or possibly a message has to be shown in the "Download
>>> from DC" dialog in the lines of "please, pair your DC devices in
>>> Control Panel first".
>>
>
> so i was finally able to connect the OSTC+ (BLE) on Windows with Qt,
> but now a Win32 developer introduced new functionality in the windows
> branch for QtConnectivty and the moment i synced with the remote
> branch it required me to build against a newer version of qtbase,
> which completely messed up by Qt build.
>

i'm able to get the dive download from the OSTC+ on Windows to start
going but early in the process it fails.
detailed log here:
https://pastebin.com/k4fCX13r

is the OSTC+ download currently working on other platforms?

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

4.8.1 has been released

[Dirk Hohndel]

Tags are pushed. Source are up. Binaries are up. Post is up on our website, but 
not yet on FB. Download links are updated.
I wonder what I forgot this time...

The announcement would benefit from translation.

Speaking of which, we should reconsider some of the translations that we offer.

Dutch and Spanish are clearly actively maintained. German is somewhat 
maintained.
The other languages haven't seen updates in a long time... 
Do we have people interested in maintaining French, Italian, Polish, Russian, 
Portuguese, and Finnish?
Because if we don't, then maybe we should discontinue those and focus on those 
languages where we have active maintainers.

Speaking of that - it's high time to refresh our website content in the first 
place. The pages haven't changed in quite a while and I think they are pretty 
stale and outdated at this time.

Any volunteers? Anyone with a knack for writing good copy who'd love to 
contribute to Subsurface by helping us refresh the website?

In the meantime, thanks to everyone who helped track down a couple of odd and 
hard to fix bugs, especially the download and configuration issues with some 
OSTCs and of course the crashes on Mac. These were rather odd issues to run 
into after the release.
While the log seems to indicate that the vast majority of the work was done by 
Jan and myself, I think it's fair to say that by far the majority of our 
commits are incremental improvements to the build system and cleanup work. The 
feature work came mostly from the other people in this list.

$ git shortlog -s -n v4.8.0..
41  Dirk Hohndel
25  jan Iversen
16  Berthold Stoeger
 9  Joakim Bygdell
 6  Stefan Fuchs
 4  Lubomir I. Ivanov
 4  Robert C. Helling
 3  Salvador Cuñat
 3  Linus Torvalds
 1  Martin Měřinský
 1  Miika Turkia
 1  Anton Lundin
 1  Alexander Wilms


Thanks everyone.

/D___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [TEST REQUEST] Windows Bluetooth LE build

[Lubomir I. Ivanov]

On 14 July 2018 at 02:52, Lubomir I. Ivanov  wrote:
> On 13 July 2018 at 18:29, Lubomir I. Ivanov  wrote:
>> On 25 June 2018 at 23:05, Dirk Hohndel  wrote:
>>>
 On Jun 25, 2018, at 10:43 PM, Lubomir I. Ivanov  
 wrote:

 got a confirmation today that the only way to communicate with GATT
 services on Windows / Qt (native API, not the the UWP) is to first go
 to the Control Panel and ***manually pair the BLE devices via the
 UI***.
 there could be hacks for that, that we are not aware of, but Google
 shows nothing.

 this means that DC users that have not paired their devices will
 experience errors in Subsurface.

 if BLE is to be eventually supported on Windows, this has to be
 documented and/or possibly a message has to be shown in the "Download
 from DC" dialog in the lines of "please, pair your DC devices in
 Control Panel first".
>>>
>>
>> so i was finally able to connect the OSTC+ (BLE) on Windows with Qt,
>> but now a Win32 developer introduced new functionality in the windows
>> branch for QtConnectivty and the moment i synced with the remote
>> branch it required me to build against a newer version of qtbase,
>> which completely messed up by Qt build.
>>
>
> i'm able to get the dive download from the OSTC+ on Windows to start
> going but early in the process it fails.
> detailed log here:
> https://pastebin.com/k4fCX13r
>
> is the OSTC+ download currently working on other platforms?
>

added Jan Mulder to CC on the above question.

link for testing my latest test build for BLE on Win32:
https://www.dropbox.com/s/zslq3ughx9ciehj/_deploy_win32_ble.zip?dl=0

maybe other DCs work.

testing instructions in this email from before:
http://lists.subsurface-divelog.org/pipermail/subsurface/2018-June/032171.html

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

the last tagged version is v4.7.8

[Lubomir I. Ivanov]

master is at 52cc51f9061f for me and the last defined tag is:
v4.7.8

did we stop using tags for v4.8.x?

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: the last tagged version is v4.7.8

[Lubomir I. Ivanov]

On 14 July 2018 at 03:46, Lubomir I. Ivanov  wrote:
> master is at 52cc51f9061f for me and the last defined tag is:
> v4.7.8
>
> did we stop using tags for v4.8.x?
>

my mistake, i didn't pull the latest tags, because i was rebasing.

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [TEST REQUEST] Windows Bluetooth LE build

[Thiago Macieira]

On Friday, 13 July 2018 08:29:42 PDT Lubomir I. Ivanov wrote:
> ...and now i cannot build Qt because of a weird qmake issue which is
> present in 5.10 and 5.11. maybe it's my compiler.
> when i get this sorted i will deploy new test binaries for people to test.

What's the issue?

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center



___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [TEST REQUEST] Windows Bluetooth LE build

[Lubomir I. Ivanov]

On 14 July 2018 at 06:55, Thiago Macieira  wrote:
> On Friday, 13 July 2018 08:29:42 PDT Lubomir I. Ivanov wrote:
>> ...and now i cannot build Qt because of a weird qmake issue which is
>> present in 5.10 and 5.11. maybe it's my compiler.
>> when i get this sorted i will deploy new test binaries for people to test.
>
> What's the issue?
>

building qt on windows with mingw (can't look at the version number right now).

i was getting a compiler error somewhere in the qmake source
(something about a duplicate "escape path" method), when building the
5.11 branch of qtbase.
cleaning object code didn't help. to solve this, i removed the qtbase
submodule completely, initialized it again but this time built the
5.10 branch.

now it works.
i'm getting these weird issues from time to time and the only thing
that works consistently for me is to either nuke submodules or the
whole local copy.

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [TEST REQUEST] Windows Bluetooth LE build

[Thiago Macieira]

On Friday, 13 July 2018 21:21:32 PDT Lubomir I. Ivanov wrote:
> building qt on windows with mingw (can't look at the version number right
> now).
> 
> i was getting a compiler error somewhere in the qmake source
> (something about a duplicate "escape path" method), when building the
> 5.11 branch of qtbase.
> cleaning object code didn't help. to solve this, i removed the qtbase
> submodule completely, initialized it again but this time built the
> 5.10 branch.

qmake is special because it's not built with qmake (circular dependency). So 
its Makefile is much simpler and is not as complete.

When I have such an issue, I do:
 rm -rf qmake
 cmd \ /c config.status

If you're in a regular DOS prompt, probably

 rd /s /q qmake
 config.status

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center



___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [TEST REQUEST] Windows Bluetooth LE build

[Lubomir I. Ivanov]

On 14 July 2018 at 07:30, Thiago Macieira  wrote:
> On Friday, 13 July 2018 21:21:32 PDT Lubomir I. Ivanov wrote:
>> building qt on windows with mingw (can't look at the version number right
>> now).
>>
>> i was getting a compiler error somewhere in the qmake source
>> (something about a duplicate "escape path" method), when building the
>> 5.11 branch of qtbase.
>> cleaning object code didn't help. to solve this, i removed the qtbase
>> submodule completely, initialized it again but this time built the
>> 5.10 branch.
>
> qmake is special because it's not built with qmake (circular dependency). So
> its Makefile is much simpler and is not as complete.
>
> When I have such an issue, I do:
>  rm -rf qmake
>  cmd \ /c config.status
>
> If you're in a regular DOS prompt, probably
>
>  rd /s /q qmake
>  config.status
>

thanks,
good to know.

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [TEST REQUEST] Windows Bluetooth LE build

[Thiago Macieira]

On Friday, 13 July 2018 21:32:10 PDT Lubomir I. Ivanov wrote:
> > rm -rf qmake
> > cmd \ /c config.status
> > 
> > If you're in a regular DOS prompt, probably
> > 
> > rd /s /q qmake
> > config.status

BTW those config.status.bat are just:

configure -redo

Usually, on Windows you want to run configure.bat, but if you've been using 
the sh script and it works for you, you can do that too.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center



___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface