Re: [Interest] QMetaProperty::write behavior changed with Qt 5.6 - Bug?

On sábado, 7 de maio de 2016 01:36:42 PDT Christian Ehringfeld wrote: > Yes, you can find it here: > https://github.com/Professi/metaproperty-write-test > Test fails under Qt 5.6 and is succesful under Qt 5.5.1. > When I remove the inheritance between person and entity it also works > with Qt 5.6.

Re: [Interest] Migrating QWeakPointer to Qt5

On Sat, May 7, 2016 at 12:54 AM, Thiago Macieira wrote: > > > Yes, by actually using a QSharedPointer for the constructor (as > > QWeakPointer is a weak reference to a shared pointer). > > That's not the same thing. For a while, we had deprecated QPointer in > favour >

Re: [Interest] QMetaProperty::write behavior changed with Qt 5.6 - Bug?

2016-05-07 1:36 GMT+02:00 Christian Ehringfeld : > Yes, you can find it here: > > https://github.com/Professi/metaproperty-write-test > > Test fails under Qt 5.6 and is succesful under Qt 5.5.1. Just for reference, I tested on 5.2.1 and it fails there as well. But yes,

Re: [Interest] QMetaProperty::write behavior changed with Qt 5.6 - Bug?

Yes, you can find it here: https://github.com/Professi/metaproperty-write-test Test fails under Qt 5.6 and is succesful under Qt 5.5.1. When I remove the inheritance between person and entity it also works with Qt 5.6. Am Freitag, den 06.05.2016, 14:56 -0700 schrieb Thiago Macieira: > On

Re: [Interest] qt.labs.controls / QtQuickControls2: ToolBar, Label / Image Colors, tinting...

I think that is better to used a ShaderEffect instead of QtGraphicalEffects that comes with an FBO. An FBO can take a lot a GPU resources and doesn't works well with some Android phone due to bad drivers. I personally use this : ShaderEffect { visible: Qt.colorEqual(parent.color,

Re: [Interest] Role of `qmlscene` and `qml` command line tools

2016-05-06 23:47 GMT+02:00 Thiago Macieira : > On sexta-feira, 6 de maio de 2016 10:50:45 PDT Shawn Rutledge wrote: >> > The reason I'm asking is I'm building a QML application for embedded >> > use. The app is QML only, apart from some calls from QML into Python >> >

Re: [Interest] QMetaProperty::write behavior changed with Qt 5.6 - Bug?

On sexta-feira, 6 de maio de 2016 23:44:25 PDT Christian Ehringfeld wrote: > I have already asked this question in the Qt Forum and was sent on to this > place. I can't find a way to fix this problem. Is it a bug or a feature? > Does anybody have an idea for a workaround? Can you provide an

Re: [Interest] Migrating QWeakPointer to Qt5

On sexta-feira, 6 de maio de 2016 12:14:14 PDT Nye wrote: > On Fri, May 6, 2016 at 8:35 AM, Tom Isaacson > > wrote: > > I'm moving some Qt4.8.2 code which uses QWeakPointer to Qt5.6. > > Simplifying a lot it looks like this: > > [snippet ..] > > but when I compile under

Re: [Interest] Enabling NEON on a Qt Android app

On sexta-feira, 6 de maio de 2016 00:38:10 PDT Thiago Macieira wrote: > On sexta-feira, 6 de maio de 2016 07:58:30 PDT Nuno Santos wrote: > > What are the necessary steps in order to enable NEON on a Arm processor > > that supports it? > > Compile a plugin for Neon and a plugin for non-Neon. At

Re: [Interest] Role of `qmlscene` and `qml` command line tools

On sexta-feira, 6 de maio de 2016 10:50:45 PDT Shawn Rutledge wrote: > > The reason I'm asking is I'm building a QML application for embedded > > use. The app is QML only, apart from some calls from QML into Python > > using pyotherside [2] when interfacing with the hardware. So in theory > > I

[Interest] QMetaProperty::write behavior changed with Qt 5.6 - Bug?

Hello, The behavior of  QMetaProperty::write has changed with 5.6.  In a special situation it is no longer working as intended (by me). This appears to be a show stopper for my project. // working with Qt < 5.6, failing with Qt 5.6  void EntityHelper::setListProperty(const QSharedPointer ,

Re: [Interest] React to signal only when at top of StackView

2016-05-06 22:41 GMT+02:00 J-P Nurmi : >> On 06 May 2016, at 22:27, Elvis Stansvik wrote: >> >> Hi all, >> >> I want that an item reacts to a certain signal only when it is at the >> top of a StackView, so I tried something like: >> >>Connections

Re: [Interest] React to signal only when at top of StackView

2016-05-06 22:39 GMT+02:00 Jason H : > > Why not handle the signal and see if you are visible? Yes, that should also work. But I realize now my mistake was just like J-P suggested, that I was using the Stack.status property attached to the Connections element, not the Rectangle

Re: [Interest] React to signal only when at top of StackView

2016-05-06 22:41 GMT+02:00 J-P Nurmi : >> On 06 May 2016, at 22:27, Elvis Stansvik wrote: >> >> Hi all, >> >> I want that an item reacts to a certain signal only when it is at the >> top of a StackView, so I tried something like: >> >>Connections

Re: [Interest] qt.labs.controls / QtQuickControls2: ToolBar, Label / Image Colors, tinting...

Thanks, J-P, I'll try it out ekke Am 06.05.16 um 21:19 schrieb J-P Nurmi: > Hi ekke, > > One possibility for tinting images could be to use ColorOverlay from > QtGraphicalEffects: > http://doc.qt.io/qt-5/qml-qtgraphicaleffects-coloroverlay.html > > -- > J-P Nurmi > > > >> On 06 May 2016, at

Re: [Interest] React to signal only when at top of StackView

> On 06 May 2016, at 22:27, Elvis Stansvik wrote: > > Hi all, > > I want that an item reacts to a certain signal only when it is at the > top of a StackView, so I tried something like: > >Connections { >// Below won't work: >

Re: [Interest] React to signal only when at top of StackView

Why not handle the signal and see if you are visible? ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest

[Interest] React to signal only when at top of StackView

Hi all, I want that an item reacts to a certain signal only when it is at the top of a StackView, so I tried something like: Connections { // Below won't work: target: Stack.status === Stack.Active ? button : null

Re: [Interest] qt.labs.controls / QtQuickControls2: ToolBar, Label / Image Colors, tinting...

Hi ekke, One possibility for tinting images could be to use ColorOverlay from QtGraphicalEffects: http://doc.qt.io/qt-5/qml-qtgraphicaleffects-coloroverlay.html -- J-P Nurmi On 06 May 2016, at 19:49, ekke > wrote: just noticed that in Qt

Re: [Interest] qt.labs.controls / QtQuickControls2: ToolBar, Label / Image Colors, tinting...

just noticed that in Qt 5.7 there's a new property Material.foreground: http://doc-snapshots.qt.io/qt5-5.7/qtquickcontrols2-material.html#foreground-attached-prop seems this didn't make it into the 5.7 Beta from docs: The default value is theme-specific (light or dark). So there's no dependency

[Interest] qt.labs.controls / QtQuickControls2: ToolBar, Label / Image Colors, tinting...

it's really easy to create a Toolbar with Title and Menu using qt.labs.controls and Material style: import QtQuick 2.6 import QtQuick.Layouts 1.3 import Qt.labs.controls 1.0 import Qt.labs.controls.material 1.0 ToolBar { id: titleToolBar property alias text: titleLabel.text RowLayout

Re: [Interest] How to set Android Version and App Name

It seems are you using “ant” for building the app. You should switch to “gradle”. “ant” has been deprecated years ago, and I never got your problem using “gradle” Ciao, Gianluca. > On 6 May 2016, at 16:55, NoRulez wrote: > > I got this from the Build log: > > . > . > . >

Re: [Interest] How to set Android Version and App Name

Hi ekke, I do not use Qt creator. I build it with CMake on the command line. Regards > Am 06.05.2016 um 07:32 schrieb ekke : > >> Am 05.05.16 um 21:47 schrieb NoRulez: >> Hello, >> >> I tried to deploy my first example app to my device. >> I noticed that the app name is

Re: [Interest] How to set Android Version and App Name

I got this from the Build log: . . . Stripping libraries to minimize size. Updating Android package files with project settings. -- res/values/libs.xml -- AndroidManifest.xml -- /src/org/qtproject/qt5/android/bindings/QtActivity.java Pregenerating entry list for assets file engine. Running

Re: [Interest] Role of `qmlscene` and `qml` command line tools

2016-05-06 16:27 GMT+02:00 Shawn Rutledge : > >> On 06 May 2016, at 15:16, Elvis Stansvik wrote: >> >> Alright, I see. There's probably some JS lib out there I could use, >> after stripping everything after Qt.application.arguments[0] up to and >>

Re: [Interest] [QT3D] How to make billboard?

> I am interesting if there are ready to use classes or functions to make > billboards (2D elements in 3D world that always faces the camera) in QT3D > (qml and cpp). >  As I see by https://bugreports.qt.io/browse/QTBUG-24454 in Qt3D 1.0 there > was BillBoardTransform class, functionality of

Re: [Interest] Role of `qmlscene` and `qml` command line tools

> On 06 May 2016, at 15:16, Elvis Stansvik wrote: > > Alright, I see. There's probably some JS lib out there I could use, > after stripping everything after Qt.application.arguments[0] up to and > including the '--'. > > The point about trust is valid for any application

[Interest] Window icon for pure QML app

Hi all, I recently switched to using `qml` to launch my pure QML app. How can I set the window icon? My root item is a Window. I found this post from 2013: http://comments.gmane.org/gmane.comp.lib.qt.user/5645 Which sounds like bad news. No way to do that short of making a C++ launcher

[Interest] [QT3D] How to make billboard?

Hello, I am interesting if there are ready to use classes or functions to make billboards (2D elements in 3D world that always faces the camera) in QT3D (qml and cpp). As I see by https://bugreports.qt.io/browse/QTBUG-24454 in Qt3D 1.0 there was BillBoardTransform class, functionality of which

Re: [Interest] Role of `qmlscene` and `qml` command line tools

2016-05-06 11:36 GMT+02:00 Elvis Stansvik : > Hi all, > > Since some time, the `qmlscene` command has been available for > debugging QML applications: > > > [estan@pyret ~]$ qmlscene --help > Usage: qmlscene [options] > > Options: > --maximized .. Run

Re: [Interest] Role of `qmlscene` and `qml` command line tools

2016-05-06 13:34 GMT+02:00 Shawn Rutledge : > >> On 6 May 2016, at 13:07, Elvis Stansvik wrote: >> >> [estan@pyret ~]$ qml test.qml -- --foo bar >> qml: /usr/lib/qt/bin/qml,test.qml,--,--foo,bar >> [estan@pyret ~]$ >> >> Do you know if there's any QML API

Re: [Interest] Role of `qmlscene` and `qml` command line tools

> On 6 May 2016, at 13:07, Elvis Stansvik wrote: > > [estan@pyret ~]$ qml test.qml -- --foo bar > qml: /usr/lib/qt/bin/qml,test.qml,--,--foo,bar > [estan@pyret ~]$ > > Do you know if there's any QML API to get just the arguments following > "--"? Or I'll have to parse that

Re: [Interest] Role of `qmlscene` and `qml` command line tools

2016-05-06 12:50 GMT+02:00 Shawn Rutledge : > >> On 6 May 2016, at 11:36, Elvis Stansvik wrote: >> >> Hi all, >> >> Since some time, the `qmlscene` command has been available for >> debugging QML applications: >> >> … >> Recently, the `qml` command is

Re: [Interest] What's the recommended way to put QObjects in smart pointers?

On 05/05/16 07:19, Thiago Macieira wrote: On quinta-feira, 5 de maio de 2016 04:24:48 PDT Nikos Chantziaras wrote: So what are you requirements? Do you want to a container that does delete the object it has, unless the parent has already deleted it? Well, basically what I want is not having

Re: [Interest] Role of `qmlscene` and `qml` command line tools

> On 6 May 2016, at 11:36, Elvis Stansvik wrote: > > Hi all, > > Since some time, the `qmlscene` command has been available for > debugging QML applications: > > … > Recently, the `qml` command is also available: > > The tools seem quite similar. What was the rationale

[Interest] Role of `qmlscene` and `qml` command line tools

Hi all, Since some time, the `qmlscene` command has been available for debugging QML applications: [estan@pyret ~]$ qmlscene --help Usage: qmlscene [options] Options: --maximized .. Run maximized --fullscreen . Run fullscreen --transparent

Re: [Interest] Migrating QWeakPointer to Qt5

> > Well you can't have implicit upcasting ... > That's a typo, I meant downcasting. > ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Migrating QWeakPointer to Qt5

On Fri, May 6, 2016 at 8:35 AM, Tom Isaacson wrote: > I'm moving some Qt4.8.2 code which uses QWeakPointer to Qt5.6. > Simplifying a lot it looks like this: > [snippet ..] > but when I compile under Visual Studio 2013 I get this error: > error C2664:

Re: [Interest] Enabling NEON on a Qt Android app

Thanks for your insight Thiago. Regards, Nuno > On 06 May 2016, at 08:38, Thiago Macieira wrote: > > On sexta-feira, 6 de maio de 2016 07:58:30 PDT Nuno Santos wrote: >> What are the necessary steps in order to enable NEON on a Arm processor that >> supports it? >

Re: [Interest] Enabling NEON on a Qt Android app

On sexta-feira, 6 de maio de 2016 07:58:30 PDT Nuno Santos wrote: > What are the necessary steps in order to enable NEON on a Arm processor that > supports it? Compile a plugin for Neon and a plugin for non-Neon. At runtime, determine which one to load, then call functions on it. Do not try to

Re: [Interest] Enabling NEON on a Qt Android app

Am 06.05.16 um 08:58 schrieb Nuno Santos: > Hi, > > > Also, in the following article: https://www.kdab.com/qt-android-episode-4/ > > *Advantages:* > > * Using Ministro, the user needs to download the Qt > libs *ONLY* once. If the user downloads another Qt application, it > will use

[Interest] Enabling NEON on a Qt Android app

Hi, What are the necessary steps in order to enable NEON on a Arm processor that supports it? I’m wondering if I need to enable things like -mfpu=neon on GCC flags or if I just simply need to do things like this: http://developer.android.com/ndk/guides/cpu-arm-neon.html

Re: [Interest] How to set Android Version and App Name

Where is your AndroidManifest.xml? That’s the place for those kind of things. > On 06 May 2016, at 06:32, ekke wrote: > > Am 05.05.16 um 21:47 schrieb NoRulez: >> Hello, >> >> I tried to deploy my first example app to my device. >> I noticed that the app name is always

Re: [Interest] Migrating QWeakPointer to Qt5

Den 06-05-2016 kl. 07:35 skrev Tom Isaacson: I'm moving some Qt4.8.2 code which uses QWeakPointer to Qt5.6. Simplifying a lot it looks like this: class MySettings : public QObject { Q_OBJECT } class MyClass : public QObject { Q_OBJECT private: QWeakPointer m_xSettings; }