Re: Crash on Windows when importing dives via USB from OSTC2

Hi All, Am 20.04.2017 um 00:04 schrieb Stefan Fuchs: >>> Hi All, >>> >>> unfortunately I see a new crash when importing via USB from my OSTC2. This >>> happens under Windows 10 with current master and was not there about 2 weeks >>> ago. It happens every time at the end of data transfer from the

Re: preparing for a 4.6.4

Hello Dirk, Am 19.04.2017 um 06:15 schrieb Dirk Hohndel: > I'm kinda leaning towards the second option but that means we need to > spend a week or two, focused on testing the latest master and finishing > the translations, again. If people have strong feelings one way or > another, please speak

Re: Suunto DM5 Format changed

Thanks, PR326 On Thu, Apr 20, 2017 at 5:44 PM, Rainer Mohr wrote: > Sent in private mail > > Rainer > > Am 20.04.17 um 16:36 schrieb Miika Turkia: >> >> Hello Rainer, >> >> >> thanks for the heads up. Can you also provide me a sample log so I can >> test our parsing works

Re: Suunto DM5 Format changed

Sent in private mail Rainer Am 20.04.17 um 16:36 schrieb Miika Turkia: Hello Rainer, thanks for the heads up. Can you also provide me a sample log so I can test our parsing works properly? (The change is simple enough, but still I would like to test it up.) miika On Thu, Apr 20, 2017 at

Re: Suunto DM5 Format changed

Hello Rainer, thanks for the heads up. Can you also provide me a sample log so I can test our parsing works properly? (The change is simple enough, but still I would like to test it up.) miika On Thu, Apr 20, 2017 at 3:20 PM, Rainer Mohr wrote: > Hi Miika, Linus, > > Picking

Re: Suunto DM5 Format changed

Hi Miika, Linus, Picking up an old thread from two years back... I got the first file from the wild with yet another Suunto DM5 format in the Profile BLOB field. This time its blocks of 26 Bytes, no idea what they changed - Maybe a new firmware for The EON Steel made that necessary, who

RE: [PATCH] MarbleDebug: don't use a class extending QIODevice as a null device

> -Original Message- > From: Thiago Macieira [mailto:thi...@kde.org] > [...] > Sounds good, but do we need this setEnabled() in the first place? Is it used > anywhere? It's meant to be used by a filter installed by QLoggingCategory::installFilter (see the example