Gordon Tyler wrote:
kscalet wrote:
what would be the best approach in finding out, if a signal is send due to a "real" gui action
like key-presses and mouse-clicks, or due to a programmatic action like setButton,
setCurrentText, etc on a specific widget.
It's often needed to trigger some action only in the former case, so I assume, there is an easy
way to find out the "source" of action, but did not find it out myself.
http://doc.trolltech.com/3.2/qobject.html#sender
This looks more like a solution to my 2nd problem. Or is there some more info I can get from the sender (activated by gui-clicking / activated by set-function)? As of Phil, there isn't.
What are you actually trying to accomplish here? What is the specific case?
http://doc.trolltech.com/3.2/qsignalmapper.html
If I understand this correctly, it would give me a nice way to, say, map 3 QButtons (no data!) to one slot.
Yep.
Ciao, Gordon
_______________________________________________ PyKDE mailing list [EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
