Hello,
Try this:
http://galfar.vevb.net/wp/2014/problems-with-cdb-debugger-in-qtcreator/
On 9/3/2016 1:33 PM, qt next wrote:
Hi,
I have a very big issue. I need to start my application in debug in Qt
creator and be able to set breakpoint and it's very slow : a few
minutes to start the appl
Il 04/09/2016 12:57, Nils Jeisecke ha
scritto:
Hi!
I don't think this is a general problem.
I've seen this behaviour when for example using a repeater on a filter
model. If initially no filter is set, the repeater will happily
instantiate delegates for every model
On Mon, Sep 5, 2016 at 1:30 AM, william.croc...@analog.com <
william.croc...@analog.com> wrote:
>
> Is Qt5 using new X11 protocols (beyond those
> used by Qt4) which NX is not expecting?
>
Hello Bill,
I'm sorry, I honestly don't know. I'm not aware of anything really new in
the XCB integration, bu
On 5 September 2016 at 02:13, Roland Hughes wrote:
> I just ran a simple QML project test on the Raspberry Pi:
> http://www.logikalsolutions.com/wordpress/information-technology/raspberry-qt-part-12-qml-blows-big-stinky-chunks/
> Yimminy is it a resource pig.
Would you be willing to re-run your t
On 09/04/2016 05:48 PM, Konstantin Shegunov wrote:
Hi,
Do you forward the X? Sometimes this might do it ... for some reason ...
Hello:
I am running on a virtual machine
through an NX windowing system.
Sorry, I just noticed that I do not get the errors
when I run through a VNC based windowing
Hi,
Do you forward the X? Sometimes this might do it ... for some reason ...
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Hello:
I am trying to port two of my apps from Qt 4.8.6 to Qt 5.7.0
(I am also moving from RHEL5 to RHEL6 at the same time.)
I can build them and one appears to run properly, I just get a
little noise on start-up...
App #1:
XXX-lx01:app: App: *W*, failed to get the current screen resources
(/n
Qt 5.6 is for those who cannot upgrade. If you can upgrade, upgrade.
How (un)likely is it that one can remain locked into 5.6 because of
dependent code that doesn't build against 5.7+? Qt's backward
compatibility principle should prevent that, no?
It is extremely likely for development to rem
> -Original Message-
> From: Interest [mailto:interest-bounces+tuukka.turunen=qt.io@qt-
> project.org] On Behalf Of Roland Hughes
> Sent: sunnuntaina 4. syyskuuta 2016 21.14
> To: 2202873.hgKzyLeXCm@patux.local; Interests Qt project.org>
> Subject: Re: [Interest] Qt 5.6LTS vs 5.7+
>
>
Qt 5.6 is for those who cannot upgrade. If you can upgrade, upgrade.
How (un)likely is it that one can remain locked into 5.6 because of dependent
code that doesn't build against 5.7+? Qt's backward compatibility principle
should prevent that, no?
It is extremely likely for development to
Em domingo, 4 de setembro de 2016, às 13:01:00 CEST, René J. V. Bertin
escreveu:
> Thiago Macieira wrote:
> > Qt 5.6 is for those who cannot upgrade. If you can upgrade, upgrade.
>
> How (un)likely is it that one can remain locked into 5.6 because of
> dependent code that doesn't build against 5.
Hi,
I am trying to run programs containing QtQuick in an Android virtual
device (AVD), so I do not need an army of physical devices for doing
testing. However, running any QtQuick program on any AVD (Windows 10
host, Qt-5.7, Android x86) I tried gives me a white or a black screen
and lots of
Understood! For some reason I've been unable to install El Capitan, even
with a clean install. I was able to install Sierra beta and the problems
still exist. (I know, beta software could introduce its own issues, but
my app appears to run okay otherwise.)
One thing I did notice in the Apple C
Thiago Macieira wrote:
> Qt 5.6 is for those who cannot upgrade. If you can upgrade, upgrade.
How (un)likely is it that one can remain locked into 5.6 because of dependent
code that doesn't build against 5.7+? Qt's backward compatibility principle
should prevent that, no?
R.
_
Hi!
I don't think this is a general problem.
I've seen this behaviour when for example using a repeater on a filter
model. If initially no filter is set, the repeater will happily
instantiate delegates for every model item. Those will then be
destroyed as soon as the filter becomes active, which
Em domingo, 4 de setembro de 2016, às 09:51:19 CEST, René J. V. Bertin
escreveu:
> It's been suggested that the LTS version might be provided as a "calm"
> option while 5.7+ see significant Wayland development. In itself that
> sounds like a plausible idea, but maybe not so much for Wayland suppor
Thanks, adding -skip qtwebengine to the configure command-line did the
trick. But this also means that Qt default configuration (I initially
didn't explicitely enable/disable modules) doesn't build successfully.
Émeric
2016-09-02 22:11 GMT+02:00 Thiago Macieira :
> Em sexta-feira, 2 de setem
Thiago Macieira wrote:
> Em sábado, 3 de setembro de 2016, às 19:00:03 CEST, René J.V. Bertin escreveu:
>> Hi,
>>
>> A bit of an existential question: to what extent should distributions and
>> distribution systems (which can target multiple OS/versions) be prepared to
>> provide 5.6 and 5.7+ alo
18 matches
Mail list logo
