On quinta-feira, 5 de maio de 2016 22:21:08 PDT Filippo Cucchetto wrote:
> void invokeDeleteLater(QObject* other) {
> other->deleteLater();
> emit aboutToBeDeleted(other)
> }
You want the emit before the deleteLater(), if the object can be in another
thread.
--
Thiago Macieira - thiago.
On quinta-feira, 5 de maio de 2016 19:09:59 PDT Sean Donnelly wrote:
> In our application we maintain a UI Inventory via a named object cache.
> When an object is destroyed we remove it from our cache and when the name
> is changed we also update our cache.
>
> However when an object is scheduled
It depends on your use case but maybe you can simply create a QObject that
has the responsability of deleting your QObjects and emit a signal just
after calling deleteLater.
class MyDeleter : public QObject
{
...
signals:
void aboutToBeDelete(QObject*);
...
void invokeDeleteLater(QObject* oth
Looking at the implementation of deleteLater:
{
QCoreApplication::postEvent(this, new QDeferredDeleteEvent());
}
It seems to me you can achieve what you want without modifying the
implementation of deleteLater(), and instead making an event filter on
QCoreApplication for QDeferredDeleteEvent.
In our application we maintain a UI Inventory via a named object cache. When
an object is destroyed we remove it from our cache and when the name is changed
we also update our cache.
However when an object is scheduled for deletion via QObject::deleteLater() the
object remains in our cache unt
On quinta-feira, 5 de maio de 2016 13:39:59 PDT Tim Blechmann wrote:
> compiling the qt-5.7-beta tarball with msvc2013/64bit/static libraries,
> out-of-tree build gives me:
>
> ---
[cut]
> h:\qt3rd\qtgamepad\src\gamepad\qgamepadmanager.h(42) : fatal error
> C1083: Cannot open include file: 'QtGame
Consider the example below (requires Qt 5.7):
import QtQuick 2.6
import QtQuick.Layouts 1.1
import QtQuick.Window 2.2
import QtQuick.Controls 2.0
ApplicationWindow {
width: 400
height: 200
visible: true
onActiveFocusItemChanged: print("
> -Original Message-
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Sean Harmer
> Sent: torstaina 5. toukokuuta 2016 15.19
> To: development@qt-project.org
> Subject: Re: [Development] Qt CI reliability
>
> On Thursday 05 May 2016 13:
On Thursday 05 May 2016 13:01:24 Sean Harmer wrote:
> And more problems today:
>
> http://testresults.qt.io/logs/qt/qt3d/83275e6eb72baa5f80d4fbaaf84bc0ffd1b597
> 62/LinuxUbuntu_15_04x86_64LinuxUbuntuTouch_15_04armv7GCCDisableTests_OpenGLE
> S2/f09f2056189e7df3613966a77c6b671ff3d5ea88/buildlog.txt.
And more problems today:
http://testresults.qt.io/logs/qt/qt3d/83275e6eb72baa5f80d4fbaaf84bc0ffd1b59762/LinuxUbuntu_15_04x86_64LinuxUbuntuTouch_15_04armv7GCCDisableTests_OpenGLES2/f09f2056189e7df3613966a77c6b671ff3d5ea88/buildlog.txt.gz
results in a 404. I hope this doesn't last all of the holida
compiling the qt-5.7-beta tarball with msvc2013/64bit/static libraries,
out-of-tree build gives me:
---
cl -c -FIQtGamepadDepends -YuQtGamepadDepends
-Fp.pch\debug\Qt5Gamepadd_pch.pch -nologo -Zc:wchar_t -FS -Zi -MDd
-D_HAS_EXCEPTIONS=0 -GR -W3 -w34100 -w34189 -w44996
/Fd..\..\lib\Qt5Gamepadd.pdb
On Wed, May 04, 2016 at 07:46:41AM +, Mark De Wit wrote:
> Having tried to do this myself last week, I cannot find any "official"
> documentation
> on how to build Qt myself for an official release with our software. Doing
> our own
> build has proven frustrating enough that we abandoned the
On Tuesday 03 May 2016 17:36:49 Jędrzej Nowacki wrote:
> On Tuesday 03 of May 2016 14:54:50 Sean Harmer wrote:
> > Do you mean VM template? If so then yes that's again something that should
> > ideally be verified before deployment.
>
> Eh, wrong phrasing. Templates are tested. The problem is tha
13 matches
Mail list logo
