On Wednesday, 20 March 2019 14:59:39 PDT René J.V. Bertin wrote:
> >Because it is a major rewrite of QtNetwork code interfacing with OpenSSL.
> >Such change cannot go to LTS branch [1]
>
> Now maybe (though I'd argue this is a bug fix; OSSL 1.0 will go EOL 5 months
> before Qt 5.9). But that was
Hi,
I try to get QGeoPositionInfoSource::createDefaultSource(this); working under
iOS 12.1.2 with Qt 5.11.x.
But the function returns always a null pointer.
Do i need to initialize the plugin first?
Maybe with Q_IMPORT_PLUGIN?
But if so, what do I need to enter?
Thanks in advance
Regards
I now have the same issue with trying to register a QTextEdit widget's
content:
|self.registerField('message', self.notes_widget.messageWidget,
'toPlainText', 'notes_widget.messageWidget.textChanged') |
Once again my sanity check with manual signal/slot connections works fine:
On Tuesday, 19 March 2019 16:46:49 PDT Jérôme Godbout wrote:
> I run qTest::exec() to run my test but I would like to known if it's
> possible to recover the number of failure/pass/skipped to do some work
> after the qTest::exec()
That information is logged, but is not exposed in the API.
--
Hi,
>From: Interest on behalf of Roman Wüger
>
>I try to get QGeoPositionInfoSource::createDefaultSource(this); working under
>iOS 12.1.2 with Qt 5.11.x.
>But the function returns always a null pointer.
In general this should work out of the box unless there is a bug...
How did you obtain
Hi,
I try to always show a done or similar button on top of the onscreen keyboard.
To do this I tried the following as an example for a Textfield:
inputMethodHints: Qt.ImhDigitsOnly
EnterKey.type: Qt.EnterKeyDone
but there is no done key shown.
Any hints?
Regards
Roman
On Wednesday 20 March 2019 10:45:18 you wrote:
> Hi,
>
> I am new to Qt.
> Yesterday, I have learned about:
> - QNetworkAccessManager
> - QNetworkRequest
> - QNetworkReply
> (as I wanted to figure out how to make HTTP GET/POST request and process the
> responses).
>
> Here:
>
>
Hi,
I just learned that Qt 5.9 apparently doesn't build against OpenSSL 1.1 . Does
anyone already have a fix for this?
If not I'll try to adapt Debian's OSSL 1.1 support patch for Qt4; that might
even be upstreamable supposing there will be further Qt 5.9 releases ?
Thanks,
R.
On Tue, Mar 19, 2019 at 7:54 PM Thiago Macieira
wrote:
> On Tuesday, 19 March 2019 09:40:42 PDT Calogero Mauceri wrote:
> > Hi all,
> >
> > I'm trying to build Qt 5.12.2 on Ubuntu 14.04.
> > I get the following error just after I launch the configure
> >
> > ERROR: Feature 'xcb' was enabled, but
Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
One QNetworkAccessManager (QNAM for short) will be enough in your case as well.
The signals on QNAM all pass a pointer to the QNetworkReply so you can know
which it relates to.
Although perhaps more fitting for your usecase may be to use the signals on
QNetworkReply instead of QNAM
>
> Hi,
>
> I try to always show a done or similar button on top of the onscreen
> keyboard.
>
> To do this I tried the following as an example for a Textfield:
>
> inputMethodHints: Qt.ImhDigitsOnly
> EnterKey.type: Qt.EnterKeyDone
>
> but there is no done key shown.
>
> Any hints?
>
I suppose
Hi,
Here are a few hints what you might want to check upon.
Do you use cmake or qmake? cmake does not work with static libs. You must use
qmake as it works out what dependencies have to be build into binary.
I suggest you go through your binaries and first verify that you have the
relevant
Hello Alex,
I use the prebuilt binaries from the online Installer.
Regards
Roman
> Am 20.03.2019 um 08:51 schrieb Alex Blasche :
>
> Hi,
>
>> From: Interest on behalf of Roman Wüger
>>
>
>> I try to get QGeoPositionInfoSource::createDefaultSource(this); working
>> under iOS 12.1.2 with
I understand LibreSSL has some advantages, is that worth checking out?
> On Mar 20, 2019, at 3:15 AM, René J.V. Bertin wrote:
>
> Hi,
>
> I just learned that Qt 5.9 apparently doesn't build against OpenSSL 1.1 .
> Does anyone already have a fix for this?
>
> If not I'll try to adapt Debian's
20.03.2019, 13:18, "René J.V. Bertin" :
> Hi,
>
> I just learned that Qt 5.9 apparently doesn't build against OpenSSL 1.1 .
> Does anyone already have a fix for this?
You should either use Qt >= 5.10 or build against OpenSSL 1.0.2
>
> If not I'll try to adapt Debian's OSSL 1.1 support patch
Hi,
Il 20/03/19 18:23, David M. Cotter ha scritto:
I understand LibreSSL has some advantages, is that worth checking out?
Qt does not work with LibreSSL.
Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France
Il 20/03/19 11:15, René J.V. Bertin ha scritto:
I just learned that Qt 5.9 apparently doesn't build against OpenSSL 1.1 . Does
anyone already have a fix for this?
Which distribution already stopped shipping OpenSSL 1.0?
Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior
On 2019-03-20 11:24, Calogero Mauceri wrote:
On Tue, Mar 19, 2019 at 7:54 PM Thiago Macieira
wrote:
On Tuesday, 19 March 2019 09:40:42 PDT Calogero Mauceri wrote:
> Hi all,
>
> I'm trying to build Qt 5.12.2 on Ubuntu 14.04.
> I get the following error just after I launch the configure
>
>
On Wednesday, 20 March 2019 13:01:18 CET Sérgio Martins via Interest wrote:
> On 2019-03-20 11:24, Calogero Mauceri wrote:
> > On Tue, Mar 19, 2019 at 7:54 PM Thiago Macieira
> >
> >
> > wrote:
> >> On Tuesday, 19 March 2019 09:40:42 PDT Calogero Mauceri wrote:
> >> > Hi all,
> >> >
> >> > I'm
>Because it is a major rewrite of QtNetwork code interfacing with OpenSSL. Such
>change
>cannot go to LTS branch [1]
Now maybe (though I'd argue this is a bug fix; OSSL 1.0 will go EOL 5 months
before Qt 5.9). But that was not the question.
5.9.0 was released on May 31st 2017
20.03.2019, 21:03, "René J.V. Bertin" :
>> You should either use Qt >= 5.10 or build against OpenSSL 1.0.2
>
> Wrong answer :P
>
> If Qt 5.9 is still in LTS it should get commit
> cfbe03a6e035ab3cce5f04962cddd06bd414dcea cherry picked from the dev branch
> before 1.0 reaches EOL later this
> Which distribution already stopped shipping OpenSSL 1.0?
See my other email: for now this is for MacPorts, but I'm guessing Qt may not
want to depend only on an OpenSSL variant that's EOL.
Moving to 5.10 may be relatively trivial on Linux but not on Mac, if you want
to
keep supporting OS
On Wednesday, 20 March 2019 06:29:19 PDT Kevin Funk wrote:
> Also, another hint for you and the other person(s) trying to build recent Qt
> on an old Ubuntu LTS: Note that Ubuntu 14.04 is reaching end-of-life in one
> month(!), and only the ESM version contains further security fixes.
>
> See:
>
On Wednesday, 20 March 2019 11:14:52 PDT René J. V. Bertin wrote:
> See my other email: for now this is for MacPorts, but I'm guessing Qt may
> not want to depend only on an OpenSSL variant that's EOL.
Except that it's not EOL. OpenSSL 1.0.2 is still officially supported until
2019-12-31. See
Il 20/03/19 19:29, Thiago Macieira ha scritto:
Qt 5.9's lifetime ends before OpenSSL 1.0's.
Actually, it doesn't: 5.9 support ends in May 2020, OpenSSL 1.0 in Dec 2019.
The reality is that if your software depends on multiple libraries, your
deadline is the whichever EOL for those libraries
On Wednesday, 20 March 2019 11:31:39 PDT Giuseppe D'Angelo via Interest wrote:
> > Qt 5.9's lifetime ends before OpenSSL 1.0's.
>
> Actually, it doesn't: 5.9 support ends in May 2020, OpenSSL 1.0 in Dec 2019.
You're off by one year. 5.9.0 was released May 29, 2017.
5.9's support ends in May
Il 20/03/19 19:41, Thiago Macieira ha scritto:
Actually, it doesn't: 5.9 support ends in May 2020, OpenSSL 1.0 in Dec 2019.
You're off by one year. 5.9.0 was released May 29, 2017.
5.9's support ends in May 2019 (probably a bit later because we are able to
make the 5.9.9 release).
Isn't the
On Wednesday, 20 March 2019 03:15:38 PDT René J.V. Bertin wrote:
> Hi,
>
> I just learned that Qt 5.9 apparently doesn't build against OpenSSL 1.1 .
> Does anyone already have a fix for this?
Forklift the support from 5.10. A couple of Linux distributions did that for a
while (notably,
20.03.2019, 21:17, "René J. V. Bertin" :
>> Which distribution already stopped shipping OpenSSL 1.0?
>
> See my other email: for now this is for MacPorts, but I'm guessing Qt may not
> want to depend only on an OpenSSL variant that's EOL.
>
> Moving to 5.10 may be relatively trivial on Linux
>You should either use Qt >= 5.10 or build against OpenSSL 1.0.2
Wrong answer :P
If Qt 5.9 is still in LTS it should get commit
cfbe03a6e035ab3cce5f04962cddd06bd414dcea cherry picked from the dev branch
before 1.0 reaches EOL later this year.
Is that commit sufficient? Getting it to apply to
Konstantin Tokarev wrote:
> It would be better to upgrade Qt in MacPorts
MacPorts provides the latest and also a whole range of older Qt versions (down
to Qt 5.5 I think). It has to, because Qt doesn't support a sufficient range of
OS versions for our purposes.
Hi Pierre,
I also have no done button if the keyboard is text only. So maybe this function
doesn‘t work at all on iOS?
Regards
Roman
Am 20.03.2019 um 10:57 schrieb Pierre-Yves Siret :
>> Hi,
>>
>> I try to always show a done or similar button on top of the onscreen
>> keyboard.
>>
>> To do
33 matches
Mail list logo
