Gunnar:
Thanks for the 5.6 doc link.
Could not find anything that talks about parallel loading. But if you
say it will provide parallel loading, what does the QML Image { } object
display while the image is loading?
I may want to return with a standard "Loading image..." image for those
imag
Hi Mark,
I think it is serial. In Qt 5.6 there will be a new QQuickAsyncImageProvider class, with it you can do parallel image loading/rendering.
Regards,
Gunnar Roth
Gesendet: Freitag, 18. September 2015 um 02:29 Uhr
Von: "mark diener"
An: "interest@qt-project.org"
Betreff: [Interest] Ima
For those of you developing for Qt 5.5 and iOS, you may want to hold off on
Xcode 7 for now.
Installing the released Xcode 7 on top of Xcode 6.4 + Qt 5.5 OS X-Android-iOS
Enterprise succeeded in building my app Android and OS X targets. So far, so
good.
However my iOS kits disappeared from Qt
Hello List:
When dealing with multi-threading, the docs say that QQuickImageProvider
will load
images in a separate low priority thread.
As it reads in the docs:
http://doc.qt.io/qt-5/qquickimageprovider.html#details
"When this is enabled, the image request to the provider is run in a low
prior
On Thursday 17 September 2015 14:59:57 Jason Kretzer wrote:
> INCLUDEPATH += "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include"
> LIBS += -L"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Lib"
> -ladvapi32 -luser32
>
> I then manually ran CLEAN, QMAKE, Rebuild.
Remove the full pat
I did a complete uninstall and reinstall (Virtual Machine so it is easy) and
started with a clean Win8.1. I first installed all windows updates. I then
installed VS2013 followed by SP5. Next, I installed the Qt 5.5.0 32bit for
VS2013.
I opened the project again -- with empty Release/debug bu
On Thursday 17 September 2015 21:14:15 Joachim Langenbach wrote:
> Yeah, you're right! Actually I knew this difference alrady and because of
> the asynchronous call I want to use the start() method, but it isn't
> working with the php executable, whereas the execute() method does. My
> guess is a
> On Thursday 17 September 2015 17:13:00 Edward Sutton wrote:
>> Has anyone tried it?
>
> I tried the final that got pushed to me yesterday. Absolutely no issues, not
> even a new warning.
Great news! Thanks for sharing.
I will give it a go.
-Ed
>
> --
> Thiago Macieira - thiago.macieira (AT)
On Thursday 17 September 2015 18:50:09 René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > The files do contain the -L setting but pkg-config should strip them out.
> >
> > $ grep Libs: /usr/lib64/pkgconfig/{dbus-1,glib-2.0}.pc
> > /usr/lib64/pkgconfig/dbus-1.pc:Libs: -L${libdir} -ldbus-1
> > /u
On Thursday 17 September 2015 17:13:00 Edward Sutton wrote:
> Has anyone tried it?
I tried the final that got pushed to me yesterday. Absolutely no issues, not
even a new warning.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Good evening Lorenz,
>
> ==> synchronous call
>
>
> "void QProcess::start(const QString & program, const QStringList &
> arguments, OpenMode mode = ReadWrite)
>
> Note: Processes are started asynchronously, which means the started()
> and error() signals may be delayed. Call waitForStarted() t
Thiago,
I tried to describe it the best I could:
https://bugreports.qt.io/browse/QTBUG-48335
Thanks,
Regards,
Nuno
On 17/09/2015 17:24, Thiago Macieira wrote:
> On Thursday 17 September 2015 13:42:41 Nuno Santos wrote:
>> Hi,
>>
>> I have seen this bug report. The funny thing is that it says
Not since the thread went dead in July. The link to purchase the Indie
license is still active, although the blog entry
(https://blog.qt.io/blog/2015/07/06/indie-mobile-available-until-aug-31st/)
continues to state that it was being terminated on 31 Aug. Whether or not
that actually took plac
Yes, me... and I had some troubles... look ate this post from me
https://forum.qt.io/topic/58926/xcode-7-and-qt-error
regards
*="El tamaño de tus logros
depende del tamaño de tus metas." *
*C++ and Qt Senior Developer*
*Lic. Computer Science*
*Bu
Has anyone tried it?
Looks like it was release yesterday Sept 16.
-Ed
This email and any files transmitted with it from The Charles Machine Works,
Inc. are confidential and intended solely for the use of the individual or
entity to which they are addressed. If you have received this email in e
Thiago Macieira wrote:
> The files do contain the -L setting but pkg-config should strip them out.
>
> $ grep Libs: /usr/lib64/pkgconfig/{dbus-1,glib-2.0}.pc
> /usr/lib64/pkgconfig/dbus-1.pc:Libs: -L${libdir} -ldbus-1
> /usr/lib64/pkgconfig/glib-2.0.pc:Libs: -L${libdir} -lglib-2.0
>
> $ pkg-con
On Sep 17, 2015, at 11:27 AM, Thiago Macieira
mailto:thiago.macie...@intel.com>> wrote:
*External Message - use caution*
On Thursday 17 September 2015 13:45:40 Edward Sutton wrote:
spend too much time adding qDebug() statements because Qt objects d_ptr
members are invisible to the debugger.
There's any news on this topic?
Em seg, 20 de jul de 2015 às 03:34, Bob Hood escreveu:
> On 7/19/2015 6:29 PM, Hamish Moffatt wrote:
> > On 18/07/15 09:05, Bob Hood wrote:
> >> On 7/17/2015 4:56 PM, Nicola De Filippo wrote:
> >>> yes, but i think if he wants update the app in the future he need
On Thursday 17 September 2015 13:45:40 Edward Sutton wrote:
> spend too much time adding qDebug() statements because Qt objects d_ptr
> members are invisible to the debugger.
You can disable the pretty printers by right-clicking the area and unchecking
the mark. You can also add an expression to
On Thursday 17 September 2015 15:38:04 Danny Smit wrote:
> Can someone advise whether this is the behavior as intended or whether
> this points to an issue in Qt?
>From the description of the symptom and from the fact that the non-glib
dispatcher behaves differently, it sounds like this behaviour
On Thursday 17 September 2015 13:42:41 Nuno Santos wrote:
> Hi,
>
> I have seen this bug report. The funny thing is that it says it is resolved
> on Qt 5.5.0
>
> I'm using Qt 5.5.0
>
> What am I missing?
Some detail.
Apparently the bug fix was not enough for your case. The fix assumed that
qt
On Thursday 17 September 2015 16:08:49 René J. V. Bertin wrote:
> QT_LIBS_DBUS = -L/usr/lib/x86_64-linux-gnu -ldbus-1
> QT_LIBS_GLIB = -L/usr/lib/x86_64-linux-gnu -lgthread-2.0 -pthread -lglib-2.0
> > pkg-config --libs glib-2.0
> >
> > If it does, please file a bug against your distribution's pk
> On Sep 17, 2015, at 11:07 AM, Michael Jackson wrote:
>
> *External Message - use caution*
>
>
> On Sep 17, 2015, at 11:50 AM, John Weeks wrote:
>
>> We use our own build of Qt 5.5, including a debug build. Debugging is often
>> painfully slow but mostly works. And with a debug build of Qt we
On Sep 17, 2015, at 11:50 AM, John Weeks wrote:
> We use our own build of Qt 5.5, including a debug build. Debugging is often
> painfully slow but mostly works. And with a debug build of Qt we can step
> into Qt code and (usually) inspect d pointers.
>
> Be sure that you have gone into the P
>"Use debug version of frameworks”
Thanks! I had not done that.
>Who else thinks that black Build button looks selected? But it's not- the Run
>button is active!
[cid:8297F21F-F701-40CB-90D6-BB77880DDBC4@ditchwitch.cmw.internal]
I agree the Black build button looks selected since all the othe
Thanks Michael. Thanks Daniel.
It sounds like Visual Studio is still the best development environment in 2015
and beyond.
I think I will get the VS 2013 Qt Plugin and start my Windows VM as my main
development machine. Qt Creator has been crashing unexpectedly lately anyway
when I am editing
Hi all,
I have some questions about Qt Installer Framework features:
1. Is it possible to add the top and the left banners (images) to the
wizard? If yes, then - how?
2. Is it possible to stylize of widgets via qss? (e.g. to change the
background color, a form of buttons and so on). If yes, then
I'm in the same boat with Michael about debugging in OSX.
As I don't use a Windows/Visual Studio for development I'm usually relying
in the silly console output solution when I need to see variables content.
gcc is known for bad integration with third party tools... but I was
expecting clang woul
On Sep 17, 2015, at 9:45 AM, Edward Sutton wrote:
> I spend too much time adding qDebug() statements because Qt objects d_ptr
> members are invisible to the debugger.
>
> I use Qt 5.5 Enterprise pre-built to debug OS X, Android, iOS, and on Windows
> ( MSVC 2013 ).
>
> Is the only solution t
Thiago Macieira wrote:
> Find out which variable(s) contains that in mkspecs/*.pri.
>
> My guess is you're going to find it on variable QT_LIBS_GLIB and the other
> glib-based libraries. If that is it, please check whether the following
> command also produces -L/usr/lib/x86_64-linux-gnu:
In qm
I spend too much time adding qDebug() statements because Qt objects d_ptr
members are invisible to the debugger.
I use Qt 5.5 Enterprise pre-built to debug OS X, Android, iOS, and on Windows (
MSVC 2013 ).
Is the only solution to build Qt from source for all 4 platforms ?
-Ed
This email an
I'm running into an issue where it seems that Qt timers are not timing
out anymore when the application has a lot of other events (say
continues stream of events) to process. For instance, when the
application receives lots of small pieces of data on (TCP) sockets,
resulting in a lot of events to b
Hi,
I have seen this bug report. The funny thing is that it says it is resolved on
Qt 5.5.0
I'm using Qt 5.5.0
What am I missing?
Regards,
--
Nuno Santos
No dia 17/09/2015, às 13:06, Tim Blechmann escreveu:
>> Im having a really awkward situation when trying to start QApplication
>> insid
> Im having a really awkward situation when trying to start QApplication
> inside a plugin. Everything works in debug mode. I have struggled a bit
> on debug mode to get rid of an ASSERTION warning:
> Q_ASSERT(allArguments.size() == origArgc);
> When I sucessfully managed to inject the very same
Hi,
Im having a really awkward situation when trying to start QApplication
inside a plugin. Everything works in debug mode. I have struggled a bit
on debug mode to get rid of an ASSERTION warning:
Q_ASSERT(allArguments.size() == origArgc);
When I sucessfully managed to inject the very same argc
35 matches
Mail list logo
