qt-quick

Let's consider the following example: we have a Qt Quick Controls Button . The user clicks it twice within 5 seconds. After pushing the Button for the first time, the QML Timer is running for these 5 seconds. We want to measure the time elapsed between two clicks, with a millisecond accuracy. Unfortunately, the QML Timer can't show us the elapsed time. As suggested on the BlackBerry forums, it would be possible to compare the dates. This isn't very handy, though, since the first click might occur on 31 Dec 2015, 23:59:55 and the second on 1 Jan 2016, 00:00:05 and the check would have to be

According to this article, there are two main methods for rendering raw OpenGL into an application whose UI is otherwise managed by QtQuick's scene graph. In short, they are (according to my understanding): Calling raw OpenGL methods in hand-written code that is hooked into the scene graph's render loop through some APIs exposed by QtQuick. Rendering the raw OpenGL portion of your scene to a QQuickFramebufferObject, which is treated like a component in the scene graph and itself rendered as if it were a texture. What are the advantages/disadvantages of the two approaches? The issue with

We're building a Qt Quick app, that must be able to save a file under a given name . In the FileDialog component you can only set a directory. This is not very user-friendly, since you don't want to type in a filename by hand every time you download a file. So far we tried different things FileDialog from QtQuick.Dialogs: filename cannot be set Native dialog via QPlatformFileDialogHelper (naughty private c++ hack): filename cannot be set on Linux (Gnome) Native dialog via static QFileDialog::getSaveFileName(): in Quick application there is no QWidget available for 'parent' QT dialog via

I have an qt widgets application. I want to add the switch control to my form. I added to my form QDeclarative widget and add this line to the code but nothing shown. ui->declarativeView->setSource(QUrl::fromLocalFile("test.qml")); This is the content of the qml file (I added this file to the resources) It display in qtcreator under resources/[project_name.qrc]/test.qml import QtQuick 2.4 import QtQuick.Controls 1.3 Button{ text:aaaa } I added the pro file : qt += declarative What am i doing wrong?? I'm using Qt 5.4.1 QtCreator 3.3.1. techneaz 1. QDeclarativeView is for older Qt versions. If

I'm learning QtQuick and I'm playing with data binding between C++ classes and QML properties. In my C++ object Model, I have two properties : Q_PROPERTY(QString name READ getName WRITE setName NOTIFY nameChanged) Q_PROPERTY(bool status READ getStatus WRITE setStatus NOTIFY statusChanged) And in my .qml file : TextEdit { placeholderText: "Enter your name" text: user.name } Checkbox { checked: user.status } When I change the user name with setName from my C++ code, it is automatically reflected in the view. When I check/uncheck the checkbox, or when I call setStatus() from my C++ code, nothing

How do I deal with 64 bit integers in QML? I know that useless Javascript can't handle them normally as it uses doubles for everything, and if I try to use them in a signal, everything gets set to undefined . Is there a way around this? Perhaps I have to use a QVariant or something? Simon Warta Create your own Integer64 class derived from QObject and give it the functions you need, like class Integer64 : public QObject { Q_OBJECT public: // ... Q_PROPERTY(QString value READ value WRITE setValue NOTIFY valueChanged) QString value() const; void setValue(QString value); Q_INVOKABLE void add

I'm trying to add effects to my items using QtQuick 2 with QtGraphicalEffects, but I don't quite understand how to tweak really blurry effects to look right. In this case, the drop shadow is poorly sized and is getting clipped at the edges before it entirely fades away. How can I make it blend in nicely and not get cut off? This is the code for the window: import QtQuick 2.0 import QtGraphicalEffects 1.0 Item { width: 250 height: 75 Text { id: textItem x: 10; y: 10 text: "how can I fix my shadow?" } DropShadow { id: shadowEffect anchors.fill: textItem source: textItem radius: 8 samples: 16