Sorry... It's not a bug... It's my mistake...
-Original Message-
From: igor.mironc...@gmail.com
Sent: Monday, June 09, 2014 1:37 AM
To: Thiago Macieira ; interest@qt-project.org
Subject: Re: [Interest] How to start object in the thread?
Actually Thiago it's my event. It's looks like a bu
List:
I am upgrading a project from Qt 4.7.1 to Qt 4.8.6
When I build this project on Windows, I now see this:
c:\qt\4.8.6\include\qtcore\../../src/corelib/global/qconfig.h(46) :
warning C4005: 'QT_LARGEFILE_SUPPORT' : macro redefinition
command-line arguments : see previo
Actually Thiago it's my event. It's looks like a bug.
When I changed
static const int changeColorEventType = QEvent::registerEventType();
to
static const int changeColorEventType = 2000;
all works fine.
P.S. In my test app I have only one custom event...
-Original Message-
From: Thi
Em seg 09 jun 2014, às 00:10:33, igor.mironc...@gmail.com escreveu:
> Thanks guys for your replies.
>
> I've found the problem. The problem was in Object's event() method...
>
> But now I have another problem.
>
> In my test app I have custom event that I post with
> QCoreApplication::postEvent(
Thanks guys for your replies.
I've found the problem. The problem was in Object's event() method...
But now I have another problem.
In my test app I have custom event that I post with
QCoreApplication::postEvent().
All seems ok, events posted and received but with another type that I
expect.
Em dom 08 jun 2014, às 12:42:39, igor.mironc...@gmail.com escreveu:
> I’ve added Launcher that works on the main thread. His job is just emit
> start() signal. My Object on the different thread connects to this start()
> signal.
>
> Now Launcher emits start() signal. All is ok. But Object doesn’t
Hello Igor!
On Sun, Jun 8, 2014 at 6:42 AM, wrote:
> I’ve added Launcher that works on the main thread. His job is just emit
> start() signal.
> My Object on the different thread connects to this start() signal.
>
> Now Launcher emits start() signal. All is ok. But Object doesn’t receive
> it...
Em dom 08 jun 2014, às 13:38:10, Nikos Chantziaras escreveu:
> > Like I said, server bug.
>
> Thanks, Thiago. It seems Mozilla/5.0 is the only user-agent this happens
> with. Could it be that there's some reason to reject connections with
> that user-agent?
No. Most likely, the server is trying
On Sun, Jun 8, 2014 at 4:08 PM, Nikos Chantziaras wrote:
> On 08/06/14 07:48, Thiago Macieira wrote:
>> Em dom 08 jun 2014, às 06:05:20, Nikos Chantziaras escreveu:
>>> It fails even without the redirection. I only used "sf.net" instead of
>>> "sourceforge.net" in order to make the code smaller fo
On 08/06/14 07:48, Thiago Macieira wrote:
> Em dom 08 jun 2014, às 06:05:20, Nikos Chantziaras escreveu:
>> It fails even without the redirection. I only used "sf.net" instead of
>> "sourceforge.net" in order to make the code smaller for posting here. So
>> this will also fail:
>>
>> QNetworkRe
On 06/08/2014 12:10 PM, igor.mironc...@gmail.com wrote:
>
> QCoreApplication app( argc, argv );
>
> Object o;
> QThread t;
> o.moveToThread( &t );
> t.start();
>
> QTimer::singleShot( 0, &o, SLOT( start() ) );
>
Hi Igor,
why are you using a QTimer? As far as I know, you could invoke the slot
I’ve added Launcher that works on the main thread. His job is just emit start()
signal.
My Object on the different thread connects to this start() signal.
Now Launcher emits start() signal. All is ok. But Object doesn’t receive it...
Why?
From: igor.mironc...@gmail.com
Sent: Sunday, June 08, 2
Hi,
for example I have Object with slot start.
And I create that object with the next code:
QCoreApplication app( argc, argv );
Object o;
QThread t;
o.moveToThread( &t );
t.start();
QTimer::singleShot( 0, &o, SLOT( start() ) );
app.exec();
But this code doesn’t invoke slot start() after laun
13 matches
Mail list logo
