On Mon, Apr 17, 2017 at 3:28 PM, Robert Sevat wrote:
>
> I am unable to setup a bluetooth connection with subsurface to my
> shearwater perdix on linux. I've run out of troubleshooting ideas. Maybe
> you guys have some pointers/ideas.
This looks like the BLE version (Bluetooth
Can this be applied? Or something similar?
On 6 Apr. 2017 8:28 am, "Rick Walsh" wrote:
> Setting up an RFCOMM connection has not been required for a long time.
>
> Reported-by: Stephen Hemminger
> Signed-off-by: Rick Walsh
Hi Robert,
On 18 Apr. 2017 11:59 am, "Robert Sevat" wrote:
Hello,
I am unable to setup a bluetooth connection with subsurface to my
shearwater perdix on linux. I've run out of troubleshooting ideas. Maybe
you guys have some pointers/ideas.
-
System
On segunda-feira, 17 de abril de 2017 14:53:12 PDT Lubomir I. Ivanov wrote:
> Stefan, could you please try building and running the attached patch?
> you can toggle the debugging with MarbleDebug::setEnabled(true/false)
> e.g. from the Subsurface source code.
Or by setting in your environment:
On segunda-feira, 17 de abril de 2017 14:41:13 PDT Lubomir I. Ivanov wrote:
> On 18 April 2017 at 00:18, Thiago Macieira wrote:
> > On segunda-feira, 17 de abril de 2017 14:10:28 PDT Lubomir I. Ivanov
wrote:
> >> i guess we could just do a:
> >> void
On 18 April 2017 at 00:18, Thiago Macieira wrote:
> On segunda-feira, 17 de abril de 2017 14:10:28 PDT Lubomir I. Ivanov wrote:
>> i guess we could just do a:
>> void MarbleDebug::setEnabled(bool enabled)
>> {
>> Marble::loggingCategory.setEnabled(enabled);
>>
On segunda-feira, 17 de abril de 2017 14:10:28 PDT Lubomir I. Ivanov wrote:
> i guess we could just do a:
> void MarbleDebug::setEnabled(bool enabled)
> {
> Marble::loggingCategory.setEnabled(enabled);
> MarbleDebug::m_enabled = enabled;
> }
I'd go a little further and drop the m_enabled
On 18 April 2017 at 00:02, Lubomir I. Ivanov wrote:
> On 17 April 2017 at 23:46, Thiago Macieira wrote:
>> This disables the debug output for the default category, that is, every user
>> of qDebug().
>>
>
> yep, i later figured that might happen.
>
>> I
On segunda-feira, 17 de abril de 2017 13:24:26 PDT Lubomir I. Ivanov wrote:
> On 17 April 2017 at 22:29, Thiago Macieira wrote:
> > On segunda-feira, 17 de abril de 2017 12:01:48 PDT Lubomir I. Ivanov
wrote:
> >> QDebug mDebug()
> >>
> >> {
> >>
> >> return QDebug(
On 17 April 2017 at 22:29, Thiago Macieira wrote:
> On segunda-feira, 17 de abril de 2017 12:01:48 PDT Lubomir I. Ivanov wrote:
>> QDebug mDebug()
>> {
>> return QDebug( QtDebugMsg ); // or "return qDebug();"
>> }
>>
>> which will essentially enable debug output for
On 14-04-17 22:04, Anton Lundin wrote:
On 14 April, 2017 - Jef Driesen wrote:
On 2017-04-13 17:04, Jef Driesen wrote:
I tried a different approach yesterday. Instead of adding 1024 to
the calibration value, I simply used the stored value as is, and
calculated the average ppO2 over all three
On 14-04-17 21:57, Anton Lundin wrote:
On 13 April, 2017 - Jef Driesen wrote:
On 2017-04-12 10:47, Anton Lundin wrote:
The issue with current libdivecomputer DC_SAMPLE_PPO2 is that you cant
distinguish between ha "real" "voted" pO2 and the raw sensor value.
I would like to see a option to
Hello Lubomir,
Am 17.04.2017 um 21:01 schrieb Lubomir I. Ivanov:
> your best bet is to change the function to this:
>
> QDebug mDebug()
> {
> return QDebug( QtDebugMsg ); // or "return qDebug();"
> }
>
> which will essentially enable debug output for everything in Marble,
> until we write a
On 17-04-17 07:33, Miika Turkia wrote:
I have an crash on exit, with some compilations occurs always, and
doesn't crash with other compilations from same source. The attached
patch might fix it, but I am not certain due to the weird
crash/no-crash behavior.
I had the exact same crash, and
14 matches
Mail list logo