I'm coming to Qt late, after a long history with wxPython (and an even longer history with direct-to-the API coding). There's one item that is tripping me up.
In wxPython and wxWidgets, EVERYTHING you can respond to is an event. When you want to handle some GUI thing, you look for an event to bind to. Since Qt is, in general, more orderly than wx, I had assumed that Qt would be much the same, substituting signals and slots. I've already found that's not the case; in order to intercept keystrokes, I have to subclass the control and provide a a keyPressEvent method. Is there some document that can help me understand what's likely to be signalled and what requires subclassing? Some general rule you use in practice? -- Tim Roberts, [email protected] Providenza & Boekelheide, Inc. _______________________________________________ PySide mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/pyside
