<feed xmlns='http://www.w3.org/2005/Atom'>
<title>subsurface.git/core, branch v4.9.7</title>
<subtitle>forked from https://github.com/subsurface/subsurface</subtitle>
<id>https://git.tsegers.com/subsurface.git/atom?h=v4.9.7</id>
<link rel='self' href='https://git.tsegers.com/subsurface.git/atom?h=v4.9.7'/>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/'/>
<updated>2020-09-22T21:10:12Z</updated>
<entry>
<title>cleanup: silence two compiler warnings in git-access.c</title>
<updated>2020-09-22T21:10:12Z</updated>
<author>
<name>Berthold Stoeger</name>
<email>bstoeger@mail.tuwien.ac.at</email>
</author>
<published>2020-09-22T19:15:55Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=fb93232931569cb6386d1150486b9e12c28f0678'/>
<id>urn:sha1:fb93232931569cb6386d1150486b9e12c28f0678</id>
<content type='text'>
gcc complained about two constructs of the kind
	remote_id &amp;&amp; SSRF_INFO("...");
And while I am not a fan of excessive warnings, I must say
it has a point here. That's just code obfuscation. In fact,
it appears that the condition was wrong - the SSRF_INFO
should probably be invoked if remote_id is NULL. The way
it was written it would be invoked if it was *not* NULL.

Change both instances to unfancy if statements.

Signed-off-by: Berthold Stoeger &lt;bstoeger@mail.tuwien.ac.at&gt;
</content>
</entry>
<entry>
<title>translations: initialize water type strings at run time</title>
<updated>2020-09-21T20:42:00Z</updated>
<author>
<name>Berthold Stoeger</name>
<email>bstoeger@mail.tuwien.ac.at</email>
</author>
<published>2020-09-21T19:44:35Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=9d3b15bf9cb758e9f371d5f5f9eec0a3a2b0a4e2'/>
<id>urn:sha1:9d3b15bf9cb758e9f371d5f5f9eec0a3a2b0a4e2</id>
<content type='text'>
The water type strings were static and therefore passed through
gettextFromC::tr() before main(). One would hope to get a warning
in such a case, but this is not the case.

Therefore, use the QT_TRANSLATE_NOOP macro to register the strings
in Qt's translation system and translate the list when needed.

Signed-off-by: Berthold Stoeger &lt;bstoeger@mail.tuwien.ac.at&gt;
</content>
</entry>
<entry>
<title>Bailout segment is part of bottom time</title>
<updated>2020-09-21T18:42:02Z</updated>
<author>
<name>Robert C. Helling</name>
<email>helling@atdotde.de</email>
</author>
<published>2020-09-21T08:51:19Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=ee7908028035b28d0ec110c65f0ebe212960352c'/>
<id>urn:sha1:ee7908028035b28d0ec110c65f0ebe212960352c</id>
<content type='text'>
The clock is only valid in ascent. In each cycle of the
'critial volume algorithm' it re-initialized to the
bottom time at the beginning of deco. So the time spent
on bailout should be added to this bottom time.

Thanks to Coverty for spotting this.

Coverity-scan:  CID-362079

Signed-off-by: Robert C. Helling &lt;helling@atdotde.de&gt;
</content>
</entry>
<entry>
<title>selection: when changing current dive make sure it is selected</title>
<updated>2020-09-21T01:23:57Z</updated>
<author>
<name>Berthold Stoeger</name>
<email>bstoeger@mail.tuwien.ac.at</email>
</author>
<published>2020-09-20T12:48:15Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=f42dee8ac2e40e02ffd2b177f7d97e1b4ba8acea'/>
<id>urn:sha1:f42dee8ac2e40e02ffd2b177f7d97e1b4ba8acea</id>
<content type='text'>
When an undo command selected invisible dives, a current dive outside
of the list of selected dives was chosen. This could have the very
unfortunate effect that the current dive was set, though not selected.
From an UI point of view this meant that the dive was displayed, but
edits would not be registered.

Change the setClosestCurrentDive function to select the current dive.

Signed-off-by: Berthold Stoeger &lt;bstoeger@mail.tuwien.ac.at&gt;
Signed-off-by: Dirk Hohndel &lt;dirk@hohndel.org&gt;
</content>
</entry>
<entry>
<title>core/bluetooth: only Linux / Windows are supported by libdc rfcomm</title>
<updated>2020-09-20T02:26:56Z</updated>
<author>
<name>Dirk Hohndel</name>
<email>dirk@hohndel.org</email>
</author>
<published>2020-09-19T21:58:26Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=780cb4fce75b0014485e62d628f9b94bcaae4f8f'/>
<id>urn:sha1:780cb4fce75b0014485e62d628f9b94bcaae4f8f</id>
<content type='text'>
For Android the Qt Bluetooth code seems to work just fine. And for macOS
nothing appears to work right now, but at least the Qt implementation compiles
and links.

Signed-off-by: Dirk Hohndel &lt;dirk@hohndel.org&gt;
</content>
</entry>
<entry>
<title>core/bluetooth: switch to use libdivecomputer rfcomm support</title>
<updated>2020-09-20T02:26:26Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2020-09-19T21:16:08Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=e1befbea0aaa537945741ae9d14e590f4ca5171b'/>
<id>urn:sha1:e1befbea0aaa537945741ae9d14e590f4ca5171b</id>
<content type='text'>
The Qt based implementation apparently got broken at some point and now fails
to connect to rfcomm dive computers like the Shearwater Petrel.

This uses the libdivecomputer rfcomm backend. Tested to work with bluez on
Linux as well as with the native Windows implementation.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Dirk Hohndel &lt;dirk@hohndel.org&gt;
</content>
</entry>
<entry>
<title>Update Shearwater sample time calculation</title>
<updated>2020-09-19T18:20:27Z</updated>
<author>
<name>Miika Turkia</name>
<email>miika.turkia@gmail.com</email>
</author>
<published>2020-09-19T10:25:47Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=db6acfdd27dbf0b20e83422970d3788ea87ae8d7'/>
<id>urn:sha1:db6acfdd27dbf0b20e83422970d3788ea87ae8d7</id>
<content type='text'>
At least Shearwater Cloud seems to use multiple formats for sample time
recorded in the database. Sometimes the time is in seconds, sometimes in
milliseconds, and sometime it is something I have no idea about. Thus
switching to calculating the sample id myself and using sample interval
to calculate the actual sample time. Seems to be more reliable than
trying to guess what format Shearwater is using for this specific dive.

Signed-off-by: Miika Turkia &lt;miika.turkia@gmail.com&gt;
</content>
</entry>
<entry>
<title>media: read timestamp from mvhd header of MP4/QuickTime videos</title>
<updated>2020-09-19T18:11:16Z</updated>
<author>
<name>Berthold Stoeger</name>
<email>bstoeger@mail.tuwien.ac.at</email>
</author>
<published>2020-09-19T11:51:44Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=75be59c76dedfd540809d36bdc341032c10492d2'/>
<id>urn:sha1:75be59c76dedfd540809d36bdc341032c10492d2</id>
<content type='text'>
ExifTools (and probably other meta-data editors) modifies the
mvhd creation date, but leaves the individual creation dates
in the tracks unchanged. Therefore, use the mvhd atom.

Reported-by: Eric Tanguy &lt;erictanguy2@orange.fr&gt;
Signed-off-by: Berthold Stoeger &lt;bstoeger@mail.tuwien.ac.at&gt;
</content>
</entry>
<entry>
<title>Extend BLE uuid matching to the characteristics, add ignore-list</title>
<updated>2020-09-17T14:54:35Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2020-09-16T18:01:09Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=aa95a9a744f28612bbb7706e4e45ba5b2aa5279d'/>
<id>urn:sha1:aa95a9a744f28612bbb7706e4e45ba5b2aa5279d</id>
<content type='text'>
This extends the uuid matching to the low-level characteristics too, so
that we can ignore the McLean Extreme characteristics that aren't
interesting.

It also renames the uuid matching to be about a "uuid_list" rather than
being about the service we're matching, since we're now using it for
other uuid's than just services.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Fix 'uud' typo in BLE uuid matching code</title>
<updated>2020-09-17T14:54:35Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2020-09-16T17:12:56Z</published>
<link rel='alternate' type='text/html' href='https://git.tsegers.com/subsurface.git/commit/?id=981c1cb1d30ff68baf4c01179866c4b827747960'/>
<id>urn:sha1:981c1cb1d30ff68baf4c01179866c4b827747960</id>
<content type='text'>
Silly typo with a missing 'i' in 'uuid' that happened when I wrote this
code originally, and that compiled fine thanks to the error being
duplicated with cut-and-paste to all relevant places.

Fix it now, since I'll extend the uuid matching to the actual
characteristics for the McLean Extreme.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
</feed>
