Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

If I understand your question correctly, you may use alias property to point to children of main / navigation bar. In Angular JS, they call this feature as "transclude". For example, Screen.qml: Item { property alias main : mainContainer.children } CustomScreen.qml: Screen { main: Item {

Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

Von: Elvis Stansvik An: "interest@qt-project.org Interest" Gesendet: 22.03.2016 20:19 Betreff: Re: [Interest] Structuring of QML app as set of interlinked screens for maximum code reuse 2016-03-22 20:13 GMT+01:00 Elvis Stansvik

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

Hello, I don't work with QML, but I'm pretty sure the events are processed in the order of their appearance in the event queue. So if you have a `deleteLater` call (i.e. you have a QEvent::DeferredDelete, which is scheduled through the event loop) any queued call to a slot (i.e. QEvent::MetaCall)

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

Hi, I saw your bug report. I encountered the same problem last week and I found a workaround by passing the properties that belong to another object one by one to JSon object. For example, setSource("qrc:/LoaderItem.qml", { "color": theGame.player.color }) But in my case there was only one

[Interest] Structuring of QML app as set of interlinked screens for maximum code reuse

Hi all, I'm working on a fullscreen Qt Quick/QML app (for machine control) which will consist of a set of interlinked screens, with key presses as the only interaction method. Each screen will have roughly the following QML structure: Rectangle { NavBar { id: topBar ...

[Interest] Ensuring that a queued invocation occurs after deferred deletion

I recently discovered [1] that Loader defers deletion of items via deleteLater(). Up until that point, I had been treating certain operations in my program as synchronous (as I haven't introduced threads yet). Now that I can't safely assume that UI items will be instantly destroyed, I have to

Re: [Interest] "Internal mouse button tracking invalid" messages

> On Mar 22, 2016, at 5:30 AM, René J. V. Bertin wrote: > > Any idea if the proposed changes in the code reviews are in any way > backportable > to 5.6? No idea at all. I only know about the bug because it affects us. -John Weeks

[Interest] Qt/JNI blows up on android when activity is closed

As my app's tendrils root further into the mobile OSs, I've found one very troubling issue. I have an alarm manager and a service to handle the pending intent. The service talks to Qt through JNI. This works for as long as my Qt Activity exists. However if the activity is closed (user task

Re: [Interest] Astropad and Tablet events

On 22 Mar 2016, at 20:18, Rutledge Shawn wrote: On 22 Mar 2016, at 02:30, Alexei Gilchrist wrote: Hi all, I'm trying to use Astropad (app provides OsX tablet interface with an iPad) with an app I’ve written and I'm getting odd results with tablet events in QT. First of

Re: [Interest] "Internal mouse button tracking invalid" messages

John Weeks wrote: > https://bugreports.qt.io/browse/QTBUG-42846 Thanks, I think that answers my question. Any idea if the proposed changes in the code reviews are in any way backportable to 5.6? R. ___ Interest mailing list Interest@qt-project.org

[Interest] Freetype and color fonts

Hi all, I've been trying to use Google color emoji font https://www.google.com/get/noto/#emoji-qaae-color with no luck. When I try to load the font using FontLoader I obtain an error: QML FontLoader: Cannot load font: "file:///E:/Qt/FontTest/NotoColorEmoji.ttf" but the font is in place, I can