The priority handling must be done by something
that is external to the two components involved. This could be the
signal/slot framework itself or a manager class.
Again, the source and receiver should not known about their respective
priorities, but it is the framework and design time wiring that must
specify the priorities, independent of the actual components sending
or consuming the signal.
On Oct 24, 2008, at 1:50 PM, André Pönitz wrote:
Still you are requesting a feature that makes the components
more depending on each other by requiring them to know about
thei respective "priorities".
If a component says "I want to be called first" it implicitly admits
there maybe others. Even worse: in case there are others that want
to be called first, too, there's a problem that can't really be
solved without the components talking to each other. Using
a set of fixed priorities is not different from the "multiple signal"
workaround I mentioned.
To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
"unsubscribe" in the subject or the body.
List archive and information: http://lists.trolltech.com/qt-interest/