On 11/29/2012 03:01 PM, Dominik Holland wrote:
> Hi all,
>
> last month i had some performance problems on a QML animation running on
> low end hardware (imx233).
> I debugged that problem and it was caused because of rounding errors
> during the comparison of two reals.
What kind of QML code lead
Hi,
can we please go back to the initial question of whether it is worth the
effort to use a more robust way of real comparison in qquickitem ?
Dominik
P.S.: I'm aware of it that how we compare the reals is also important,
but that's not the aim of that mail
On 11/30/2012 01:36 PM, Samuel Rød
On Sunday 02 December 2012 23:02:15 Thiago Macieira wrote:
> On segunda-feira, 3 de dezembro de 2012 07.53.07, Olivier Goffart wrote:
> > I was able to reproduce the error by making QMetaTypeIdQObject a template.
> > (On linux with both clang 3.1 and clang trunk)
> > Attached the problematic testas
On segunda-feira, 3 de dezembro de 2012 07.53.07, Olivier Goffart wrote:
> I was able to reproduce the error by making QMetaTypeIdQObject a template.
> (On linux with both clang 3.1 and clang trunk)
> Attached the problematic testase.
>
> I am not sure yet if this is a compiler bug or if we are in
On Monday 03 December 2012 00:41:38 Francisco Lopes da Silva wrote:
> I'm trying to build Qt5 on my environment but I'm stumbling at an error I'm
> having a hardtime dealing with.
> I use OS X Mountain Lion, but I don't use the default Xcode environment, I
> compile both clang and libc++
> from sou
On Dec 2, 2012, at 8:55 AM, Thiago Macieira
wrote:
> On domingo, 2 de dezembro de 2012 14.52.12, Knoll Lars wrote:
>>> Most of the pending changes in master today are fixes that need to go into
>>> the 5.0 release, so the branch should be merged to stable, not dev.
>>
>> I have been seeing lot
I'm trying to build Qt5 on my environment but I'm stumbling at an error I'm
having a hardtime dealing with.
I use OS X Mountain Lion, but I don't use the default Xcode environment, I
compile both clang and libc++
from sources.
clang --version
clang version 3.3 (trunk 168290)
Target: x86_64-apple-
On Sun, Dec 02, 2012 at 05:11:18PM +0100, Stephen Kelly wrote:
> On Sunday, December 02, 2012 14:09:15 you wrote:
> > Hi,
> >
> > Apologies for the top-quote, handicapped with web access right now
> > :(
>
> I don't understand the connection between web access and top-quoting,
> but fair enough :
On domingo, 2 de dezembro de 2012 14.52.12, Knoll Lars wrote:
> > Most of the pending changes in master today are fixes that need to go into
> > the 5.0 release, so the branch should be merged to stable, not dev.
>
> I have been seeing lots of pending changes in master that are 5.1 material
> and
On domingo, 2 de dezembro de 2012 14.09.15, Hausmann Simon wrote:
> (2) QWebElement and QWebSettings are indeed in include/QtWebKit and
> QWebView is in include/QtWebKitWidgets, i.e. the module split is present on
> the include level, too.
This, in turn, automatically means the error we found
On Sunday, December 02, 2012 14:09:15 you wrote:
> Hi,
>
> Apologies for the top-quote, handicapped with web access right now :(
I don't understand the connection between web access and top-quoting, but fair
enough :). I assume outlook makes it impossible to bottom quote somehow.
>
> Regarding
On 12/02/2012 04:04 PM, haithem rahmani wrote:
>
> Hi,
>
> I did :
> $> git submodule foreach "git checkout -b stable remotes/origin/stable"
>
can you try:
git submodule foreach "git checkout -b stable remotes/origin/stable ||:"
Cheers,
--
Sergio Ahumada
Release Engineer - Digia, Qt
___
Hi,
I did :
$> git submodule foreach "git checkout -b stable remotes/origin/stable"
and got the error:
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'remotes/origin/stable' which can not be
resolved as commit?
Stopping at 'qtqa'; script r
On Dec 1, 2012, at 11:20 AM, Thiago Macieira wrote:
> On quarta-feira, 28 de novembro de 2012 19.47.47, Knoll Lars wrote:
>> Transitional only. Will be closed for new pushes once the branches get
>> created. Patches that are already in gerrit can still be staged for around
>> a week to allow eve
Hi,
Apologies for the top-quote, handicapped with web access right now :(
Regarding your questions I'm positive:
(1) QtWebKit and QtWebKitWidgets are using all the features of the Qt5
build system for module creation, they behave like any other module.
(2) QWebElement and QWebSettings a
On Sunday, December 02, 2012 12:27:18 Hausmann Simon wrote:
> Hi,
>
> I can try to add some clarifications.
>
> It is our intention to make it so that when you write
>
> QT += webkitwidgets
>
Did you also consider how you might have to change how the cmake files are
generated?
Do you now
Hi,
I can try to add some clarifications.
In beta2 we did the most developer-visible change with reards to the WebKit
library split by simply renaming QtWebKit to QtWebKitWidgets, which affects
.pro files and #include statements that use the module syntax.
Now we implemented a split for real, wh
17 matches
Mail list logo
