Re: quick hack to fix update check service

[Werner Macho via subsurface]

Hi!
Ja, gerade ausprobier - zumindest unter Linux und Windows können Links
direkt angeklickt werden

LG Werner

On Thu, Feb 23, 2023 at 11:37 AM Dirk Hohndel  wrote:

>
>
> > On Feb 23, 2023, at 01:27, Werner Macho  wrote:
> >
> > Hi!
> >
> > Also ich würde als Nutzer so etwas einfacher finden und bevorzugen:
> >
> > "Eine neue Version ist verfügbar.
> > Subsurface-5.0.10 kann hier heruntergeladen werden."
> >
> > Subsurface-5.0.10 ist dann die neu verfügbare Version
> > und "hier heruntergeladen werden" wäre der Link zur Download Seite.
>
> Wenn ich mich recht erinnere, konnte man (zumindest als ich das Ding
> das erste Mal entwickelt hatte) in Dialogboxen keine Links klicken.
>
> Geht das inzwischen?
>
> 🤷🏼‍♂️
>
> /D
>
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: quick hack to fix update check service

[Werner Macho via subsurface]

Hi!

Also ich würde als Nutzer so etwas einfacher finden und bevorzugen:

"Eine neue Version ist verfügbar.
Subsurface-5.0.10 kann hier heruntergeladen werden."

Subsurface-5.0.10 ist dann die neu verfügbare Version
und "hier heruntergeladen werden" wäre der Link zur Download Seite.

regards
Werner

On Wed, Feb 22, 2023 at 6:15 PM Dirk Hohndel  wrote:

> That is... not the best translation ever.
>
> Mein Deutsch ist nicht mehr ganz so komfortabel - ich lese sehr wenig
> Deutsch und schreibe noch weniger.
> Hättest Du eine bessere Übersetzung? Muss ja nicht wort-wörtlich sein,
> sondern einfach nur ein sinnvoller Text für diese Situation...
>
> Danke
>
> /D
>
> On Feb 21, 2023, at 23:56, Werner Macho  wrote:
>
> Hi!
>
> Checked with Subsurface-4.9.3-x86_64.AppImage
> and Subsurface-5.0.10-x86_64.AppImage on debian bookworm (testing) with the
> following messages:
> German translation for "bitte auf unserer Programme herunterladen Seite
> nachlesen" sounds a bit "holprig" ;)
>
> In that term I would at least set "Programme herunterladen" under quotes.
>
> regards
> Werner
>
>
> On Wed, Feb 22, 2023 at 2:58 AM Dirk Hohndel via subsurface <
> subsurface@subsurface-divelog.org> wrote:
>
>>
>> I think I have something that works - but it could really benefit from
>> some testing.
>>
>> Would people mind running old and new versions of Subsurface (on Linux,
>> macOS, and Windows) and check for an update (that's under the Help menu
>> entry)?
>> Does the response make sense? If not, what does it say, what should it
>> say.
>>
>> In order to get a feel for how much this has tested, would you also send
>> "success" emails (including what combinations you tested)?
>>
>> Thanks
>>
>> /D
>> ___
>> subsurface mailing list
>> subsurface@subsurface-divelog.org
>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>>
> 
>
>
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: quick hack to fix update check service

[Werner Macho via subsurface]

Hi!

Checked with Subsurface-4.9.3-x86_64.AppImage
and Subsurface-5.0.10-x86_64.AppImage on debian bookworm (testing) with the
following messages:
German translation for "bitte auf unserer Programme herunterladen Seite
nachlesen" sounds a bit "holprig" ;)

In that term I would at least set "Programme herunterladen" under quotes.

regards
Werner


On Wed, Feb 22, 2023 at 2:58 AM Dirk Hohndel via subsurface <
subsurface@subsurface-divelog.org> wrote:

>
> I think I have something that works - but it could really benefit from
> some testing.
>
> Would people mind running old and new versions of Subsurface (on Linux,
> macOS, and Windows) and check for an update (that's under the Help menu
> entry)?
> Does the response make sense? If not, what does it say, what should it say.
>
> In order to get a feel for how much this has tested, would you also send
> "success" emails (including what combinations you tested)?
>
> Thanks
>
> /D
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Transifex translation PRs - and a question about the German translation

[Werner Macho via subsurface]

Hi Dirk,
I am one of the translators, but honestly I cannot remember if I
preferred "Sie" or "Du".
I also have no strong opinion about that, except that I usually find the
"Du" in opensource Projects more welcoming ("you can join us, you can work
with us, you can change something") than the "stay away - Sie" in
proprietary software, but I also know (very few) people who feel offended
by "Du".
So - whatever outcome it will bring, I am fine with it and would help to
rework the translation.

regards
Werner

On Mon, Feb 20, 2023 at 12:35 AM Dirk Hohndel via subsurface <
subsurface@subsurface-divelog.org> wrote:

> To those of you subscribed to GitHub notification... my apologies for the
> ~420 emails that you received in the last 20 hours from Github.
> They deprecated the API that I used to update the translations and
> enabling the GitHub integration seemed like the logical thing to do - I'm
> not so sure anymore.
>
> For those of you working on the German translations - I notice that
> someone started shifting from "Sie" to "Du"... I'd love to have a
> conversation about the preference amongst the German translators... I don't
> have an opinion (I never use software in German), but I want to make sure
> we are consistent.
>
> Thanks
>
> /D
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: heads up

[Werner Macho via subsurface]

enjoy the trip and being disconnected ..
And don't forget to go diving ;) I'll do the same on saturday .

regards
Werner

On Thu, Jun 17, 2021 at 10:04 AM Jason Bramwell via subsurface <
subsurface@subsurface-divelog.org> wrote:

> I echo Alberto’s thoughts, enjoy your trip, stay safe and we’ll all be
> here once you are back.
>
> Jb
>
> Sent from my iPhone
>
> On 17 Jun 2021, at 08:52, tormento via subsurface <
> subsurface@subsurface-divelog.org> wrote:
>
> 
> And you did the best decision ever.
>
> Enjoy your trip and your family. We deserve lot of love.
>
> Alberto
>
> Il giorno mer 16 giu 2021 alle 23:46 Dirk Hohndel via subsurface <
> subsurface@subsurface-divelog.org> ha scritto:
>
>> Hi Everyone,
>>
>> Just a quick heads up - I'll be on a family trip next week... and I
>> decided not to take a computer with me.
>>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Facebook

[Werner Macho]

congratulations to drop facebook!
I left facebook about a year ago and never regret - to me it is not a
social network anymore but rather an asocial advertising page.

publishing on twitter is a good idea - although I think there are more
people with facebook accounts than twitter.

anyway I welcome this move!
thanks a lot
regards
Werner

On Wed, Oct 30, 2019 at 9:10 AM Dirk Hohndel  wrote:

>
> On Oct 30, 2019, at 3:24 AM, Robert Helling  wrote:
>
>
> Quick heads up, I have just deleted the Subsurface Facebook page. It has
> become clear to me over the last few weeks that I cannot in good conscience
> do any business with that company, even if that business is only to give
> reason to people to engage with Facebook in the first place. There are
> plenty of other venues for users to get in contact with us.
>
>
> I think this is a bold move but the right decision. I wish I could be as
> strong.
>
>
> I'm not sure this is about being strong as much as about being fed up.
>
> Speaking of „other venues“, maybe this is the right time to revive the
> Subsurface Twitter account so we have at least one outlet where our users
> would not have to poll to find information about our software. My password
> manager has a password for the SubsurfaceLog account but twitter.com is
> currently down so I cannot check if I can still log in.
>
>
> Twitter isn't down for me. Strange. And yes, we should use that to
> announce releases and other interesting stuff.
>
> /D
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: latest Android Beta

[Werner Macho]

Hi,
Just tried it on my oneplus x without knowing what the problem was..
The opening and closing of dive trips seem to work a bit better now. It 
took ages before (the animation seemed to stop) and now it is still slow 
but better (maybe only my personal imagination).

Everything else works smooth.. No problems so far

Regards
Werner

On 20 September 2019 21:17:47 Dirk Hohndel  wrote:

At some point soon (depending on the Google Play Gods) a new beta version 
for Android should become available - 2.2.1 (4.9.3.30).
As this fixes a super-annoying problem for OnePlus phone users (which made 
Subsurface-mobile pretty much unusable for them), I'd love to promote this 
to production, soon, but I want to make sure that this doesn't break 
something else by mistake.


So if people with an Android device could be on the lookout for that 
version (I assume everyone here is on the beta channel, but you can also 
side load it from downloads/testing) and give it some good testing and then 
REPORT BACK HERE, that would be highly appreciated.


(and yes, I got so frustrated with this that I bought a used OnePlus 6 in 
order to be able to actually connect to it with adb while Subsurface-mobile 
is running so I was able to poke at what was happening...)


Thanks

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




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

Re: Testing v392 with OSTC Sport

[Werner Macho]

Hi
Was able to reproduce.. It seems like my OSTC sport is detected as OSTC 3.
Hope the log will go through.
Switching manually to OSTC sport results in not being able to download 
anything.

(log can be sent if needed)

Regards
Werner


On 13 July 2017 3:04:04 pm Dirk Hohndel  wrote:


[bringing this back as a response to the original question]

On Thu, Jul 13, 2017 at 02:01:30PM +0200, Matthias Heinrichs wrote:

Hi,

> From: Werner Macho 
> To: Subsurface Mailing List 
> Subject: Testing v392 with OSTC Sport
> There is no reaction when I switch the Dive Computer to "OSTC Sport" but
> accidentally I hit the retry button while the Dive Computer was set to
> "OSTC 3" and everything worked.

How is the App deciding to which BLE device it's connecting?


It tries to associate Bluetooth names (and the correspondong addresses)
with known patterns for dive computer names. I'm actually surprised that
this didn't end up with an error that it can't determine the address - but
maybe the slightly odd BT names of the OSTC devices worked out in our
favor here and it was misdetected?

Can you reproduce this behavior? If yes, I'd love to see the
subsurface.log for such a successful attempt


To download the logs, both versions (hwOS2 Tech and Sport) are compatible
and the Bluetooth name should not matter. OSTC4 is different, of course.


That's what worries me about this whole thing, TBH. It shouldn't work, and
if it did work, it shouldn't make a difference. So what's going on?

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
"0.000: Successfully opened logfile/storage/emulated/0/subsurface.log"
"0.000: Starting Subsurface-mobile:2.0(4.6.4.392):Android Nougat 
(7.1):arm:en-GB"
"0.000: build with Qt Version 5.9.1, runtime from Qt Version 5.9.1"
"localDevice OnePlus X is valid, starting discovery"
paired Device type 3 with address "00:80:25:49:F9:4D"
paired Device type 3 with address "LE:00:80:25:49:F9:4D"
Found new device: "OSTC 3" "00:80:25:49:F9:4D"
"this could be a Heinrichs Weikamp OSTC family"
adding new btDCs entry (detected DC) "OSTC 3" 4 5 "00:80:25:49:F9:4D"
Found new device: "OSTC 3" "LE:00:80:25:49:F9:4D"
"this could be a Heinrichs Weikamp OSTC family"
adding new btDCs entry (detected DC) "OSTC 3" 4 5 "LE:00:80:25:49:F9:4D"
Paired = "OSTCs 12100" "00:80:25:49:F9:4D"
Paired = "OSTCs 12100" "LE:00:80:25:49:F9:4D"
"Created position source android"
"0.018: Created position source android"
"0.018: location service is available"
getDetectedVendorIndex "" 4
getDetectedProductIndex 5
getDetectedVendorIndex "" 4
getDetectedVendorIndex "" 4
getDetectedProductIndex 5
getDetectedProductIndex 5
getDetectedVendorIndex "Heinrichs Weikamp" 4
getDetectedProductIndex 5
Both point size and pixel size set. Using pixel size.
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
"0.631: Switching to no cloud mode"
"0.631: working in no-cloud mode"
"0.633: Load dives from local cache"
"0.649: Successfully opened dive data"
"0.651: 0 dives loaded"
"0.652: working in no-cloud mode, finished loading 0 dives from 
/data/user/0/org.subsurfacedivelog.mobile/files/cloudstorage/localrepo[master]"
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
Using the following font: Roboto
qqwindow devicePixelRatio 3 3
qqwindow screen has ldpi/pdpi 72 146.967
"1.486: AppState changed to active with no save ongoing and no unsaved changes"
qrc:/templates/ApplicationHeader.qml:140: TypeError: Cannot read property of 
null
"1.624: Credential scrn: hide kbd was: invisible"
Both point size and pixel size set. Using pixel size.
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
Both point size and pixel size set. Using pixel size.
qrc:/templates/ApplicationHeader.qml:84:13: QML Heading: Binding loop detected 
for property "width"
"16.445: DCDownloadThread started for 00:80:25:49:F9:4D"
Starting download from  BT
Starting the thread 0
connecting to Uuid "{1101--1000-8000-00805f9b34fb}"
connectToService() "00:80:25:49:F9:4D" "{1101--1000-8000-00805f9b34fb}"
Connnecting via insecure rfcomm
Connecting socket
"LocalDeviceBroadcastReceiver::onReceive(

Re: Testing v392 with OSTC Sport

[Werner Macho]

Hi!

Tried it 2 times yesterday and it was reproducible.
Going to copy the log today evening as I think it will still be
reproducible ;) (unless there is a new version out there)

And there is already the list in subsurface where you can choose from.
That's how I choose OSTC Sport and nothing happened while "accidentally"
OSTC3 worked.

regards
Werner

On Thu, Jul 13, 2017 at 3:39 PM, Matthias Heinrichs <
matthias.heinri...@heinrichsweikamp.com> wrote:

> Am 13.07.2017 um 15:03 schrieb Dirk Hohndel:
>
>> It tries to associate Bluetooth names (and the correspondong addresses)
>> with known patterns for dive computer names. I'm actually surprised that
>> this didn't end up with an error that it can't determine the address - but
>> maybe the slightly odd BT names of the OSTC devices worked out in our
>> favor here and it was misdetected?
>>
>
> I'd prefer a small pop-up with a list to choose from (Detected devices).
> Makes this all a bit more robust and future proof. In case /we/ choose the
> rename the newest model different /again/.
>
> Divemate had the same problems and they now keep a list of all possible BT
> names in their code. I still use one of the earliest OSTC3 BLE prototypes
> personally and it still has it's default name like "BlueMod+SR", for
> example.
>
> Regards,
> Matthias
>
>
> --
> heinrichs weikamp gmbh * Adlerstr. 7 * 79098 Freiburg * Germany
>
> Amtsgericht Freiburg HRB 713558 * Gerichtsstand Freiburg im Breisgau
> Geschäftsführer: Matthias Heinrichs, Christian Weikamp
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Testing v392 with OSTC Sport

[Werner Macho]

Hi List,

A "strange" behaviour I found yesterday evening while testing my OSTC Sport.

There is no reaction when I switch the Dive Computer to "OSTC Sport" but
accidentally I hit the retry button while the Dive Computer was set to
"OSTC 3" and everything worked.

I definitely have an OSTC Sport with the latest firmware v10.37 (hope this
is still the latest ;) )

Mobile is a OnePlus X with latest lineageOS.

So I can confirm that I can download all dives - but not with the settings
I expected.
Maybe there is some wiring gone wrong?

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

Re: Android beta... - FTDI download

[Werner Macho]

Hi!

just tested -392.

To my surprise I accidentally got it working by pressing "Retry" to early
while the Dive computer was set to "OSTC3".
Is it possible that there is something wrong?

I definitely have a OSTC sport and while there is no transfer happening
when the Dive Computer is set to "OSTC Sport" it fluently works when I set
it to "OSTC3".

So from my point of view download is working but the declaration is wrong
(or maybe the v10.37
 firmware from an OSTC Sport works like that from OSTC3).

If you still need a complete log - no problem.

thanks and kind regards
Werner

On Wed, Jul 12, 2017 at 12:23 PM, Dirk Hohndel  wrote:

> On Wed, Jul 12, 2017 at 03:39:37AM -0700, Dirk Hohndel wrote:
> > I don't think that it makes any difference, but I pushed -390 to
> > download/test a few hours ago.
>
> I just pushed -392 which will detect if BT is turned off.
>
> /D
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android beta... - FTDI download

[Werner Macho]

Thanks a lot - already downloading 392 and testing today (unfortunately a
bit later) evening.

regards
Werner

On Wed, Jul 12, 2017 at 1:23 PM, Dirk Hohndel  wrote:

> On Wed, Jul 12, 2017 at 03:39:37AM -0700, Dirk Hohndel wrote:
> > I don't think that it makes any difference, but I pushed -390 to
> > download/test a few hours ago.
>
> I just pushed -392 which will detect if BT is turned off.
>
> /D
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android beta... - FTDI download

[Werner Macho]

Hi,

It seems that being "a quiet, non-coding, time-limited
reader of your mailing list" is unfortunately also true for me.

But I also want to share my current experience.

Some weeks ago I was able to download from my OSTC sport to my Oneplus X
with lineageOS.

Now this has unfortunately changed.

Installed is latest LineageOS 14.1 from 6.July 2017
OSTC sport is latest firmware v10.37

bluetooth is paired but there is no connection with download.


>From what I can see in the log.
2.0(4.6.4.380): Android Nougat (7.1): arm:en-GB""0.002: build with Qt
Version 5.9.1, runtime from Qt Version 5.9.1"
localBtDevice isn't valid
...
...
"22.847: DCDownloadThread started for cannot determine address of dive
computer"
Starting download from BT
Starting the thread 0
connecting to Uui
"{1101-000-1000-8000-00805f9b34fb}"
connectToService() "00:00:00:00:00:00"
"1101-000-1000-8000-00805f9b34fb}"
Bt device offline
Failed to connect to device cannot determine address if dive computer .
Device state QBluetoothSocket::UnconnectedState .
Error:QBluetoothSocket::NetworkError
Finishing the thread Insufficient privileges to open the device %s %s (%s)
dives downloaded 0 no new dives downloaded.
...
...

I realised that bluetooth is still off. Is there a way to activate
bluetooth automatically when the bluetooth checkbox is checked?

After activating bluetooth the lines from "Bt device offline" downwards
changed to:

Connnecting via insecure rfcomm
Connecting socket
The connection step took more than expected.
Wait another 20 seconds
Falling back to reverse uuid workaround.
Workaround failed
Failed to connect  same as above

I afterwards also checked with my backup mobile (no custom firmware - just
plain old Android 4.4.2) to make sure it is not a mobile or Android problem.
The same results.

I am also a DiveMate user and the download there is working (if that helps
in any way).

Thanks a lot for creating subsurface. I use it to archive all my dives.
If only I could help more - coding skills are very limited, unfortunately.

regards
Werner


On Mon, Jul 10, 2017 at 12:04 AM, Dirk Hohndel  wrote:

>
> > On Jul 9, 2017, at 3:02 PM, Dietrich Meyer 
> wrote:
> >
> > On Sonntag, 9. Juli 2017 23:53:36 CEST you wrote:
> >>> but with your help I see the problem:
> >>> there is a line
> >>> "Finished thread Insufficient privileges to open the device %s %s (%s)
> >>> dives downloaded 0"
> >>> next line reads
> >>> "50.409: DCDownloadThread finished"
> >>>
> >>> So some privileges problem. probably similar to what was discussed
> >>> previously with selinux
> >>
> >> Actually, that's another potentially painfully misleading error message.
> >> Is there anything useful in the lines just before this?
> >
> > There are three more lines:
> > -
> > "50.393: DCDownloadThread started for /tmp/ttyS1"
> > Starting download from   ftdi
> > Starting the thread 0
> > ---
> >
> > This seems ok. Everything above that and below the "50.409:
> DCDownloadThread
> > finished" is not related to download (pixel size etc).
>
>
> Correct analysis. I'm about NN minutes away from an update that provides
> much better debug information. I hope NN < 30 - but I have learned not to
> make such promises.
>
> /D
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Images needed: Subsurface-mobile user manual

[Werner Macho]

I can do a screenshot downloading from a OSTC sport with BT today evening
if nobody else is faster ;)

regards
Werner

On Tue, Jul 4, 2017 at 10:53 AM, Willem Ferguson <
willemfergu...@zoology.up.ac.za> wrote:

> I am updating the user manual. I need someone to send me an Android
> download screen using a FTDI USB dive computer. I also need a download
> screen using a BT dive computer. Help, please?
>
> Kind regards,
>
> willem
>
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Subsurface 4.7 / 5.0

[Werner Macho]

Hi!

As I am one of the mobile users ;) - I would opt for option 1 .. Tidy
up the room for a clean standard base where everything can base on.
I am more the "let's make it sustainable" guy .. ;)
I would like to see it more used on mobile devices - in comibination
with the desktop and the cloud-git-storage this makes it really nice
to use, look at and show others.

But as I am also a non-coder I'll be happy with everything. Just
wanted to say that subsurface 5.0 would be my favourite.

regards
Werner

On Fri, Jan 20, 2017 at 5:06 PM, Tomaz Canabrava  wrote:
> Hello Crazy People,
>
> It's that time of the year again, where we should talk about new things to
> implement for next versions. I already talked to dirk about one thing that's
> been bothering me, but that needs a bit of background history first:
>
> === BACKGROUND HISTORY ===
>
> Since I joined Subsurface a lot of time ago, the internet didn't really
> existed and geocities was still a thing, the biggest social network of that
> time was IRC and people used to think that computer virus could make people
> sick. As you may know, Those where dark ages, and subsurface was written in
> mainly in GTK back then because it was the language that the Finnish Guy
> (tm) used to know and love. Since than I started a crazy hacking spree
> (followed by Dirk, Robert, Anton, Deivide, and quite a few more) to port the
> original GTK version to Qt, and We actually managed to do that in around six
> months (adding a lot of new things, removing a lot of other things in the
> process, that where brougth back to life a bit later)
>
> There are things that I'm really proud on how I ported Subsurface, Mainly
> the profile is *much* more flexible than the old one was (the proof is that
> Dirk and Robert keep adding things to it even tougth they always complain
> that they don't know C++ or Qt), and there are things that I'm really not
> proud on how I ported ( the MainTab, for instance, and the new Configuration
> - but the configuration is a different story... )
>
> Then Mobile came to Existence and this was mostly a curse because the
> codebase for subsurface wasn't adapted at all for mobile, my port to Qt was
> a "let's try to port this as fast as we can, and also let's keep this as C
> as possible", but Qml doesn't understands C - it understands QObject
> inheritance and Q_PROPERTIES, so a lot of boilerplate code was created (the
> ObjectHelpers and *tons* of code for that) that basically duplicated the C
> code in a C++/Qt way to feed the QML interface on the Mobile usecase.
>
> === Where we stand today ===
>
> One option is to try to make next Subsurface the Subsurface 5:
>
> We have an *Awesome* dive log, and we can continue to develop that, or we
> can do a step back and try to change the *bare minimum* on the core to
> facilitate the integration on the Qml engine without code duplication, my
> take on that would be to port the C-Structs to C++ Classes that inherit from
> QObject (because we can fed those to QML), not messing with the algorithms
> nor anything else that we don't need to touch - those should still be in C,
> algougth compiled with a c++ compiler to have C++ linkage and we can call
> their code  from QML, while also using those parts on the Desktop version
> reducing the amount of duplicated code.
>
> Other option is to try to make next Subsurface the Subsurface 4.7:
>
> Continue duplicating code for the Mobile version (that has a small userbase
> but will probabbly gain an increase of usage over the years) and cleaning /
> improving the Desktop version, changing things on the core as little as we
> need.
>
> What you guys think?
> I'm back on hacking, but I need directions, remember that I don't dive that
> much. :)
>
> Tomaz
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Subsurface BT test with OSTC

[Werner Macho]

Hi all!

Just tested the BT on my OSTC Sport.

Version: Subsurface-4.6-Beta-2-x86_64.AppImage
OS: Debian GNU/Linux 8.6 (jessie)

So far everything worked fine (unfortunately only after a few tries)

At first I always have to "redo" the BT connection every time..
That means whenever I start subsurface and want to download dives the
"Device or mount point" in the windows looks like "00:80:25:49:F9:4D" a
connection with this entry is not possible.

I first have to start the "Remote bluetooth device selection" and scan
for the OSTC Sport again, select the discovered device and click on OK.

Then the MAC Number from the "Device or mount point" changed to "OSTCs
12100" and everything works again.

Unfortunately if I close the download window and open it again - the
"device and mount point" again switched to show only the MAC address
(which is again not working for connections) and I have to rescan again.

Sometimes (to me it seems I tried too fast) it also says "Error
registering the event handler" or even "Insufficient privileges to open
the device 00:80:25:49:F9:4D Heinrichs Weikamp (OSTC Sport)".

But now back to the good news.

I updated the firmware from 10.26 to 10.31 without any problems.
It told me that my firmware is old - I gave it a try and .. now its
10.31 - so no problems so far with a firmware update.

Though I had again some connection problems while assigning the first
connection. The output from console is the following:

./Subsurface-4.6-Beta-2-x86_64.AppImage
can't find Qt localization for locale "en-GB" searching in
"/usr/share/qt5/translations"
Plugins Directory:  QDir( "/tmp/.mount_mHiOKe/usr/bin" , nameFilters = {
"*" },  QDir::SortFlags( Name | IgnoreCase ) , QDir::Filters(
Dirs|Files|Drives|AllEntries ) )
qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 33
error: -1 "Resource temporarily unavailable"
Connection on channel 1 failed. Trying on channel number 5.
Failed to connect to device  00:80:25:49:F9:4D . Device state
QBluetoothSocket::UnconnectedState . Error:
QBluetoothSocket::UnknownSocketError
[9.469210] ERROR: Failed to open the serial port. [in
../../src/hw_ostc3.c:344 (hw_ostc3_device_open)]
qt.bluetooth.bluez: Bluez 5 detected.
qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
qt.bluetooth.bluez: Discovered:  "00:80:25:49:F9:4D" "OSTCs 12100" Num
UUIDs 5 total device 0 cached RSSI 0 Class 7936
qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
The connection on RFCOMM channel number 1 took more than expected. Wait
another 15 seconds.
[5.890507] ERROR: Unsupported command. [in ../../src/hw_ostc3.c:217
(hw_ostc3_transfer)]
The connection on RFCOMM channel number 1 took more than expected. Wait
another 15 seconds.
qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 30
error: -1 "Resource temporarily unavailable"
Failed to connect to device  00:80:25:49:F9:4D . Device state
QBluetoothSocket::UnconnectedState . Error:
QBluetoothSocket::UnknownSocketError
[17.275994] ERROR: Failed to open the serial port. [in
../../src/hw_ostc3.c:344 (hw_ostc3_device_open)]
[2.074706] ERROR: Unsupported command. [in ../../src/hw_ostc3.c:217
(hw_ostc3_transfer)]
QObject::connect: No such slot ConfigureDiveComputer::dc_close()
qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 24
error: -1 "Resource temporarily unavailable"
Connection on channel 1 failed. Trying on channel number 5.
The connection on RFCOMM channel number 5 took more than expected. Wait
another 15 seconds.
qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 24
error: -1 "Resource temporarily unavailable"
Failed to connect to device  00:80:25:49:F9:4D . Device state
QBluetoothSocket::UnconnectedState . Error:
QBluetoothSocket::UnknownSocketError
[6.039782] ERROR: Failed to open the serial port. [in
../../src/hw_ostc3.c:344 (hw_ostc3_device_open)]

Hope this helps a bit.

regards
Werner


On 08/01/17 21:54, Dirk Hohndel wrote:
> 
>> On Jan 8, 2017, at 12:50 PM, Stefan Fuchs > > wrote:
>>
>> Hi All,
>>
>> Am 07.01.2017 um 21:13 schrieb Dirk Hohndel:
>>>
 On Jan 7, 2017, at 12:01 PM, Stefan Fuchs >>> > wrote:

 Hallo Dirk,


 Am 07.01.2017 um 20:40 schrieb Dirk Hohndel:
>
> OK, so that's a USB device, not BT. One of my concerns is our BT
> support - I'm hoping that the newer version of Qt that I switched
> to won't give us any regressions, but of course you never know...
>
 I will be able to recruit at least one OSTC (2C?!) BT beta tester.
 Wolf (in copy) will test the 4.6 beta 2 tomorrow and give some feedback.
>>>
>> Wolf sent me a WhatsApp this afternoon that he successfully tested the
>> download via BT as well.
>> Setup:
>> - Win 10
>> - OSTC 2 "new", hwOS 2.09
>> - Bluetooth via a bt dongle
>>
>> All his dives were downloaded successfully.
> 
> Thank you so much. That really helps me feel more confident about a release.
> 
> /D
> 
> 
> __

Re: Subsurface BT test with OSTC

[Werner Macho]

Hi!

I also an an OSTC (Sport). If testing with this (BT) is still needed I
am more than happy to do it.

regards
Werner

On 07/01/17 21:13, Dirk Hohndel wrote:
> 
>> On Jan 7, 2017, at 12:01 PM, Stefan Fuchs > > wrote:
>>
>> Hallo Dirk,
>>
>>
>> Am 07.01.2017 um 20:40 schrieb Dirk Hohndel:
>>>
>>> OK, so that's a USB device, not BT. One of my concerns is our BT
>>> support - I'm hoping that the newer version of Qt that I switched to
>>> won't give us any regressions, but of course you never know...
>>>
>> I will be able to recruit at least one OSTC (2C?!) BT beta tester.
>> Wolf (in copy) will test the 4.6 beta 2 tomorrow and give some feedback.
> 
> Danke, Rolf (und natürlich Stefan). Das ist super!
> 
> /D
> 
> 
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
> 
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Theoretical Diver Blog

[Werner Macho]

Hi all,

Regarding the blog: really great and nicely explained.
But I found a few typos (at least in the german part for now) which
should be corrected.. Is it possible to do something like a pull
request or should I directly send them?
(for e.g. Nahrung instead of Näherung)

kind regards
Werner

On Mon, Nov 14, 2016 at 12:07 PM, Benjamin  wrote:
> It's in English further down the page.
>
> Benjamin
>
>
> On Mon, 14 Nov 2016, 12:48 Davide DB,  wrote:
>>
>> Great Work indeed,
>>
>> Unfortunately I do not speak German and google translate doesn't grasp
>> very well such articles.
>>
>> On 13 November 2016 at 13:57, Robert Helling  wrote:
>> > Hi,
>> >
>> > I finally got around to do what I had intended to do for more than a
>> > year: Start a blog on the theoretical aspects of diving (many of which I
>> > learned while contributing to Subsurface):
>> >
>> > http://atdotde.de/theoreticaldiver/
>> >
>> > So far, I started with some comments on VPM-B.
>> >
>> > Comment, contribute and spread the word!
>> >
>> > Best
>> > Robert
>> >
>> >
>> > ___
>> > subsurface mailing list
>> > subsurface@subsurface-divelog.org
>> > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>> >
>>
>>
>>
>> --
>> Davide
>> https://vimeo.com/bocio/videos
>> ___
>> subsurface mailing list
>> subsurface@subsurface-divelog.org
>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Next release [was Re: Frequent cloud storage authentication errors with Subsurface 4.5.6 (desktop)]

[Werner Macho]

Hi!

I'd really like to help with testing (Owning a OSTC Sport with
bluetooth) but somehow I can only get the "stable" versions to run.

So no testing with development version. :(

Maybe it's me using debian stable as OS (Qt 5.3.2). But I cannot compile
current master nor v4.5-branch using debian stable using the
scripts/build.sh.

[ 42%] Building CXX object
core/CMakeFiles/subsurface_corelib.dir/qthelper.cpp.o
In file included from
/home/macho/dev/cpp/subsurface/subsurface/./desktop-widgets/mainwindow.h:16:0,
 from
/home/macho/dev/cpp/subsurface/subsurface/qt-models/filtermodels.cpp:8:
/home/macho/dev/cpp/subsurface/subsurface/build/ui_mainwindow.h:24:32:
fatal error: notificationwidget.h: No such file or directory
 #include "notificationwidget.h"
^
compilation terminated.

I will keep on trying to compile ;)

I can also test on Windows 10 but .. I can only find the "normal"
"subsurface-4.5.6.exe" on the homepage.

But I am more than willing to help testing (also on android).
(Doing a diving trip in the beginning of october to Cairns.)

Any hints for me how I can help in the best way?

regards
Werner



On 24/09/16 14:41, Steve wrote:
> 
> 
>> On Sep 22, 2016, at 9:24 PM, Dirk Hohndel  wrote:
>>
>>
>>> On Sep 20, 2016, at 9:00 AM, John Smith  wrote:
>>>
>>> Running 4.5.2-1600 on Windows 10
>>>
>>> The SHARE ON button goes blue in clicking but doesn't open a window.
>>
>> That should work now with the -1619 build. I even tested it on Windows 
>> (crazy, I know).
> 
> Replaced by -1620
> 
>>> Every time I try to import a csv file from my ccr using the import log 
>>> files, subsurface crashes.
>>
>> I didn't notice that you had sent the test file just to me, I just forwarded 
>> it to Miika.
>>
>>> Language always shows Bulgarian rather than English.
>>
>> That should also be fixed in -1619
>>
>>> If you do anything on the language page, it always gives a 'to use new 
>>> language' message even if you are changing time settings.
>>
>> Ditto.
>>
>> BUT: while setting the language works fine now on Linux, it's still not 
>> working on Windows and I don't quite understand why.
> 
> -1620 fixes this on Windows as well.
> 
>> I'd appreciate if you could verify all this (and more testing would be 
>> extremely welcome, too) :-)
> 
> Still true. And please - not just John - we really need more people to test.
> 
> /D
> 
> 
> 1620 tested Bluetooth with DiveSystems ix3m reb and HW OSTC3+ On windows both 
> download dives well.
> Steve
> 
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
> 
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
> 
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

subsurface typo fix

[Werner Macho]

Hi!

I guess it would be easier to create a pull request somewhere but I
could not find which repository is the official one to create a pull
request on.
http://git.subsurface-divelog.org/
https://github.com/torvalds/subsurface

I only found the explaination to create patches which can be sent by
mail (I guess)

So here you are.. It's just a small typo but whenever I see such things
I try to fix them - otherwise it will never be done ;)

Thanks for subsurface! It's great!

kind regards
Werner
>From 354ddf088cac766993f0c902894d4d72a40a12e4 Mon Sep 17 00:00:00 2001
From: Werner Macho 
Date: Wed, 23 Mar 2016 19:46:27 +0100
Subject: [PATCH] typo fix

small typo fix for GUI

Signed-off-by: Werner Macho 
---
 desktop-widgets/configuredivecomputerdialog.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/desktop-widgets/configuredivecomputerdialog.cpp b/desktop-widgets/configuredivecomputerdialog.cpp
index a4fc708..428b326 100644
--- a/desktop-widgets/configuredivecomputerdialog.cpp
+++ b/desktop-widgets/configuredivecomputerdialog.cpp
@@ -1275,6 +1275,6 @@ void ConfigureDiveComputerDialog::dc_close()
 	ui.DiveComputerList->setEnabled(true);
 	ui.logToFile->setEnabled(true);
 	ui.updateFirmwareButton->setEnabled(false);
-	ui.progressBar->setFormat("Disonnected from device");
+	ui.progressBar->setFormat("Disconnected from device");
 	ui.progressBar->setValue(0);
 }
-- 
2.1.4

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