It's tempting to make the "detect shadowing and give error" a warning only,
which is turned off when deploying on a device.
But this would only remove *some* pointless fstats. Given that fstats on
certain types of devices are slow, we should avoid them altogether.
One solution: create qmldi
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" wrote:
My mistake. NOTIFY is listed in the Q_PROPERTY documentation in 4.6, but not
consistently.
In the
The concept itself is fine - as you say, QML doesn't really *need* an order for
resolving, it just needs to be well-defined.
A potential problem with this "detect shadowing and give error" is the cost of
implementing the exhaustive search - I believe the code in the "#if 1" is the
added expense
On Fri, 16 Apr 2010 06:04:13 am ext Louis Koziarz wrote:
> Hi all,
>
> I'm working on a flickable ListView where the items in the Model contain
> MouseArea buttons. The MouseAreas work correctly (with onPressed,
> onClicked, etc), but when the mouse is down and moves inside of the
> MouseArea, th
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 b
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,
wrote:
>
> The dynamic parts of the UI should be build entirely based on properties
> provided by the CodeBehind. If those properties
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
Hi all,
I'm working on a flickable ListView where the items in the Model contain
MouseArea buttons. The MouseAreas work correctly (with onPressed,
onClicked, etc), but when the mouse is down and moves inside of the
MouseArea, the flickable area underneath starts to move.
Is there some way to tel
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
Fellow qml hackers,
I wasn't too happy with type shadowing and resolving in current qml.
Background: the implicit "." import has been moved to be the last import
checked. This was done in order to support our previous coding convention with
case insensitive file systems.
Example:
Foo/foo.qml
Hi,
QML now prohibits you from assigning to the ³onDestroyed² property of
objects. Code like this is now banned:
Item {
onDestroyed: print(³Goodbye cruel world!²)
}
Those of you familiar with C++ will know that QML inherits this property
because QObject happens to have a destroyed() signal.
On Thu, 15 Apr 2010 04:53:13 pm ext Brett Morgan wrote:
> Is there a lighter way of getting to qt convenience functions like
> QColor's lighter() from QML hosted javascript?
Not generally speaking, but there are a number of useful methods in the Qt
global object, including Qt.lighter()
http://qt
12 matches
Mail list logo
