I just discovered a pretty simple and convenient technique that allows my
compiled-and-linked Qt .pro app to easily resolve to one-and-only-one main QML
file, whether I build my app from the command line in my app dir and run it
from there, or whether I have Qt Creator build my app in the defaul
specifically this video:
http://www.youtube.com/watch?feature=player_embedded&v=u94vwMXJJrs
On Sat, Dec 22, 2012 at 12:28 AM, Mark wrote:
> On Sat, Dec 22, 2012 at 12:26 AM, Mark wrote:
>> Hi,
>>
>> A while ago there was a (tech) demonstration video with QML2/Qt5 and
>> some very nice effects. I
On Sat, Dec 22, 2012 at 12:26 AM, Mark wrote:
> Hi,
>
> A while ago there was a (tech) demonstration video with QML2/Qt5 and
> some very nice effects. I think it was posted for the beta 1 or 2 on
> the Qt site. I don't mean the Qt5 video player demo. But i can't find
> it anywhere anymore.. It mus
Hi,
A while ago there was a (tech) demonstration video with QML2/Qt5 and
some very nice effects. I think it was posted for the beta 1 or 2 on
the Qt site. I don't mean the Qt5 video player demo. But i can't find
it anywhere anymore.. It must be somewhere on youtube ~_~
Does anyone happen to know
On 12/21/12 12:51 PM, Raul Metsma wrote:
> Seems like 10.6 does not have libc++.
> maybe have 2 prebuilt binaries, one with libc++ and libstdc++
>
> Raul
No, it doesn't. But it's easy enough to build one targeting 10.6 and
bundle it in the application. That's what we do.
> On Dec 21, 2012, at 6:
Seems like 10.6 does not have libc++.
maybe have 2 prebuilt binaries, one with libc++ and libstdc++
Raul
On Dec 21, 2012, at 6:56 PM, Stephen Chu wrote:
> On 12/21/12 3:17 AM, Sorvig Morten wrote:
>>
>>> Does the pre built binary use libstdc++ or libc++?
>>
>>
>> According to "otool -L", QtC
On 12/21/12 3:17 AM, Sorvig Morten wrote:
>
>> Does the pre built binary use libstdc++ or libc++?
>
>
> According to "otool -L", QtCore from the 5.0.0 binary links against libstdc++.
Doesn't that pretty much precludes us from using most C++11 features?
Using C++11 features like initializers list
On 21-Dec-12 17:22, Thiago Macieira wrote:
> On sexta-feira, 21 de dezembro de 2012 17.14.00, Attila Csipa wrote:
>> 2. QtOpenGL reports no non-ES versions, only OpenGL ES 2 as supported,
>> which is odd (being run on a desktop computer).
>
> How did you configure Qt? It's possible you're linking t
On Friday 21 December 2012 08:22:09 Thiago Macieira wrote:
> On sexta-feira, 21 de dezembro de 2012 17.14.00, Attila Csipa wrote:
> > 2. QtOpenGL reports no non-ES versions, only OpenGL ES 2 as supported,
> > which is odd (being run on a desktop computer).
>
> How did you configure Qt? It's possib
On sexta-feira, 21 de dezembro de 2012 17.14.00, Attila Csipa wrote:
> 2. QtOpenGL reports no non-ES versions, only OpenGL ES 2 as supported,
> which is odd (being run on a desktop computer).
How did you configure Qt? It's possible you're linking to ANGLE as your GL
libraries. That would make it
Hi,
I've ported QtInfo (
https://projects.developer.nokia.com/qtinfo ) to Qt5,
and here are a few notes. Overall the porting went fairly easy (had just
two methods to work around, QString::toAscii and
QLibraryInfo::buildKey), the rest was either packaging/qmake magic, or
MSVC peculiarities (a
On sexta-feira, 21 de dezembro de 2012 10.16.30, Sergio Ahumada wrote:
> I don't see this as a P0/P1 for 5.0.1 .. so I wonder how do we avoid the
> bags in the future.
That's why it's a brown paper bag: it was found only after the release.
I asked the reporter to create a bug entry, but it looks
On sexta-feira, 21 de dezembro de 2012 08.48.18, Mark wrote:
> > Because there are a few outstanding bugs with the new font database code.
>
> Ai, that sounds painful. That didn't qualify as a release delay?
No. They did not qualify as showstoppers.
We can see the text, we can read it. It's not
Hello !
On Thu, Dec 20, 2012 at 12:40 AM, Mehmet İpek wrote:
> In native c code you read unsigned long (4 byte in 32 bit platforms) and in
> Qt code you read quint64 (64 bit in all platforms).
Problem was here, thanks a lot.
--
Best regards,
Sincerely yours,
Yuriy Rusinov.
On Fri, Dec 21, 2012 at 2:42 AM, Thiago Macieira
wrote:
> On sexta-feira, 21 de dezembro de 2012 01.46.13, andy fillebrown wrote:
>> >> One of the reasons I use -dont-process is so I can add CONFIG+=silent
>> >> and -after CONFIG+=warn_off to the call to qmake. Is there another
>> >> way of reduc
Le 21/12/2012 10:46, Koehne Kai a écrit :
>> -Original Message-
>> From: interest-bounces+kai.koehne=digia@qt-project.org
>> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf
>> Of Yves Bailly
>> Sent: Friday, December 21, 2012 10:35 AM
>> Cc: interest@qt-project.o
>
> Another side note: at the end, "configure" says to "nmake confclean" to
> re-configure. However
> "nmake confclean" doesn't work, whereas "nmake distclean" seems to work.
>
https://bugreports.qt-project.org/browse/QTBUG-26414
but maybe it deserves a higher priority.
--
Sergio Ahumada
s...@
> -Original Message-
> From: interest-bounces+kai.koehne=digia@qt-project.org
> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf
> Of Yves Bailly
> Sent: Friday, December 21, 2012 10:35 AM
> Cc: interest@qt-project.org
> Subject: Re: [Interest] Trouble with "relea
On Fri, Dec 21, 2012 at 9:54 AM, Bache-Wiig Jens
wrote:
>> Hi Jens,
>>
>> I find the Qt decision in this area a bit strange - to put it mildly.
>> Text should imho look good at it's defaults (that's called strong
>> defaults). Zooming is a nice feature in QML, but remember, the
>> majority of apps
Hello again,
Le 21/12/2012 09:44, Yves Bailly a écrit :
> Le 21/12/2012 09:10, Koehne Kai a écrit :
I'm building Qt5 for 64bits using Visual 2010 on a Windows 7 64bits host,
>>> debug and release.
However it seems anything using Qt5Gui.dll fails to start.
>>> Now things get weird... I bu
>
>> who's wondering what the brown paper bag #1 is anyway ;)
>
> Mac source builds of frameworks in release mode (not debug-and-release) don't
> install any headers:
>
> #mac frameworks
> mac:!static:contains(QT_CONFIG, qt_framework) {
> #QMAKE_FRAMEWORK_VERSION = 4.0
> CONFIG += lib_bundl
> Hi Jens,
>
> I find the Qt decision in this area a bit strange - to put it mildly.
> Text should imho look good at it's defaults (that's called strong
> defaults). Zooming is a nice feature in QML, but remember, the
> majority of apps are probably not even going to have zooming support
> so perh
Le 21/12/2012 09:10, Koehne Kai a écrit :
>>> I'm building Qt5 for 64bits using Visual 2010 on a Windows 7 64bits host,
>> debug and release.
>>> However it seems anything using Qt5Gui.dll fails to start.
>> Now things get weird... I build a 32bits version of Qt5, Visual 2010 Pro SP1,
>> on a Windo
On Fri, Dec 21, 2012 at 2:42 AM, Thiago Macieira
wrote:
> On sexta-feira, 21 de dezembro de 2012 01.46.13, andy fillebrown wrote:
>> >> One of the reasons I use -dont-process is so I can add CONFIG+=silent
>> >> and -after CONFIG+=warn_off to the call to qmake. Is there another
>> >> way of reduc
>Does the pre built binary use libstdc++ or libc++?
According to "otool -L", QtCore from the 5.0.0 binary links against libstdc++.
Morten
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On Fri, Dec 21, 2012 at 9:02 AM, Bache-Wiig Jens
wrote:
> It looks like he distance field rendering can be tweaked on windows to be a
> bit sharper and thinner, but it is expected that the font rendering looks a
> bit more fuzzy than before on windows since distance field rendering is not
> pix
From: Adam Light [acli...@gmail.com]
>I think you left one major one (for us at least) out of your list: the
>elimination of the QMacPasteboardMime class (the equivalent QWindowsMime class
>on Windows is also gone).
Yes, thanks for mentioning it. That class and also others such as
QMacCocoaVie
> -Original Message-
> From: interest-bounces+kai.koehne=digia@qt-project.org
> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf
> Of Yves Bailly
> Sent: Friday, December 21, 2012 8:17 AM
> To: interest@qt-project.org
> Subject: Re: [Interest] Trouble with "releas
It looks like he distance field rendering can be tweaked on windows to be a bit
sharper and thinner, but it is expected that the font rendering looks a bit
more fuzzy than before on windows since distance field rendering is not pixel
grid aligned by like the windows native fonts are.
If you wan
29 matches
Mail list logo
