On Tue, Mar 25, 2014 at 2:49 AM, Alan Ezust wrote:
> If you're using Qt 5.2 or later, there is a new API you can use.
>
> Call isInterruptionRequested() in your loop,
>
> http://qt-project.org/doc/qt-5/qthread.html#isInterruptionRequested
>
> And call requestInterruption() from outside.
>
> http:
If you're using Qt 5.2 or later, there is a new API you can use.
Call isInterruptionRequested() in your loop,
http://qt-project.org/doc/qt-5/qthread.html#isInterruptionRequested
And call requestInterruption() from outside.
http://qt-project.org/doc/qt-5/qthread.html#requestInterruption
I gues
Hi,
I've been advised to ask this here because you guys are more familiar with
Qt3D, so here goes:
I'm having trouble rendering multiple pieces of geometry with QGLBuilder. I
have a RenderBox test class which has an origin, min and max vector, and a
toGeomData() function which returns its curr
> Report a bug.
Not necessary. After I found out what this problem was, it was easy to find
that this
bug was already reported quite a while ago:
https://bugreports.qt-project.org/browse/QTBUG-33450
Ok, perhaps not the exact wording, but same problem. A new comment and a vote
might be enough t
Em seg 24 mar 2014, às 09:49:07, Bob Hood escreveu:
> I actually use the "volatile" tag to tell the compiler that it cannot
> optimize (i.e., make compile-time assumptions about) the variable that it
> decorates. Does std::atomic have the same meaning for optimizations? I
> can't get a clear pictu
Em seg 24 mar 2014, às 18:31:14, Guido Seifert escreveu:
> Now the webkit scripts don't use flex, but win_flex. No problem, Digia was
> nice enough to bundle those tools into the .zip file. Unfortunately the
> zip's win_flex.exe was only in the search path when -prefix was
> %CD%\qtbase.
Report a
Problem found and solved. Very stupid. As I said: Usually I compile my Qt5 from
git. To do this I have
all necessary tools installed: Ruby, Python, Perl, flex, bison... whatever.
Now the webkit scripts don't use flex, but win_flex. No problem, Digia was nice
enough to bundle those tools
into t
On 3/24/2014 9:53 AM, Koehne Kai wrote:
>
>> -Original Message-
>> From: interest-bounces+kai.koehne=digia@qt-project.org
>> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf Of
>> Bob Hood
>> Sent: Monday, March 24, 2014 4:49 PM
>> To: Thiago Macieira; interest@qt
Am 24.03.2014 um 16:53 schrieb Koehne Kai :
>
>
>> -Original Message-
>> From: interest-bounces+kai.koehne=digia@qt-project.org
>> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf Of
>> Bob Hood
>> Sent: Monday, March 24, 2014 4:49 PM
>> To: Thiago Macieira; in
On 3/24/14, 2:50pm, alexander golks wrote:
>> Right now I can detect if a file changes, and it's ok. However, can I
>> track if a file *comes back*?
>>
>> For instance, if I rename a watched file "a.txt" and rename it to
>> "b.txt", I get the slot running. Can I detect if the "b.txt" gets
>> rename
> -Original Message-
> From: interest-bounces+kai.koehne=digia@qt-project.org
> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf Of
> Bob Hood
> Sent: Monday, March 24, 2014 4:49 PM
> To: Thiago Macieira; interest@qt-project.org
> Subject: Re: [Interest] QThread
On 3/24/2014 9:30 AM, Thiago Macieira wrote:
> Em seg 24 mar 2014, às 16:27:06, André Somers escreveu:
>> The point is, that usually you don't _need_ synchronization for this
>> purpose, and using synchronization does come at a cost. It is usually
>> not critical that the worker thread stops imme
Em seg 24 mar 2014, às 16:27:06, André Somers escreveu:
> The point is, that usually you don't _need_ synchronization for this
> purpose, and using synchronization does come at a cost. It is usually
> not critical that the worker thread stops immediately when signalled,
> just that it stops soon
Etienne Sandré-Chardonnal schreef op 24-3-2014 16:11:
volatile is not providing synchronization guarantees in the standard.
Even if it may work on most platforms with bool, this is not a good
practice.
std::atomic or QAtomicInt will do the job.
The point is, that usually you don't _need_ syn
Em seg 24 mar 2014, às 11:38:54, Graham Labdon escreveu:
> m_generatorThread = new GeneratorThread(this);
>
> Then I call moveToThread and make the connections-
> m_generatorThread->moveToThread(m_thread)
I'm pretty sure that moveToThread printed a warning and failed to move, since
your object
Em seg 24 mar 2014, às 16:01:08, Michael Sué escreveu:
> There once was a warning NOT to download the zipped export of the site but
> explicitly git clone the source by yourself.
Downloading the release .zip files is fine. Downloading .zip files from
gitorious.org by clicking on tag archives or r
> -Original Message-
> From: interest-bounces+kai.koehne=digia@qt-project.org
> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf Of
> Guido Seifert
> Sent: Monday, March 24, 2014 4:06 PM
> To: interest@qt-project.org
> Subject: Re: [Interest] qt-everywhere-opens
volatile is not providing synchronization guarantees in the standard. Even
if it may work on most platforms with bool, this is not a good practice.
std::atomic or QAtomicInt will do the job.
2014-03-24 13:40 GMT+01:00 André Somers :
> Protecting it with a mutex is usually not needed, and it doe
> Here's my theory: You've a .qmake.cache in one of the top level directories
> of your build folder. That is, qmake does have this wonderful feature that it
> walks up until your drive directory to search for .qmake.xxx files, and loads
> them if found ...
>
> You can check this by running '
There once was a warning NOT to download the zipped export of the site but
explicitly git clone the source by yourself.
- Michael.
> -Original Message-
> From: interest-bounces+sue=nf.mpg...@qt-project.org [mailto:interest-
> bounces+sue=nf.mpg...@qt-project.org] On Behalf Of Guido Seife
Sorry, from time to time it happens that I just press 'reply' when it actually
should go to the list.
Here the missing answer for all. Sorry
> I could run your setup (with mingw) just fine. Note that you pass -no-angle
> here, and the
> error comes from a ANGLE Makefile, so it looks that you're
Thanks all
-Original Message-
From: interest-bounces+graham.labdon=avalonsciences@qt-project.org
[mailto:interest-bounces+graham.labdon=avalonsciences@qt-project.org] On
Behalf Of André Somers
Sent: 24 March 2014 12:40
To: interest@qt-project.org
Subject: Re: [Interest] QThread
> -Original Message-
> From: interest-bounces+kai.koehne=digia@qt-project.org
> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf Of
> Guido Seifert
> Sent: Sunday, March 23, 2014 1:42 AM
> To: interest@qt-project.org
> Subject: [Interest] qt-everywhere-opensourc
Am Mon, 24 Mar 2014 12:47:36 +0100
schrieb Sensei :
> Right now I can detect if a file changes, and it's ok. However, can I
> track if a file *comes back*?
>
> For instance, if I rename a watched file "a.txt" and rename it to
> "b.txt", I get the slot running. Can I detect if the "b.txt" gets
Hello,
I would need to know if there is a way to enable or disable the rendering to
a VNC port at runtime, (so, not only from application arguments), with qt4e
and QWS server (version 4.8.5).
I need to understand if it's possible, because I don't want to spend CPU
time to render always the graphi
william.croc...@analog.com schreef op 24-3-2014 13:34:
> On 03/24/2014 08:10 AM, Graham Labdon wrote:
>> Thanks for that - my ui is now responsive
>> What is the correct way to stop my thread running?
>> I tried m_thread->exit() but it still continues
>>
> Have it periodically check a global, (mute
On 03/24/2014 08:10 AM, Graham Labdon wrote:
> Thanks for that - my ui is now responsive
> What is the correct way to stop my thread running?
> I tried m_thread->exit() but it still continues
>
Have it periodically check a global, (mutex-protected?)
variable and then terminate (by returning from t
Thanks for that - my ui is now responsive
What is the correct way to stop my thread running?
I tried m_thread->exit() but it still continues
Thanks again
-Original Message-
From: interest-bounces+graham.labdon=avalonsciences@qt-project.org
[mailto:interest-bounces+graham.labdon=avalo
Graham Labdon schreef op 24-3-2014 12:38:
> Hi
> I am experimenting with QThreads
> The basic idea is to have a thread performing some task and to have a button
> on the UI that can stop this operation
>
> So I have a class that will perform the operation called GeneratorThread that
> has a start
2014-03-24 12:38 GMT+01:00 Graham Labdon :
> Hi
> I am experimenting with QThreads
> The basic idea is to have a thread performing some task and to have a button
> on the UI that can stop this operation
>
> So I have a class that will perform the operation called GeneratorThread that
> has a star
> ...and I get Qt installed in "C:\Qt\5.2.1".
>
> Maybe Digia tweaked something in the commercial version?
>
> I do not have the problem on another WINDOWS XP 32-bit machine, neither.
>
> - Michael.
Or it is a MinGW or MinGW 64 bit problem. I have it reproducible with all
options
I tried, ye
Dear all,
I'm using QFileSystemWatcher to watch a list of files, checking for the
existence of files.
Right now I can detect if a file changes, and it's ok. However, can I
track if a file *comes back*?
For instance, if I rename a watched file "a.txt" and rename it to
"b.txt", I get the slot r
Hi,
I do not have this problem. I call the following configure command (WINDOWS 7
64-bit with VS 2012) in "C:\Qt\qt-everywhere-enterprise-src-5.2.1":
configure.bat -prefix C:\Qt\5.2.1 -no-openssl -commercial -I c:\qt\icu\include
-L c:\qt\icu\lib64 -icu -opengl desktop -platform win32-msvc2012 -
Hi
I am experimenting with QThreads
The basic idea is to have a thread performing some task and to have a button on
the UI that can stop this operation
So I have a class that will perform the operation called GeneratorThread that
has a start slot
In the main ui class I create an instance of the
To minimize latency, your best bet would be to:
1. disable vsync, either using QSurfaceFormat::setSwapInterval(0) (since 5.3)
or in the system's control panel.
2. Run your application with QSG_RENDER_LOOP=basic to turn off the
threaded/window render loops. The windows/threaded render loops will
Yes, the "laggy" behavior is perfectly reasonable on some configurations, given
that the movements of the mouse cursor, the mouse event input rate, etc. are
all up to the system and Qt has no synchronization between that and the
display. When vsync is enabled, which is true by default for pretty
Hi Damian,
On Monday 24 March 2014 07:42:43 Damian Ivanov wrote:
> Hmm 2 options Jason:
> a) You are not affected by the bug but are uneducated about QML (it
> should run on embedded systems and slow systems too)
> b) You have some sickness about hand-eye coordination.
No need to be rude. There a
37 matches
Mail list logo
