Clearing the signal queue

[wysota]

This situation is not well suited for signals and slots. If you expect exactly one receiver for a signal and you know the receiver upfront then why not interact with it directly? Either post an event to the other object or implement some kind of a message queue between two objects.

[grabalon]

"If you expect exactly one receiver for a signal and you know the receiver upfront then why not interact with it directly?"

Signals, or events (I consider them equivalent when using a queued connection across threads) give me a simple means of passing information from my main thread to my worker thread. The problem I have is that the user can obsolete previously sent commands before the worker has had time to process them. Is it easier to clear out posted events than it is to clear a signal queue? Is there another message queuing structure within QT that would do a better job at what I am trying to do, or should I look at 3rd party libraries?

[wysota]

Is it easier to clear out posted events than it is to clear a signal queue?

Physically yes, logically no. You can send (not post but send) an event to the other thread to order it to ignore some other events. Of course you have to implement that all and you have no guarantees whether the other thread didn't manage to process those events in the meantime.

Is there another message queuing structure within QT that would do a better job at what I am trying to do, or should I look at 3rd party libraries?

Does everything have to be given on a silver platter? Can't you use QQueue with a mutex or other similarily simple solution?

[squidge]

What you need is to call methods directly which directly manage a list, then you have full control.

eg. in your header file:

QReadWriteLock listlock;
    QList<myListType*> list;

QReadWriteLock listlock;
    QList<myListType*> list;

To copy to clipboard, switch view to plain text mode 

then, in an append method:

listlock.lockForWrite();
list.append(foo);
listlock.unlock();

listlock.lockForWrite();
list.append(foo);
listlock.unlock();

To copy to clipboard, switch view to plain text mode 

then you can have clear method, private read method, etc.

[This is only an example, there are lots of other ways to do it]

[grabalon]

The list idea is exactly what I need. Thanks to all for your help.