You mean QML or QtQuick? If you want to instantiate widgets from QML then I
think this should not be a problem (as you can instatiate there any
QObject), just expose them to QML engine. If you mean embedding QWidget in
a QtQuick application, then Olivier gave you the answer.
BR,
Filip
On Wed,
On Wednesday 26 Nov 2014 09:06:25 Till Oliver Knoll wrote:
Am 26.11.2014 um 06:28 schrieb Igor Mironchik igor.mironc...@gmail.com:
Hi guys,
Is it possible to use QWidget based components in QML?
This might lead to the answer:
http://qt-project.org/forums/viewthread/7893
The
QML module versions is somewhat fuzzy area for me, so I'm
looking for some advice.
Some of my files start with a barrage of imports, like
import QtQuick 2.3
import QtQuick.Controls 1.2
import QtQuick.Window 2.2
import QtSensors 5.0
import QtMultimedia 5.4
That becomes lots of versions to keep
No, it can't.
-Richard
Fra: interest-bounces+richard.gustavsen=theqtcompany@qt-project.org
interest-bounces+richard.gustavsen=theqtcompany@qt-project.org på vegne
av Mike Krus mike.k...@gmail.com
Sendt: 25. november 2014 19:46
Til:
I have tried to get QtQuick2 maps to work with flickable. The issue is
that Flickable steals touch events from Maps gesture area. There is no
prevent stealing property on map component.
QDeclarativeGeoMap inherits QQuickItem . QQuickItem has
grabTouchPoints(const QVectorint ids) and
Hi,
While I'm not aware of the versions being well documented, the
autocomplete in QtCreator seems to offer all the available versions, so
you can check that. The idea originally was that the versions should
reflect the Qt module version, but IIRC this is not strictly true, as
the version
On 26 November 2014 at 13:29, Attila Csipa q...@csipa.in.rs wrote:
The good news is your 2.0 statement will import whatever the latest
implementation registers for the 2.0 version. The ((un)intended?)
side-effect of this is that the backward compatibility is not 100% - if
you relied on
On 11/26/2014 1:39 PM, Tomasz Siekierda wrote:
On 26 November 2014 at 13:29, Attila Csipa q...@csipa.in.rs wrote:
The good news is your 2.0 statement will import whatever the latest
implementation registers for the 2.0 version. The ((un)intended?)
side-effect of this is that the backward
Hello,
As part of the website updates, the download page on qt-project.org is now
redirected to qt.io.
You can read the details at the blog (which will also move to a qt.io address
in the near future).
http://blog.qt.digia.com/blog/2014/11/26/qt-downloads-moving-to-qt-io/
Best regards,
Tero
On Wednesday, November 26, 2014 12:53:54 PM Kate Alhola wrote:
I have tried to get QtQuick2 maps to work with flickable. The issue is
that Flickable steals touch events from Maps gesture area. There is no
prevent stealing property on map component.
QDeclarativeGeoMap inherits QQuickItem .
that’s a pity. Apple now accepts the use of frameworks, would be nice to make
easier to conform with the LGPL, not to mention not having to deploy huge
binaries to the device every time you change your code and rebuild...
On 26 Nov 2014, at 09:06, Gustavsen Richard
On Wednesday 26 November 2014 13:29:12 Attila Csipa wrote:
The import versioning system as done by Qt is a sort of API handshake -
it doesn't actually select between different implementations, you just
select feature-sets. Thus, you should always import the latest (for
better or worse).
I am seeing confusing QEvent::WindowActivate events associated with floating
windows on Macintosh. I wonder if someone can give me an explanation. Please
excuse the length...
The code here is a vastly simplified version of actual application code.
I use code like this to make three floating
Hi,
Is there any way of retrieving a unique device identifier with Qt?
Nuno Santos
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On Wednesday 26 November 2014 19:30:50 Nuno Santos wrote:
Hi,
Is there any way of retrieving a unique device identifier with Qt?
What device?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
I wonder if there is a more user friendly site to list archives
somewhere than what
http://lists.qt-project.org/pipermail/ provides by default?
Many posts are shown just as one very long line in my Firefox.
A nice formatting for reading would good, a search feature would be even
better.
Maybe
On Wednesday 26 November 2014 21:07:57 Harri Pasanen wrote:
I wonder if there is a more user friendly site to list archives
somewhere than what
http://lists.qt-project.org/pipermail/ provides by default?
Many posts are shown just as one very long line in my Firefox.
A nice formatting for
Sorry, I forgot to specify.
I was looking for a unified solution for iOS and Android.
iOS has the identifierForVendor which gives a unique identifier per vendor. The
unique device id was deprecated:
[[UIDevice currentDevice] identifierForVendor];
Android seems to have a few options as well.
On 11/26/2014 7:34 PM, Thiago Macieira wrote:
On Wednesday 26 November 2014 13:29:12 Attila Csipa wrote:
The import versioning system as done by Qt is a sort of API handshake -
it doesn't actually select between different implementations, you just
select feature-sets. Thus, you should always
Guys,
Less than 10 days for the deadline for the Desktops DevRoom at FOSDEM 2015
and not a single Qt-related talk submited.
I cannot really believe nobody has anything to say!
Call for Talks:
http://www.elpauer.org/2014/10/fosdem-2015-desktops-devroom-call-for-talks/
--
Pau Garcia i Quiles
20 matches
Mail list logo
