[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 QtApp and the target is a

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; } MyClass

[Interest] Migrating QWeakPointer to Qt5

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; } MyClass::MyClass(MySettings* pSettings, QObject* pPare

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

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 QtApp and the target is always > android-23. > I tried to set the version with "--android platform android-21" but it > doesn't work either. > > Can anyb

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

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 even a single 'new' or > 'delete' a

[Interest] [QtWayland] App window now showing in Weston

Hello, I have successfully built a yocto image that includes wayland and is using the reference weston compositor on my target device. I have also successfully ran Qt5_CinematicExperience as well as other example Qt apps within weston. My problem occurs when I run the same example apps or even a

Re: [Interest] Qt interfacing to Android native UI ?

I emailed th author of react-qml, he's just fiddling with it, it's not s serious project.   Dang, why can't we (Qt) get buy-in like that?     Sent: Thursday, May 05, 2016 at 3:58 PM From: "Edward Sutton" To: "Jason H" Cc: "Robert Iakobashvili" , "interest@qt-project.org" Subject: Re: [Inte

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

The name and version in the package/AndroidManifest.xml are the correct ones > Am 05.05.2016 um 21:50 schrieb Jason H : > > >> I tried to deploy my first example app to my device. >> I noticed that the app name is always QtApp and the target is always >> android-23. >> I tried to set the versio

Re: [Interest] Qt interfacing to Android native UI ?

I have not used the project. My guess one motivating goal would be to reuse the many react-native modules that support both Android and iOS ( or one OS or the other ). Another goal would be to access real native UI components and native API’s. While QML looks native-like, for Android or iOS ap

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

> I tried to deploy my first example app to my device. > I noticed that the app name is always QtApp and the target is always > android-23. > I tried to set the version with "--android platform android-21" but it > doesn't work either. > > Can anybody give me a hint to set those options? Edit

[Interest] How to set Android Version and App Name

Hello, I tried to deploy my first example app to my device. I noticed that the app name is always QtApp and the target is always android-23. I tried to set the version with "--android platform android-21" but it doesn't work either. Can anybody give me a hint to set those options? Thanks __

[Interest] [QML][C++][Context] change property into context

Hi, I would like to known if there's a way to efficiently change the value into a context and emit changed() signal without having setContextProperty() forcing whole context revaluation? Let say I have a special Repeater alike component that create and maintain expensive Object that add index,valu

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

On 05/05/16 14:52, Giuseppe D'Angelo wrote: On Thu, May 5, 2016 at 1:22 PM, Nikos Chantziaras wrote: That doesn't do anything useful. I think you're missing the point here. Did you try the earlier suggestion of using a QScopedPointer with a custom deleter that holds a QPointer to the instance

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

Well, lots of strong opinions on this one :-) Anyway, to each his own. Of course I know that C++ isn't Java, nor would I want it to be. But just because C++ isn't Java doesn't mean I am in favor of poor exception safety or lots of manual checking and cleaning up. Yes, we still have to do these

Re: [Interest] Qt interfacing to Android native UI ?

What is the motivation for such a project?   Sent: Thursday, May 05, 2016 at 10:31 AM From: "Edward Sutton" To: "Robert Iakobashvili" Cc: "interest@qt-project.org" Subject: Re: [Interest] Qt interfacing to Android native UI ? An interesting project:   https://github.com/grassator/react-qml

Re: [Interest] Qt interfacing to Android native UI ?

An interesting project: https://github.com/grassator/react-qml react-qml is a bridge library that allows to use React.js with QML. Example Usage of ReactQml is pretty straightforward — the only difference from web version is that you need to pass id of the qml item to React.render instead of D

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

> > Well, that's not quite true of course. If you want to show a dialog > created on the stack, you will have to use it's exec() method. That spins > an event loop, and that means that a lot can happen in the mean time. It > can vary from an incoming DBUS messages causing the application to > termi

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

Op 05/05/2016 om 13:20 schreef Nye: On Thu, May 5, 2016 at 4:22 AM, Nikos Chantziaras > wrote: On 05/05/16 01:44, Nye wrote: No one said it does. Perhaps I'm misunderstanding, are you searching for a silver bullet for memory management?

Re: [Interest] using cmake to build Qt projects.

On Thu, May 05, 2016 at 07:54:53AM -0400, william.croc...@analog.com wrote: > > > > >>I have never been able to get creator to work. The 5 series won't even run > >>under my versions of VNC and the NX virtual desktops. This apparently due > >>to a > >>dependency on new visual fluff. > > > >Qt Q

Re: [Interest] using cmake to build Qt projects.

I have never been able to get creator to work. The 5 series won't even run under my versions of VNC and the NX virtual desktops. This apparently due to a dependency on new visual fluff. Qt Quick doesn't indeed not work well over VNC. The common workaround is to not load Quick based plugins

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

On Thu, May 5, 2016 at 1:22 PM, Nikos Chantziaras wrote: > That doesn't do anything useful. I think you're missing the point here. Did you try the earlier suggestion of using a QScopedPointer with a custom deleter that holds a QPointer to the instance and deletes it only if it has not been delete

Re: [Interest] using cmake to build Qt projects.

On Thu, May 05, 2016 at 06:53:54AM -0400, Bill Crocker wrote: > >>I am trying to port my Qt project to a cmake based build so I can use CLion > >>for debugging. > > > >Why is CLion preferable for you to do Qt debugging, opposed to e.g. using Qt > >Creator? > > > > Because CLion works out of the bo

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

On 05/05/16 14:24, André Pönitz wrote: On Thu, May 05, 2016 at 04:24:48AM +0300, Nikos Chantziaras wrote: Well, basically what I want is not having even a single 'new' or 'delete' anywhere in my code. I already achieved that with all my non-Qt projects. remedyforirrationalfear.h: namespace

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

On Thu, May 5, 2016 at 4:22 AM, Nikos Chantziaras wrote: > > On 05/05/16 01:44, Nye wrote: > >> No one said it does. Perhaps I'm misunderstanding, are you searching for >> a silver bullet for memory management? >> > > I already found it. Question is how to make Qt work with it :-) > > You most cer

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

On Thu, May 05, 2016 at 04:24:48AM +0300, Nikos Chantziaras wrote: > On 04/05/16 21:35, Thiago Macieira wrote: > >On quarta-feira, 4 de maio de 2016 20:56:52 PDT Nikos Chantziaras wrote: > >> From what I can tell, QPointer does not delete the object, so that's a > >>no go. > >> > >>Putting the obj

Re: [Interest] using cmake to build Qt projects.

On 05/05/2016 06:08 AM, Jean-Michaël Celerier wrote: I am almost there, but when it links there are symbols undefined. From my experience the symbols I am seeing are typical of missing moc files. You should still post your error messages I think, maybe it's some library that Qt links automati

Re: [Interest] using cmake to build Qt projects.

05.05.2016, 13:54, "Bill Crocker" : >>>  I am trying to port my Qt project to a cmake based build so >>>  I can use CLion for debugging. >> >>  Why is CLion preferable for you to do Qt debugging, opposed to >>  e.g. using Qt Creator? > > Because CLion works out of the box and I am assuming > that

Re: [Interest] using cmake to build Qt projects.

I am trying to port my Qt project to a cmake based build so I can use CLion for debugging. Why is CLion preferable for you to do Qt debugging, opposed to e.g. using Qt Creator? Because CLion works out of the box and I am assuming that I can use it to debug my app once I get it to build wit

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

I completely disagree with you :-) I hope you're not the type of guy who writes code like this: something; if (!something) { delete; return; } something else; if (!something else) { delete; return; } try { do stuff; } catch (...) { delete;

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

05.05.2016, 13:16, "Jean-Michaël Celerier" : > On Thu, May 5, 2016 at 3:24 AM, Nikos Chantziaras wrote: >> By now, I consider application-level code that uses 'new' or 'delete' as >> bogus and in need of fixing. > This line of thought doesn't work at all with Qt. It's just how it is done. > If

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

On Thu, May 5, 2016 at 3:24 AM, Nikos Chantziaras wrote: > > By now, I consider application-level code that uses 'new' or 'delete' as > bogus and in need of fixing. This line of thought doesn't work at all with Qt. It's just how it is done . If you are in such

Re: [Interest] using cmake to build Qt projects.

> I am almost there, but when it links there are symbols undefined. > From my experience the symbols I am seeing are typical of missing moc files. You should still post your error messages I think, maybe it's some library that Qt links automatically but that you have to link by hand with CMake ?

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

Den 04-05-2016 kl. 16:48 skrev Nikos Chantziaras: I've been removing every trance of 'new' and 'delete' from my code and switching to something like: auto obj = std::make_unique(ctor args); (Or std::make_shared, depending on the situation.) But for QObjects with a parent, that can go horribl