This workaround works:
importQtQuick2.0
importQtQuick.Controls2.12
StackView
{
propertyvarqueue:[]
functionwaPush(item,properties,operation){
if(queue.length||
!push(item,properties,operation))
{
queue.push({i:item,p:properties,o:operation});
applyTimer();
}
}
functionwaClear(){
que
Hello,
Qt 5.12.8, Android 10.
We're getting the subject message in app log when trying to push an item
in some occasions. And thus the item is not pushed.
Is it a bug? We've tried to use this custom component with no luck:
importQtQuick2.0
importQtQuick.Controls2.12
StackView
{
propertyv
On Tuesday, 21 July 2020 10:32:13 PDT Alexander Carôt wrote:
> Hej Thiago,
>
> > Whether they work or not is irrelevant, since you shouldn't be shipping
> > the
> > same certificate to all users. You'd have to make it extremely long-lived
> > (expiry 20 years from now). Generating a short-lived on
Hej Thiago,
> Whether they work or not is irrelevant, since you shouldn't be shipping the
> same certificate to all users. You'd have to make it extremely long-lived
> (expiry 20 years from now). Generating a short-lived one (3 months) limits
> the
> damage if it somehow gets misused.
just
Am 21.07.2020 um 18:58 schrieb Doogster:
My program uses both Qt and a C API that takes, as parameters, UTF-8
const char * strings.
Is this the correct way to convert a QString containing a UTF8 string
to that format?
qString.toUtf8().constData()
Wasn't this question already answered?
https://
On Tuesday, 21 July 2020 09:58:54 PDT Doogster wrote:
> My program uses both Qt and a C API that takes, as parameters, UTF-8
> const char * strings.
>
> Is this the correct way to convert a QString containing a UTF8 string
> to that format?
>
> qString.toUtf8().constData()
Just remember th
Pay attention:
::toUtf8() returns a QBytearray. After your complete call, the constData() is
invalid.
You must copy the pointer before the QBytearray gets out of scope.
Am July 21, 2020 4:58:54 PM UTC schrieb Doogster :
>My program uses both Qt and a C API that takes, as parameters, UTF-8
>cons
On Tuesday, 21 July 2020 09:13:18 PDT Alexander Carôt wrote:
> Well, it's worth learning it and also from your answer I understand that the
> current files in the example server do *not* work. This is a good
> confirmation because indeed it doesn't :-)
Whether they work or not is irrelevant, since
My program uses both Qt and a C API that takes, as parameters, UTF-8
const char * strings.
Is this the correct way to convert a QString containing a UTF8 string
to that format?
qString.toUtf8().constData()
___
Interest mailing list
Interest@qt-project.o
> You'll have to learn the OpenSSL API or to require the openssl command to be
> present.
>
> I know the OpenSSL API is not the simplest or easiest to use. But I don't see
> a way out.
Well, it's worth learning it and also from your answer I understand that the
current files in the example ser
On Tuesday, 21 July 2020 01:07:45 PDT Alexander Carôt wrote:
> How do I generate the required CRT and KEY - File for localhost which shall
> work on every other client's localhost.
You'll have to learn the OpenSSL API or to require the openssl command to be
present.
I know the OpenSSL API is not
>> How do I generate the required CRT and KEY - File for localhost which shall
>> work on every other client's localhost.
Or asked in a different way: The qwebsocketserver - example:
https://code.qt.io/cgit/qt/qtwebsockets.git/tree/examples/websockets/sslechoserver?h=5.15
already has the CERT-
> I don't see how that affects anything. Are you saying you can't update the
> application? If you can't update the application, how are you going to apply
> the fixes we're discussing here?
Misunderstanding :-) Of course I apply application updates in more or less
regular intervals of several
13 matches
Mail list logo
