Main Event Loop response to all signals

[^NyAw^]

Hi,

I have a Thread that emits "results" that have to be computed in the main Thread. The Thread emits a signal like "mySignal(bool)" so the result of the processing is passed to the main Thread. The problem is that the Main Event Loop joins a group of those signals into one slot call because the signals contain the same value:

true
true
true
true
...
true
false
true
true
true
...

true
true
true
true
...
true
false
true
true
true
...

To copy to clipboard, switch view to plain text mode 

Using a random value as a second argument will force the Main Event Loop to call the slot for every signal emitted?

I need this because in the Main Thread there is a IO card that must activate or deactivate some Outputs. For the complexity of the application it can't be done directly on the worker thread as could be there more than a thread that give results and then this results are joined and finally must activate the Outputs according this joined result.

Thanks,

[wysota]

You can always use QCoreApplication::postEvent() and QObject::customEvent() instead of signals.

[^NyAw^]

Hi,

I have tryied but the application was very slow. Maybe I did it wrong. I have deleted the code but it was like this:

worker thread

...
QCoreApplication::postEvent(myObject,new myEvent());
...

...
QCoreApplication::postEvent(myObject,new myEvent());
...

To copy to clipboard, switch view to plain text mode 

myClass

bool myClass::event(myEvent *event)
{
  ...
  return true;
}

bool myClass::event(myEvent *event)
{
  ...
  return true;
}

To copy to clipboard, switch view to plain text mode 

Thanks,

Hi again,

I have rewrited the code using "QCoreApplication:ostEvent()" and it works fine. The application works as expected.

Using "QCoreApplication:ostEvent()", all the events are processed?

So, using this way I don't need to use mutexes to lock the main and the worker threads about results.

Thanks,

[wysota]

You are supposed to use customEvent() and not event().