I'm afraid this is your bug :)
QSGNode::DirtyForceUpdate is an internal undocumented property used for
internal reasons. The right thing to do is to the scene graph exactly what you
changed, which is also cheaper for the scene graph to handle.
QSGNode::DirtyGeometry in this case.
cheers,
Gunn
Hi, everyone, i'm recently working on a project which is qml&pyqt based, i
have to say that it's really much faster doing GUI things in qml, but now i
have one problem, every time i called the setSource(url) method of
QQuickview, i got plenty of my memory consumed and it never came back event
i des
It looks like using QSGNode::DirtyGeometry did the trick. I would have
expected QSGNode::DirtyForceUpdate to work though. Is this a bug?
On Wed, Dec 4, 2013, at 02:14 PM, achart...@fastmail.fm wrote:
> Hi,
>
> I had a QQuickItem-based 2D linegraph working fine in prior versions of
> Qt 5. This co
Hi,
I had a QQuickItem-based 2D linegraph working fine in prior versions of
Qt 5. This code does not seem to work with Qt 5.2 RC 1. Below is the
relevant code of my QQuickItem-based linegraph:
QSGNode* Linegraph::updatePaintNode(QSGNode* oldNode,
UpdatePaintNodeData* updatePaintNodeData)
{
Q_
Hi,
On Wednesday 04 December 2013 11:47:29 Sletta Gunnar wrote:
> If we added conversion functions for inch(), cm(), mm(), points() to
> QQuickItem, it could look up its current window/screen object and figure
> out the relationship between each unit for the screen the item is on and
> just set th
Because everything else, x, y, width, height, image dimensions, anchor margins,
etc is in pixels. The fact that we have Font.pointSize is in my opinion a flaw.
That being said, I wouldn't mind changing Font.pixelSize to Font.size if there
was an agreement on standardizing on pixels.
__
On Wed, Dec 4, 2013 at 12:37 PM, Mitch Curtis wrote:
> On 12/04/2013 11:47 AM, Sletta Gunnar wrote:
>> QWidget has the exact opposite problem. Layouts, styles and rendering
>> happens in pixel units while fonts are sized in point size. This is also a
>> problem when moving between platfoms as th
On 04 Dec 2013, at 11:47, Sletta Gunnar wrote:
> QWidget has the exact opposite problem. Layouts, styles and rendering happens
> in pixel units while fonts are sized in point size. This is also a problem
> when moving between platfoms as the pixelsize of a point has a different
> definition o
On 12/04/2013 11:47 AM, Sletta Gunnar wrote:
> QWidget has the exact opposite problem. Layouts, styles and rendering happens
> in pixel units while fonts are sized in point size. This is also a problem
> when moving between platfoms as the pixelsize of a point has a different
> definition on eac
Hi,
what is already possible is to read the font.pixelSize property for a
specific point size or just using the implicit size of a text item.
One main problems with layouts following physical units (pt, cm), is
that icons (all pixel based resources) have to be scaled accordingly (or
have a "ran
QWidget has the exact opposite problem. Layouts, styles and rendering happens
in pixel units while fonts are sized in point size. This is also a problem when
moving between platfoms as the pixelsize of a point has a different definition
on each platform. When running widgets on a hidpi screen, t
On Wednesday 04 December 2013 11:05:43 Tim Blechmann wrote:
> >> hi,
> >>
> >> in order to compile qt-5.2.0-rc1 as static library with c++11 on osx, i
> >> need to apply the attached patch.
> >> the issue had been reported in a comment in [1], but i guess the issue
> >> was missed, because the bug
Hi all,
Petri Järvenpää is nominated to Qt project sysadmin role.
He is the default assignee for all tickets at
https://bugreports.qt-project.org/browse/QTSYSADM
In case of Petri's vacations or other absences deputies are handling tickets.
Olli Hirvonen
Senior Manager, Qt Releases - Digia
Visi
>> hi,
>>
>> in order to compile qt-5.2.0-rc1 as static library with c++11 on osx, i
>> need to apply the attached patch.
>> the issue had been reported in a comment in [1], but i guess the issue
>> was missed, because the bug was closed before.
>>
>> iac, attached patch fixes the issue, would be g
Hi,
Only 5 days left before the submissions deadline for C++Now 2014!
C++Now is a general C++ conference for C++ experts and enthusiasts.
It is not specific to any library/framework or compiler vendor and
has three tracks with presentations ranging from hands-on, practical
tutorials to advanced C
On Wednesday 04 December 2013 09:55:55 Tim Blechmann wrote:
> hi,
>
> in order to compile qt-5.2.0-rc1 as static library with c++11 on osx, i
> need to apply the attached patch.
> the issue had been reported in a comment in [1], but i guess the issue
> was missed, because the bug was closed before
hi,
in order to compile qt-5.2.0-rc1 as static library with c++11 on osx, i
need to apply the attached patch.
the issue had been reported in a comment in [1], but i guess the issue
was missed, because the bug was closed before.
iac, attached patch fixes the issue, would be great if it can be incl
Hi all,
We have again new snapshot available for you verification & testing:
http://download.qt-project.org/snapshots/qt/5.2/5.2.0/2013-12-04_194/
Almost all installers are available, only combined iOS & Android installer for
mac is missing.
Mirroring is ongoing so it might be all installers ar
18 matches
Mail list logo
