Matthias, The documentation for Qt 4.6.2 does not mention a NOTIFY section for Q_PROPERTY. Is this new to 4.7?
Thanks, John On Apr 15, 2010, at 10:37 AM, <[email protected]> <[email protected]> wrote: > > The dynamic parts of the UI should be build entirely based on properties > provided by the CodeBehind. If those properties are notifyable (i.e. the > Q_PROPERTY macro contains a NOTIFY section), then the UI will update itself. > > A less pretty and less declarative way would be to emit a signal from > CodeBehind, and then have a signal handler in QML react to it imperatively. > But that would be old school. QML's property bindings are waaaaay more > elegant. > > Matthias > ________________________________________ > From: [email protected] [[email protected]] On Behalf > Of ext Peter Matuchniak [[email protected]] > Sent: Thursday, April 15, 2010 8:37 PM > To: [email protected] > Subject: [Qt-qml] Best way to update QML display based on external input via > TCP socket? > > Hello > > I have a Qt main application that does the following (with my descriptions in > parentheses): > > - Displays a QML user interface (the “UI”) > > - Handles user events in a C++ class (the “CodeBehind”) > > - Listens on a TCP socket for external input (the “Listener”) > > Here’s my question: > > - What is the best way for the Listener to cause some update in the > UI to occur when the Listener receives some external command via TCP > > Note: > > - I already have the Listener functioning and receiving commands > > - I already have the CodeBehind acting upon input from the UI > > - What I need is to have a way to affect the UI from the Listener > > Kind regards > Peter > > > > __________________________________________________________________ > > This email and any files transmitted with it are confidential & proprietary > to Systems and > Software Enterprises, Inc. (dba IMS). This information is intended solely for > the use of > the individual or entity to which it is addressed. Access or transmittal of > the information > contained in this e-mail, in full or in part, to any other organization or > persons is not > authorized. > > __________________________________________________________________ > > > > > > > _______________________________________________ > Qt-qml mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-qml _______________________________________________ Qt-qml mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-qml
