On Wednesday, 24 April 2019 14:11:09 PDT Tom Isaacson wrote:
> I've got some legacy code where a timer is firing on the wrong thread. The
> sequence is: 1. Thread instantiates MyClass.
> 2. MyClass constructor calls QTimer::singleShot(60 * 1000, this,
> &MyClass::OnTimer); 3. Move class to thread b
You can put the timer child of the object, so moveToThread() should move the
children too:
https://doc.qt.io/Qt-5/qobject.html#moveToThread
-Original Message-
From: Interest On Behalf Of Tom Isaacson
Sent: April 24, 2019 5:11 PM
To: Interest@qt-project.org
Subject: [Interest] Set a timer
I've got some legacy code where a timer is firing on the wrong thread. The
sequence is:
1. Thread instantiates MyClass.
2. MyClass constructor calls QTimer::singleShot(60 * 1000, this,
&MyClass::OnTimer);
3. Move class to thread by calling MyClass.moveToThread();
4. OnTimer is called on the wrong
You could copy your file and replace the console.log() with a regex and then
use this file version. You will need to add a target to your .pro. Here a quick
example of something I do for my i18n target:
i18nTarget.target = $${AMOTUS_ROOT}/i18n
i18nTarget.depends = FORCE
i18nTarget.commands = QMA
>> That's possible to do with qmake already, but you'll have to build
resource files manually via custom targets
Great! Where can I read about this? Is there any examples?
>> You can wrap this whole expression into function and replace that
>> function with empty one:
>> function printPasswordTo
ср, 24 апр. 2019 г. в 22:08, Konstantin Tokarev :
>
>
>
> 24.04.2019, 22:01, "Alexander Ivash" :
> > What I really need is some 'plugin' to qmake which would allow to
> > modify qml files on the fly before placing it into resources (but not
> > touching them on filesystem!). In ideal world, yeah.
>
24.04.2019, 22:01, "Alexander Ivash" :
> What I really need is some 'plugin' to qmake which would allow to
> modify qml files on the fly before placing it into resources (but not
> touching them on filesystem!). In ideal world, yeah.
That's possible to do with qmake already, but you'll have to b
What I really need is some 'plugin' to qmake which would allow to
modify qml files on the fly before placing it into resources (but not
touching them on filesystem!). In ideal world, yeah.
ср, 24 апр. 2019 г. в 21:51, Alexander Ivash :
>
> 2Jerome:
>
> The issue is that even if that function will
2Jerome:
The issue is that even if that function will be doing nothing, logging
data (which might be sensitive) can be captured via hooks / dump
analysis etc. I really need to pre-processes to eliminate not only
function call but also function parameters completely. Think about
this scenario:
con
Maybe you can overload the functor directly into the code and import the file
only if in debug mode (optional module):
http://udidu.blogspot.com/2012/12/override-console-functions.html
That could also be helpful to split the log into multiple receiver.
Not sure if this would work, but maybe you
I assume you don't use LoggingCategory.
Why?
śr., 24 kwi 2019, 18:56 użytkownik Alexander Ivash
napisał:
> I understand that this topic was raised a lot of times and that this
> is not QML-way. But, what options do I have in case of requirements to
> eliminate all the logging for release builds?
I understand that this topic was raised a lot of times and that this
is not QML-way. But, what options do I have in case of requirements to
eliminate all the logging for release builds?
Is there any hidden magic in qmake, like 'QMAKE_SUBSTITUTES' but more
flexible to substitute all the 'console.de
I'm interested in using occlusion query for an image processing task to
count pixels. Does Qt3D support occlusion query, if not, is there a way
call OpenGL commands directly to run the query?
Thanks,
Phi|ip
___
Interest mailing list
Interest@qt-project.o
13 matches
Mail list logo
