measurements done by e.g. Volker Krause on KF5 code.
>
> Fair enough, go ahead and change it.
>
+1 for not lying to Qt users. Our company has had to change a lot of our
critical-path code to use QVector in recent months, and we probably
would've started that way if not for the
> Note that we're talking about a standard violation in the first place. The
> standard says you can replace operator new, so if MSVC doesn't allow you to do
> it properly, then you can throw the standard out of the window. If an inline
> operator new (for MSVC only) solved the problem, it would be
On Mon, Mar 9, 2015 at 12:57 AM, Knoll Lars wrote:
> Yes, the best solution IMO is still to use your own malloc and operator
> new replacements. In addition, OOM handlers on the OS level can help.
Except that dynamically linked Windows Qt applications (read: most)
don't work this way, so Windows
Is it a design goal of QML/Quick to discourage C++ interaction? I ask
because every DevDays talk I attend includes some version of the
phrase "any reasonably complex QML application will have C++ doing its
back-end work", but yet I keep running into QML classes that hide
important Qt C++ classes /
> Could I safely assume that these are false positives? I am not overly
> concerned since the leaks are tiny and only on exit, but the object dump to
> stdout is a bit annoying.
>
Personally, I doubt that they are false positives. There are quite a few
leak-on-exit bugs in Qt5 nowadays, which I p
Are source packages somehow harder to make than packages for particular
platforms? Many of the people who would bother trying out a beta have
special needs like maintaining their own patches or static linking and it
is annoying to have to resort to git. Would it be possible to make source
packages
Any chance of getting source packages like last time?
On Tue, Jun 3, 2014 at 12:17 AM, Heikkinen Jani
wrote:
> Hi,
>
> New Qt 5.3.1 snapshot available here:
> http://download.qt-project.org/snapshots/qt/5.3/5.3.1/2014-06-03_98/
>
>
>
> Qt5 changes:
>
> https://codereview.qt-project.org/#change
Hello,
I saw on the Qt blog that some awesome Digia folk have make progress on a
Qt Quick treeview. I understand that the code isn't "production quality"
yet, but I'd love to offer help with any development/polish/testing work
that would be useful.
Right now I've hacked together a system where my
Hello,
While trying to style a ComboBox such that its text didn't elide and it
didn't have inexplicably large margins, I was surprised to learn that these
two items would be displayed entirely differently:
ComboBox { model: ["1", "2"] }
ComboBox { model: ["1", "2"]; style: ComboBoxStyle{} }
Whic
Hello,
I understand that Widgets are considered "complete" in Qt5, and no new
features are going to be added, but it's seeming more and more like the
actual position of developers is that Widgets are fully deprecated.
For at least five months Digia and others have known that one of the
fundamenta
I especially like the idea of creating an ignore list for valgrind if we
could use it for unit tests. Then at least people would have to be
conscious about the memory leaks they create and add them to the valgrind
ignore list if they are intentional.
___
Hello,
I think Thiago made a great point when he said, "Objects not properly
destroyed at shutdown could be an indication of something else wrong". The
thing that scares me most about the philosophy that we don't have to delete
reachable dynamically allocated objects is that those objects never ha
Hi everybody,
We had a small discussion on the #qt-labs IRC channel about memory leaks
earlier, and I'd like to get a feel from the community in general.
In QtQuick, QSGRenderLoop::instance() can create a QSGWindowsRenderLoop
using new that it never destroys. The memory is always pointed to by a
Excuse my ignorance, but does this include adding notes for known bugs in
Jira? For example, there's a bug where all widget moves generate double
move events, and the second event has incorrect coordinates. It's
documented here:
https://bugreports.qt-project.org/browse/QTBUG-32590
Would that be th
14 matches
Mail list logo
