Re: Roll our own qUtf8Printable()?

On Montag, 26. Februar 2018 02:33:58 CET Thiago Macieira wrote: > > [Sidenote: There's a reason the C++-standard disallows reference counting > > for its string class.] > > There is, but this isn't it. The concern is the unexpected memory allocation > when calling a non-const function. The

Re: Roll our own qUtf8Printable()?

On Montag, 26. Februar 2018 03:19:48 CET Thiago Macieira wrote: > On domingo, 25 de fevereiro de 2018 17:13:11 PST Thiago Macieira wrote: > > But there's another option, which is to avoid a copy of the QString if the > > input is already a QString. Let me try a few variations of possible > >

Re: Roll our own qUtf8Printable()?

On Montag, 26. Februar 2018 02:13:11 CET Thiago Macieira wrote: > On domingo, 25 de fevereiro de 2018 15:00:38 PST Lubomir I. Ivanov wrote: > > wrote: > > > Dear all, > suggested here: > > > So what do you think about rolling our own helper function: > > > > > >

RE: password rest

On February 25, 2018 5:09:24 PM PST, Glenn Moore wrote: >Dirk, > >How is it that the cloud storage log for the same account is different >on 2 computers at the same time? > > > >I can save and open cloud storage for my account on one computer. All >looks good. > >Open

Re: Roll our own qUtf8Printable()?

On domingo, 25 de fevereiro de 2018 17:13:11 PST Thiago Macieira wrote: > But there's another option, which is to avoid a copy of the QString if the > input is already a QString. Let me try a few variations of possible > solutions and compile Qt to see what happens. > > I'll BRB. Change to Qt:

Re: Roll our own qUtf8Printable()?

On domingo, 25 de fevereiro de 2018 14:34:28 PST Berthold Stoeger wrote: > I think the compiler can't optimize the copy away, because QString doesn't > copy the string, but does reference counting. I'm not sure if it is allowed > to throw away the side effects of the ref()/deref() calls? This does

Re: Roll our own qUtf8Printable()?

On domingo, 25 de fevereiro de 2018 15:00:38 PST Lubomir I. Ivanov wrote: > wrote: > > Dear all, > > > > In many places, QStrings are converted to C-style strings with an > > expression of the kind > > > > s.toUf8().data() > > > > I have a patch replacing all of

Re: Roll our own qUtf8Printable()?

On 25 February 2018 at 21:39, Berthold Stoeger wrote: > Dear all, > > In many places, QStrings are converted to C-style strings with an expression > of the kind > s.toUf8().data() > > I have a patch replacing all of them with > qUtf8Printable(s) > > The idea is that

Re: Roll our own qUtf8Printable()?

Hi, On Sonntag, 25. Februar 2018 22:40:00 CET Lubomir I. Ivanov wrote: > On 25 February 2018 at 21:39, Berthold Stoeger > > wrote: > > Dear all, > > Much to my surprise, qUtf8Printable() produced larger code. The reason is > > that it is defined as a macro in : > >

Re: Roll our own qUtf8Printable()?

On 25 February 2018 at 23:40, Lubomir I. Ivanov wrote: > On 25 February 2018 at 21:39, Berthold Stoeger > wrote: >> Dear all, >> >> In many places, QStrings are converted to C-style strings with an expression >> of the kind >> s.toUf8().data() >>

Re: Roll our own qUtf8Printable()?

On 25 February 2018 at 21:39, Berthold Stoeger wrote: > Dear all, > > In many places, QStrings are converted to C-style strings with an expression > of the kind > s.toUf8().data() > > I have a patch replacing all of them with > qUtf8Printable(s) > > The idea is that

Roll our own qUtf8Printable()?

Dear all, In many places, QStrings are converted to C-style strings with an expression of the kind s.toUf8().data() I have a patch replacing all of them with qUtf8Printable(s) The idea is that - according to the documentation - this is equivalent to s.toUtf8().constData() The latter should

Re: Latest update

I'll admit that I have no idea what gates the ability of an app to be moved to SD card. I don't own any Android devices that support SD card, so I can't even test this... /D On February 25, 2018 2:58:48 AM PST, paul.e.c...@virgin.net wrote: >Hi, > I have the Beta version of subsurface mobile

Fwd: Cylinder handling - when allow to delete a cylinder

Hello Linus, we have two pending Subsurface PRs since some time regarding cylinder handling where Dirk and I are unsure if it's the right thing to do. Also from the mailing list there was no feedback on my question. Would you mind to have a look, mainly at #885 and tell us what you think? #890