Hi,
The Timer element is not officially supported in the designer. The designer
does show an error message, that you can ignore though.
There are work arrounds for your isse:
1) Use .ui.qml files and decouple the logic that requires the Timer from the
pure form (see: http://doc.qt.io/qtcrea
Hi,
I guess using a TCP connection would still be possible, but not be the defaut
anymore for local debugging/profiling?
Kind Regards,
Thomas Hartmann
From: development-bounces+thomas.hartmann=digia@qt-project.org
[development-bounces+thomas.hartmann
Hi,
please note that we had to hand edit some files to work around limitations of
the code model.
Currently I am aware of the fact that we have to "forward declare" Window in
the qmltypes file of controls.
So please if you update a qmltypes file check the history and if you see
something "weird
April 2014 11:38
To: Hartmann Thomas
Cc: development@qt-project.org; Alan Alpert
Subject: Re: [Development] Perceptions/Understandings of the QML language [was:
Question about Qt's future]
On Wednesday 30. April 2014 11.11.39 Hartmann Thomas wrote:
> Hi,
>
> > Can you elaborate
Hi,
> Can you elaborate a bit with an example what this means?
Some rough ideas were discussed here:
http://lists.qt-project.org/pipermail/development/2013-June/011572.html
Kind Regards,
Thomas Hartmann
___
Development mailing list
Development@qt-proj
Hi,
On Mon, Apr 28, 2014 at 2:34 PM, André Pönitz wrote:
> I think at least three modifications are inavoidable: For one, things that
> could be written in a declarative way but which currently are only possible
> using JavaScript, a declarative way should be added. Second, it should be
> stresse
_
From: development-bounces+thomas.hartmann=digia@qt-project.org
[development-bounces+thomas.hartmann=digia@qt-project.org] on behalf of
André Somers [an...@familiesomers.nl]
Sent: 28 April 2014 11:57
To: development@qt-project.org
Subject: Re: [Development] Question about Qt's f
(QJSContext context)
{
context.get("mouse.x")
}
But currently this is not more then a couple of wild ideas.
Kind Regards,
Thomas Hartmann
From: Nils Jeisecke [njeise...@saltation.de]
Sent: 28 April 2014 11:56
To: Hartmann Thomas
Cc: deve
s expected?
Kind Regards,
Thomas Hartmann
From: Nils Jeisecke [njeise...@saltation.de]
Sent: 28 April 2014 11:00
To: Hartmann Thomas
Cc: development@qt-project.org
Subject: Re: [Development] Question about Qt's future
Hi,
> Another idea is to a
Hi,
while (at least for me) it is not really clear where exactly the boundary
between declarative and functional programming lies, we could/should at least
rule out control flow statements and anything with side effects in bindings.
The statement "width: Math.floor(height)" could be considered
10 matches
Mail list logo
