> -Original Message-
> From: Nuno Santos [mailto:nunosan...@imaginando.pt]
> Sent: Wednesday, March 02, 2016 5:22 PM
> To: Koehne Kai
> Cc: interest
> Subject: Re: [Interest] Enabling OpenSSL on a shared build of Qt
>
> I think I have missed something. If it has support enabled by defaul
> > Ah you mean by "knowing types at compile time" is actually defined
> types, so you actually defining classes at run-time?
> Sina,
> No, I didn't mean that. You can't define classes at runtime as C++ is not
> a dynamic language.
>
Yeah, but sometimes qt makes me confuse, reflection was also not
On quarta-feira, 2 de março de 2016 15:29:16 PST Thiago Macieira wrote:
> A better solution: copy the two libraries to your application's
> /Contents/Frameworks
Oh, I should point out: if you do this, you'll be distributing cryptographic
code. If your application is not open source, you
On quarta-feira, 2 de março de 2016 23:15:09 PST Nuno Santos wrote:
> cat out | grep ssl
> loaded library "/usr/lib/libssl.dylib"
> qt.network.ssl: QSslSocket: cannot resolve SSL_set_psk_client_callback
> qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_client_method
> qt.network.ssl: QSslSocket:
On quinta-feira, 3 de março de 2016 00:08:38 PST Jason H wrote:
> > Another idea: why don't you use QTemporaryFile?
>
> Thought about it. It takes a template specification which does not allow me
> to specify the exact filename. "If the templateName does not contain XX
> it will automatically
Thiago,
I have run with QT_DEBUG_PLUGINS=1 and redirected stderr to out and “greped”
with ssl:
cat out | grep ssl
loaded library "/usr/lib/libssl.dylib"
qt.network.ssl: QSslSocket: cannot resolve SSL_set_psk_client_callback
qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_client_method
qt.net
> Another idea: why don't you use QTemporaryFile?
Thought about it. It takes a template specification which does not allow me to
specify the exact filename. "If the templateName does not contain XX it
will automatically be appended and used as the dynamic portion of the filename."
_
On quarta-feira, 2 de março de 2016 20:20:32 PST NoRulez wrote:
> Hello,
>
> what is the minimum required Mac OS X SDK?
Latest. There's no point in using any SDK but the latest.
You can compile applications (and Qt itself) to target older OSes, even with
the latest SDK.
--
Thiago Macieira - t
On quarta-feira, 2 de março de 2016 09:53:46 PST Thiago Macieira wrote:
> On quarta-feira, 2 de março de 2016 17:45:15 PST Jason H wrote:
> > Let me expand on this, I can f->setParent(reply), but I also need to
> > delete
> > the file from disk. If I rely on the parent/child object deletion, I can'
> Am 02.03.2016 um 20:20 schrieb NoRulez :
>
> Hello,
>
> what is the minimum required Mac OS X SDK?
> I tried it with MacOSX10.8.sdk and C++11 enabled but it fails with (I
> think that C++11 is not fully supported in 10.8):
Just to clarify: you need to distinguish between "(Minimum) BUILD S
> You can either use QMetaType for that or your own registration/factory.
Thiago,
Yes, that's exactly true. I just decided to use QMetaType, as Qt already
provides the registration/creation infrastructure, instead of pushing a
factory object to the library that will create the instances (or using m
Looks like you have to create and launch in Java that will take over
uploading your file in the background when Android feels like it.
Job Schedule API may be your best way out.
No more worrying about ApplicationSuspended, Job Api is independent of that.
Bad thing is that you have to write som
So there seems to be some conflicting information out there about how to do
this in Qt.
It seems that in 5.3, because the Qt thread as not the UI thread, everything
worked. then in 5.4, that stopped working? This was supposed to be fixed in
5.5? Anyhow, I'm working with 5.6 now. I have enough o
Hello,
what is the minimum required Mac OS X SDK?
I tried it with MacOSX10.8.sdk and C++11 enabled but it fails with (I
think that C++11 is not fully supported in 10.8):
In file included from
/opt/Qt/5.6/clang_64/lib/QtCore.framework/Headers/QString:1:
/opt/Qt/5.6/clang_64/lib/QtCore.framework/H
And yet another idea (untested), using C++11 lambdas :
QFile *f = new QFile(filename);
f->open(QIODevice::ReadOnly);
QNetworkReply* reply = nam.post(req, f);
connect(reply, &QNetworkReply::finished, f, [=f]() {
f->close();
f->remove();
delete f; // or f->d
2016-03-02 18:56 GMT+01:00 Jason H :
> Indeed it is, there's a couple ways to skin this cat.
Another idea, after looking at the API: You could perhaps transport
your QFile* pointer in a user attribute of the request, e.g. something
like (untested):
int CoolFileAttribute = QNetworkRequest::User;
On quarta-feira, 2 de março de 2016 17:45:15 PST Jason H wrote:
> Let me expand on this, I can f->setParent(reply), but I also need to delete
> the file from disk. If I rely on the parent/child object deletion, I can't
> get a change to delete the file.
If you're on Unix, you can delete the file w
On quarta-feira, 2 de março de 2016 15:37:41 PST Nuno Santos wrote:
> Hi,
>
> I’m using Qt 5.5.1 clang_64 prebuilt package and it doesn’t seem to have
> OpenSSL support built in as I’m receiving this output.
That output indicates that it *does* have OpenSSL support built-in. It
wouldn't be looki
On quarta-feira, 2 de março de 2016 13:04:35 PST Nye wrote:
> I just meant that in my case the classes are defined in the user
> application, so the library has no notion whatsoever what classes it has
> available to create instances from and it depends on the meta-type system
> exclusively for tha
> On 02 Mar 2016, at 16:49, Jason H wrote:
>
> Is there a static/singleton QNetworkAccessManager that I can get in a Qt app
> rather than creating my own?
http://doc.qt.io/qt-5/qqmlengine.html#networkAccessManager
--
J-P Nurmi
___
Interest mailing li
Let me expand on this, I can f->setParent(reply), but I also need to delete the
file from disk. If I rely on the parent/child object deletion, I can't get a
change to delete the file.
> QFile *f = new QFile(filename);
> f->open(QIODevice::ReadOnly)
> ...
> nam.post(req, f);
> ...
>
> // someti
QFile *f = new QFile(filename);
f->open(QIODevice::ReadOnly)
...
nam.post(req, f);
...
// sometime later in the finished slot:
finished(QNetworkReply *reply) {
// how to close and delete f ? (The QFile object)
}
Thanks
___
Interest mailing list
Int
I think I have missed something. If it has support enabled by default why can’t
he find openssl on my system? I’m on Mac OSX 10.11.2 and I there are this
crypto and ssl libs available:
/opt/local/lib/libcrypto.dylib
/usr/lib/libcrypto.dylib
/opt/local/lib/libssl.dylib
/usr/lib/libssl.dylib
Ar
On Wed, Mar 2, 2016 at 6:07 PM, Robert Iakobashvili wrote:
> On Wed, Mar 2, 2016 at 5:37 PM, Nuno Santos wrote:
>> I’m using Qt 5.5.1 clang_64 prebuilt package and it doesn’t seem to have
>> OpenSSL support built in as I’m receiving this output.
>>
>> From documentation I see that OpenSSL is enab
> -Original Message-
> From: Interest [mailto:interest-
> bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of
> Nuno Santos
> Sent: Wednesday, March 02, 2016 4:38 PM
> To: interest
> Subject: [Interest] Enabling OpenSSL on a shared build of Qt
>
> Hi,
>
> I’m using Qt 5.5.
On Wed, Mar 2, 2016 at 5:37 PM, Nuno Santos wrote:
> I’m using Qt 5.5.1 clang_64 prebuilt package and it doesn’t seem to have
> OpenSSL support built in as I’m receiving this output.
>
> From documentation I see that OpenSSL is enabled by default however it
> doesn’t seem to able to find it.
>
> I
Is there a static/singleton QNetworkAccessManager that I can get in a Qt app
rather than creating my own? I know there is a QNetworkAccessMangerFactory for
customizing the QNAM that QML gets, but that's not what I'm asking.
Platform is Android, but I'm interested "in general".
Hi,
I’m using Qt 5.5.1 clang_64 prebuilt package and it doesn’t seem to have
OpenSSL support built in as I’m receiving this output.
From documentation I see that OpenSSL is enabled by default however it doesn’t
seem to able to find it.
I’m even trying to additionally link ssl libraries to the
Ah you mean by "knowing types at compile time" is actually defined types,
so you actually defining classes at run-time?
2016-03-02 13:04 GMT+02:00 Nye :
> I just meant that in my case the classes are defined in the user
> application, so the library has no notion whatsoever what classes it has
>
I just meant that in my case the classes are defined in the user
application, so the library has no notion whatsoever what classes it has
available to create instances from and it depends on the meta-type system
exclusively for that (while still handling the
serialization/deserialization of said in
Op 02/03/2016 om 11:51 schreef Sina Dogru:
>For now there is a design choice which I feel weak myself, to do
factory or to use QMetaType for creating instances.
Depends on the use case I suppose. If you know the types at
compile time, as is usually the case I'd go with the sim
>
> > For now there is a design choice which I feel weak myself, to do
> factory or to use QMetaType for creating instances.
>
> Depends on the use case I suppose. If you know the types at compile time,
> as is usually the case I'd go with the simple solution to make a factory. I
> recently, howeve
> For now there is a design choice which I feel weak myself, to do factory
or to use QMetaType for creating instances.
Depends on the use case I suppose. If you know the types at compile time,
as is usually the case I'd go with the simple solution to make a factory. I
recently, however, had a case
2. Why are you write string values? It's not "Image.Stretch", it's an
enum value of QQuickImage.
3. Remove the .ui suffix, like "MainForm.qml".
4. QML id is not the same as objectName. If you use
QObject::findChild(), you should set objectName.
Also, creating two QQmlEngine's for different QML fil
34 matches
Mail list logo
