[Qt-qml] Best way to update QML display based on external input via TCP socket?
aaron.kennedy at nokia.com
aaron.kennedy at nokia.com
Fri Apr 16 02:23:35 CEST 2010
Hi,
Yes, the QObject documentation is out of date. I've fixed it, but it will take a while to make its way to the public website.
Cheers,
Aaron
On 16/04/10 6:58 AM, "ext John Vilburn" <john at ohanasoftware.com> wrote:
My mistake. NOTIFY is listed in the Q_PROPERTY documentation in 4.6, but not consistently.
In the QObject Class Reference, Q_PROPERTY is listed like this:
Q_PROPERTY(type name
READ getFunction
[WRITE setFunction]
[RESET resetFunction]
[DESIGNABLE bool]
[SCRIPTABLE bool]
[STORED bool]
[USER bool])
But on the Qt's Property System page it is listed like this:
Q_PROPERTY(type name
READ getFunction
[WRITE setFunction]
[RESET resetFunction]
[NOTIFY notifySignal]
[DESIGNABLE bool]
[SCRIPTABLE bool]
[STORED bool]
[USER bool]
[CONSTANT]
[FINAL])
Is this just a case of the QObject Class Reference being out of date, or is there another reason for the discrepancy?
Thank you,
John
On Apr 15, 2010, at 10:48 AM, John Vilburn wrote:
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, <matthias.ettrich at nokia.com> <matthias.ettrich at nokia.com> 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: qt-qml-bounces at trolltech.com [qt-qml-bounces at trolltech.com] On Behalf Of ext Peter Matuchniak [pmatuchniak at imsco-us.com]
Sent: Thursday, April 15, 2010 8:37 PM
To: qt-qml at trolltech.com
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
Qt-qml at trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-qml
_______________________________________________
Qt-qml mailing list
Qt-qml at trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-qml
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt.nokia.com/pipermail/qt-qml/attachments/20100416/9883e43f/attachment.html
More information about the Qt-qml
mailing list