[Interest] Compiling Qt from source 64 bit on Windows

[Nuno Santos]

Hi,

Is there any special difference in compiling Qt from source in Windows 
in 64 bit?


This is my configure linke
configure -prefix c:\qt\5.6\msvc2013_opengl_5_6_rc_64_static -commercial 
-debug-and-release -static -nomake examples -nomake tools -nomake tests 
-opengl dynamic -skip multimedia -openssl-linked -I 
c:\openssl-lib\include -L c:\openssl-lib\lib64 
OPENSSL_LIBS_DEBUG="ssleay32MTd.lib libeay32MTd.lib" 
OPENSSL_LIBS_RELEASE="ssleay32MT.lib libeay32MT.lib"


Qt compiled just fine.

The projecto also compiles fine until it gets to the linking phase:

libcpmt.lib(locale.obj) : error LNK2001: unresolved external symbol 
_purecall


libcpmt.lib(wlocale.obj) : error LNK2001: unresolved external symbol 
_purecall


libcpmt.lib(xlocale.obj) : error LNK2001: unresolved external symbol 
_purecall


libcpmt.lib(xdateord.obj) : error LNK2001: unresolved external symbol 
_purecall


libcpmt.lib(locale0.obj) : error LNK2001: unresolved external symbol 
_purecall


libcpmt.lib(ios.obj) : error LNK2001: unresolved external symbol _purecall

libcpmt.lib(cerr.obj) : error LNK2001: unresolved external symbol _purecall

libcpmt.lib(iosptrs.obj) : error LNK2001: unresolved external symbol 
_purecall


Qt5Core.lib(qanimationgroup.obj) : error LNK2001: unresolved external 
symbol _purecall


Qt5Core.lib(qfilesystemwatcher_polling.obj) : error LNK2001: unresolved 
external symbol _purecall


libcpmt.lib(xthrow.obj) : error LNK2019: unresolved external symbol 
_purecall referenced in function "public: __cdecl 
std::basic_string,class 
std::allocator >::basic_stringstd::char_traits,class std::allocator >(char const *)" 
(??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAA@PEBD@Z)


libcpmt.lib(syserror.obj) : error LNK2001: unresolved external symbol 
_purecall


Qt5Core.lib(qabstractfileengine.obj) : error LNK2001: unresolved 
external symbol _purecall


Qt5Core.lib(qmimeprovider.obj) : error LNK2001: unresolved external 
symbol _purecall


Qt5Core.lib(qabstractstate.obj) : error LNK2001: unresolved external 
symbol _purecall


Qt5Core.lib(qabstracttransition.obj) : error LNK2001: unresolved 
external symbol _purecall



What am I missing?


Thanks,

Regards,


Nuno


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiling Qt from source 64 bit on Windows

[Nuno Santos]

Thiago,

Thanks for the clarification. I will investigate further.

Thanks,

Regards,

Nuno

> On 14 Mar 2016, at 20:45, Thiago Macieira  wrote:
> 
> On segunda-feira, 14 de março de 2016 18:11:46 PDT Nuno Santos wrote:
>> Hi,
>> 
>> Is there any special difference in compiling Qt from source in Windows
>> in 64 bit?
> 
> No. It's been working just fine for the last 3 or 4 years for me.
> 
>> libcpmt.lib(locale.obj) : error LNK2001: unresolved external symbol
>> _purecall
> 
>> libcpmt.lib(xthrow.obj) : error LNK2019: unresolved external symbol
>> _purecall referenced in function "public: __cdecl
>> std::basic_string,class
>> std::allocator >::basic_string> std::char_traits,class std::allocator >(char const *)"
>> (??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAA@PEBD@Z
>> )
> 
> Looks like your environment wasn't set up properly. This library 
> (libcpmt.lib) 
> is requiring functions that aren't present.
> 
> I've never heard of libcpmt, so I have no idea what it's supposed to be doing 
> or how you got linking to it. My guess is that the OpenSSL libraries are 
> causing it, somehow. I suggest you go back to dynamic loading of the OpenSSL 
> libraries, instead of -openssl-linked.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiling Qt from source 64 bit on Windows

[Nuno Santos]

Gunnar,

Thanks for your keen eye. 

So, maybe libcpmt.lib is not being specified to the linker by default? Need to 
check tomorrow at the office.

Regards,

Nuno
 
> On 14 Mar 2016, at 23:04, Gunnar Roth  wrote:
> 
> Hi Thiago, you probably missed the -static configure option, so Nunos is 
> making a static qt build. He really should mention that in the subject line.
> Ordinary 64 bit windows qt 5.6rc builds worked for me without a problem with 
> vs2012 an 2015.
> 
> libcpmt.lib is the c++ multithread static lib of visual studio. 
> 
> 
> 
> Regards,
> Gunnar Roth
> 
> 
>> Am 14.03.2016 um 21:45 schrieb Thiago Macieira :
>> 
>> On segunda-feira, 14 de março de 2016 18:11:46 PDT Nuno Santos wrote:
>>> Hi,
>>> 
>>> Is there any special difference in compiling Qt from source in Windows
>>> in 64 bit?
>> 
>> No. It's been working just fine for the last 3 or 4 years for me.
>> 
>>> libcpmt.lib(locale.obj) : error LNK2001: unresolved external symbol
>>> _purecall
>> 
>>> libcpmt.lib(xthrow.obj) : error LNK2019: unresolved external symbol
>>> _purecall referenced in function "public: __cdecl
>>> std::basic_string,class
>>> std::allocator >::basic_string>> std::char_traits,class std::allocator >(char const *)"
>>> (??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAA@PEBD@Z
>>> )
>> 
>> Looks like your environment wasn't set up properly. This library 
>> (libcpmt.lib) 
>> is requiring functions that aren't present.
>> 
>> I've never heard of libcpmt, so I have no idea what it's supposed to be 
>> doing 
>> or how you got linking to it. My guess is that the OpenSSL libraries are 
>> causing it, somehow. I suggest you go back to dynamic loading of the OpenSSL 
>> libraries, instead of -openssl-linked.
>> 
>> -- 
>> Thiago Macieira - thiago.macieira (AT) intel.com
>> Software Architect - Intel Open Source Technology Center
>> 
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiling Qt from source 64 bit on Windows

[Nuno Santos]

Kai,

To whom should I pass the -static-runtime option? To Qt configure or to Openssl 
libs? 

When I compile Qt from source I modify msvc-desktop.conf to use MT instead of 
MD which comes by default.

The Openssl libs are pre compiled and they provide binaries for both 32 and 64 
bit.

With a 32 bit build of Qt everything is alright. 

Regards,

Nuno

> On 15 Mar 2016, at 07:52, Koehne Kai  wrote:
> 
> 
> 
>> -Original Message-
>> From: Interest [mailto:interest-
>> bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of
>> Nuno Santos
>> Sent: Monday, March 14, 2016 7:12 PM
>> To: interest@qt-project.org
>> Subject: [Interest] Compiling Qt from source 64 bit on Windows
>> 
>> Hi,
>> 
>> Is there any special difference in compiling Qt from source in Windows in 64
>> bit?
>> 
>> This is my configure linke
>> configure -prefix c:\qt\5.6\msvc2013_opengl_5_6_rc_64_static -
>> commercial -debug-and-release -static -nomake examples -nomake tools -
>> nomake tests -opengl dynamic -skip multimedia -openssl-linked -I
>> c:\openssl-lib\include -L c:\openssl-lib\lib64
>> OPENSSL_LIBS_DEBUG="ssleay32MTd.lib libeay32MTd.lib"
>> OPENSSL_LIBS_RELEASE="ssleay32MT.lib libeay32MT.lib"
> 
> You're linking against the MT version of openssl libs, but do not pass 
> '-static-runtime' as configure argument - so the Qt libs will link against 
> the MD versions of the runtime libs. I wouldn't be surprised if this causes 
> linking issues like yours.
> 
> Regards
> 
> Kai 
> 

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiling Qt from source 64 bit on Windows

[Nuno Santos]

Ok... something weird happened. Today, it compiles just fine!

There was probably some configuration conflict around. With a fresh 
start and a fresh build it just worked!


Em 15/03/2016 15:35, Thiago Macieira escreveu:

On terça-feira, 15 de março de 2016 08:30:33 PDT Koehne Kai wrote:

The Openssl libs are pre compiled and they provide binaries for both 32
and
64 bit.

I never tried building Qt 64 bit with openssl statically. So I'm afraid I've
nothing to add.

Suggestion: give up, use dynamic runtime and dynamically load the OpenSSL
DLLs.



___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] How to properly delete qApp?

[Nuno Santos]

Hi,

My application is targeted to run as a software plugin inside another 
third party application. When a instance of my plugin is instanciated I 
check if qApp exists. If so, I will use that pointer, otherwise I will 
reuse the pointer. I also increment a counter to know how many instances 
of my plugin are active. When the plugin is deleted I check the counter. 
If it gets to zero I will delete qApp.


The problem is that  I'm having a different behaviour across platforms. 
On OSX I don't even need to delete qApp, everything works alright. On 
Windows, if I don't delete the qApp, the host hangs, seems like a dead 
lock, so I need to force delete it and this is what I am doing:


_app->processEvents(QEventLoop::AllEvents, 1000);
_app->quit();
delete _app;
_app = 0;

This way, the host is able to close and exit but the return code is not 
zero, it is basically crashing but no error window pops up. If I don't 
call delete _app, the host hangs and it is not able to exit.


It is important to refer that I'm using a static and namespaced build of 
Qt and that I'm calling a new Windows thread to call qApp exec.


The thread body has two modes. Why? Because when I call _app->exec() it 
immediatelly returns saying that it must be called from main thread, 
however things continue to happen, Qml works, QObjects works, apparently 
at least! The approach works also, not apparent problems, but the thread 
doesn't return.


#ifdef Q_OS_WIN
unsigned int id;
Qt::HANDLE h = (Qt::HANDLE) _beginthreadex(NULL, 0, threadInit, this, 0, 
&id);

#endif

#ifdef Q_OS_WIN
unsigned int __stdcall threadInit(void *args)
{
qDebug() << "--Qt Init Thread";
IVst *plugin = (IVst*)args;

#if 1
while(plugin->_running)
plugin->_app->processEvents();
#else
plugin->_app->exec();
#endif

qDebug() << "--Thread done";
return 0;
}

So far on OSX I was not even deleting the app and it worked without issues.

Does anyone has a clue of what is going on?

Thanks,

Regards,

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to properly delete qApp?

[Nuno Santos]

Nikos,

Thanks for your reply. 

The problems is that host application hangs forever if I don’t delete it and 
crashes if I delete it. I’m in a kind of dead end.

Any ideas?

Thanks

Nuno

> On 16 Mar 2016, at 14:07, Nikos Chantziaras  wrote:
> 
> On 16/03/16 14:01, Till Oliver Knoll wrote:
>> I don't think you're supposed to delete qApp
> 
> Actually you do need to delete it. Most people don't because after 
> qApp->exec() returns, the program ends anyway. But if you want to have 0 
> leaks, you need to delete your QApplication instance.
> 
> Usually you don't delete qApp directly, but just your instance, but that's 
> the same thing, really:
> 
>  int main(int argc, char** argv)
>  {
>  QApplication app = new QApplication(/* ... */);
>  app->exec();
>  delete app;
>  // or:
>  // delete qApp;
>  // which does the same thing.
>  }
> 
> In normal applications, like the above, deleting it is redundant. You're 
> exiting the process, so the environment is going to clean your memory anyway. 
> It's still a memory leak, if you're pedantic about it.
> 
> If you're using QApplication in a plugin, deleting qApp is actually 
> mandatory, otherwise you're leaking the qApp instance when the plugin 
> unloads; no one else is going to delete it for you.
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] How to change compiler flags of Android compilations?

[Nuno Santos]

Hi,

I was trying to set new compiler flags for Android compilation but they don’t 
seem to be reflect during the compilation.

I added:

QMAKE_CXXFLAGS_RELEASE += -mfloat-abi=softfp -mfpu=neon -O3 -DHAVE_NEON=1

But during the compilation there was this:

arm-linux-androideabi-g++ -c -Wno-psabi -march=armv7-a -mfloat-abi=softfp 
-mfpu=vfp -ffunction-sections -funwind-tables -fstack-protector 
-fno-short-enums -DANDROID -Wa,--noexecstack -fno-builtin-memmove -std=c++11 -g 
-g -marm -O0 -fno-omit-frame-pointer -Wall -Wno-psabi -W -D_REENTRANT -fPIC

What am I missing?

Thanks,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Moving from Parse

[Nuno Santos]

Hi,

Since Parse announced it’s shutdown I have been looking for a pain free and 
scaling solution.

The most difficult problem is to find a baas/daas that has a C++ client lib. 
All platforms out there only provide REST API as an alternative to iOS and 
Android libs.

Question: what are you people using for baas/daas of your Qt based 
applications? 

Thanks,

Regards

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Moving from Parse

[Nuno Santos]

This seems nice! Let me investigate.

Thanks Ben

> On 28 Mar 2016, at 20:00, Ben Lau  wrote:
> 
> 
> Amazon (Mobile Hub , DynamoDB, Lambda, API Gateway, Cognito) can be an 
> alternative solution to Parse. And Amazon have C++ SDK available now.
> 
> Introducing the AWS SDK for C++ | AWS Blog 
> <https://aws.amazon.com/blogs/aws/introducing-the-aws-sdk-for-c/>
> 
> 
> On 29 March 2016 at 02:12, Nuno Santos  <mailto:nunosan...@imaginando.pt>> wrote:
> Hi,
> 
> Since Parse announced it’s shutdown I have been looking for a pain free and 
> scaling solution.
> 
> The most difficult problem is to find a baas/daas that has a C++ client lib. 
> All platforms out there only provide REST API as an alternative to iOS and 
> Android libs.
> 
> Question: what are you people using for baas/daas of your Qt based 
> applications? 
> 
> Thanks,
> 
> Regards
> 
> Nuno
> 
> ___
> Interest mailing list
> Interest@qt-project.org <mailto:Interest@qt-project.org>
> http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
> 
> 

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Moving from Parse

[Nuno Santos]

Jason,

What I really want to avoid is to manage my own servers. That takes me a lot of 
time. I want to focus myself on doing development and not server management. 

I also want that basic stuff such as users registration, registration emails, 
etc to be provided by the backend already, otherwise I would need to invest 
time in making my own.

Regards,

Nuno

> On 28 Mar 2016, at 20:55, Jason H  wrote:
> 
> I'm not sure I see your problem. You're using Qt, you can use QJson* classes, 
> QNAM, and interop with these without issue.
> I believe you can just use MongoDB, as a JS object store. I've not done that 
> though, but that seems the path of most resistence. I personally just roll my 
> own using Node/Express/Postgres (since the newer Prostgres has JSONB datatype)
>  
> Sent: Monday, March 28, 2016 at 2:12 PM
> From: "Nuno Santos" 
> To: interest 
> Subject: [Interest] Moving from Parse
> Hi,
>  
> Since Parse announced it’s shutdown I have been looking for a pain free and 
> scaling solution.
>  
> The most difficult problem is to find a baas/daas that has a C++ client lib. 
> All platforms out there only provide REST API as an alternative to iOS and 
> Android libs.
>  
> Question: what are you people using for baas/daas of your Qt based 
> applications? 
>  
> Thanks,
>  
> Regards
>  
> Nuno
> ___ Interest mailing list 
> Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Moving from Parse

[Nuno Santos]

Ilya,

Yes, there are a lot of Parse Server hosting options now. Which provider have 
you chosen? Or are you hosting your own server?

Thanks,

Nuno

> On 29 Mar 2016, at 09:16, Ilya Diallo  wrote:
> 
> Hi,
> 
> I use Parse Server <https://github.com/ParsePlatform/parse-server>, and this 
> C++/QML client lib <https://github.com/a-team-fr/QtQML-BaaS>.
> There's tons of Parse Server hosting options available, and the Qt client lib 
>  has served me well for getting data from the (also retiring) Qt Cloud 
> Services db to Parse Server. It's in early stages but mostly working, 
> contributions are welcome.
> 
> Cheers,
> 
> Ilya.
> 
> 2016-03-28 23:03 GMT+02:00 Nuno Santos  <mailto:nunosan...@imaginando.pt>>:
> Jason,
> 
> What I really want to avoid is to manage my own servers. That takes me a lot 
> of time. I want to focus myself on doing development and not server 
> management. 
> 
> I also want that basic stuff such as users registration, registration emails, 
> etc to be provided by the backend already, otherwise I would need to invest 
> time in making my own.
> 
> Regards,
> 
> Nuno
> 
>> On 28 Mar 2016, at 20:55, Jason H mailto:jh...@gmx.com>> 
>> wrote:
>> 
>> I'm not sure I see your problem. You're using Qt, you can use QJson* 
>> classes, QNAM, and interop with these without issue.
>> I believe you can just use MongoDB, as a JS object store. I've not done that 
>> though, but that seems the path of most resistence. I personally just roll 
>> my own using Node/Express/Postgres (since the newer Prostgres has JSONB 
>> datatype)
>>  
>> Sent: Monday, March 28, 2016 at 2:12 PM
>> From: "Nuno Santos" > <mailto:nunosan...@imaginando.pt>>
>> To: interest mailto:interest@qt-project.org>>
>> Subject: [Interest] Moving from Parse
>> Hi,
>>  
>> Since Parse announced it’s shutdown I have been looking for a pain free and 
>> scaling solution.
>>  
>> The most difficult problem is to find a baas/daas that has a C++ client lib. 
>> All platforms out there only provide REST API as an alternative to iOS and 
>> Android libs.
>>  
>> Question: what are you people using for baas/daas of your Qt based 
>> applications? 
>>  
>> Thanks,
>>  
>> Regards
>>  
>> Nuno
>> ___ Interest mailing list 
>> Interest@qt-project.org <mailto:Interest@qt-project.org> 
>> http://lists.qt-project.org/mailman/listinfo/interest 
>> <http://lists.qt-project.org/mailman/listinfo/interest>
> 
> ___
> Interest mailing list
> Interest@qt-project.org <mailto:Interest@qt-project.org>
> http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
> 
> 

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] iPad Pro display support?

[Nuno Santos]

Hi,

I’m wondering if there is any special care I should take for iPad Pro.

I have a user saying that the graphics is not crystal clear on it’s iPad Pro.

The graphics are mostly based on Qml Text and Canvas elements.

Thanks,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] iPad Pro display support?

[Nuno Santos]

Haven’t tried it with Qt 5.6 yet. Will try! 

Any special flags that need to be enabled?

> On 29 Mar 2016, at 13:34, m...@rpzdesign.com wrote:
> 
> How does it look on Qt 5.6?
> 
> I had similar text fuzziness comments from IOS on Qt.5.5.
> 
> md
> 
> On 3/29/2016 4:52 AM, Nuno Santos wrote:
>> Hi,
>> 
>> I’m wondering if there is any special care I should take for iPad Pro.
>> 
>> I have a user saying that the graphics is not crystal clear on it’s iPad Pro.
>> 
>> The graphics are mostly based on Qml Text and Canvas elements.
>> 
>> Thanks,
>> 
>> Nuno
>> 
>> 
>> ___
>> Interest mailing list
>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>> http://lists.qt-project.org/mailman/listinfo/interest 
>> <http://lists.qt-project.org/mailman/listinfo/interest>
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] doubleClicked on MultiPointTouchArea

[Nuno Santos]

Hi,

Has anyone here missed the doubleClicked event on MultiPointTouchArea? 

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] QSGRenderThread crashed: libGPUSupportMercury.dylib`gpus_ReturnGuiltyForHardwareRestart:

[Nuno Santos]

Hi,

I have just discovered something that might be an unpredicted bug in Qt iOS. I 
have an app which makes uses of inter app audio. Therefore, this app should be 
able to jump and forth from host to app and vice versa. It should be also able 
to make the jump with the lowest overhead as possible to avoid audio glitches. 
Right now, what is concerning me the most is that after a couple of jumps, 
which sometimes can be more or less, the app crashes. I was able to crash it 
while running the debugger and this is what appeared in the stack trace:

libGPUSupportMercury.dylib`gpus_ReturnGuiltyForHardwareRestart:
  0x18ef91f1c <+0>:  orrw8, wzr, #0x1
  0x18ef91f20 <+4>:  movz   w9, #0xdead, lsl #16
  0x18ef91f24 <+8>:  movk   w9, #0xbeef
->  0x18ef91f28 <+12>: strw9, [x8]
  0x18ef91f2c <+16>: ret  

The crashes thread was the QSGRenderThread. This seems to be a critical bug for 
apps that need to behave this way, which I consider that is any professional 
audio app nowadays. This happens on both Qt 5.5.1 and 5.6

Before filling a bug report I would like to share this info with the list and 
have some insights about it.

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] QSGRenderThread crashed: libGPUSupportMercury.dylib`gpus_ReturnGuiltyForHardwareRestart:

[Nuno Santos]

Hi,

I have just discovered something that might be an unpredicted bug in Qt iOS. I 
have an app which makes uses of inter app audio. Therefore, this app should be 
able to jump and forth from host to app and vice versa. It should be also able 
to make the jump with the lowest overhead as possible to avoid audio glitches. 
Right now, what is concerning me the most is that after a couple of jumps, 
which sometimes can be more or less, the app crashes. I was able to crash it 
while running the debugger and this is what appeared in the stack trace:

libGPUSupportMercury.dylib`gpus_ReturnGuiltyForHardwareRestart:
0x18ef91f1c <+0>:  orrw8, wzr, #0x1
0x18ef91f20 <+4>:  movz   w9, #0xdead, lsl #16
0x18ef91f24 <+8>:  movk   w9, #0xbeef
->  0x18ef91f28 <+12>: strw9, [x8]
0x18ef91f2c <+16>: ret  

The crashes thread was the QSGRenderThread. This seems to be a critical bug for 
apps that need to behave this way, which I consider that is any professional 
audio app nowadays. This happens on both Qt 5.5.1 and 5.6

Before filling a bug report I would like to share this info with the list and 
have some insights about it.

Also, when the app starts I have some UIKit related warning. Not sure if they 
related with the crash. Since I don’t write UI code for cocoa anymore since 
using Qt/Qml, I deduce that this warnings come from Qt UIKit layer.

2016-04-05 00:17:37.131 DRC[307:14615] Unable to simultaneously satisfy 
constraints.
Probably at least one of the constraints in the following list is one 
you don't want. 
Try this: 
(1) look at each constraint and try to figure out which you 
don't expect; 
(2) find the code that added the unwanted constraint or 
constraints and fix it. 
(
"",
""
)

Will attempt to recover by breaking constraint 


Best regards,

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] QSGRenderThread crashed: libGPUSupportMercury.dylib`gpus_ReturnGuiltyForHardwareRestart:

[Nuno Santos]

Hi,

I have just discovered something that might be an unpredicted bug in Qt iOS. I 
have an app which makes uses of inter app audio. Therefore, this app should be 
able to jump and forth from host to app and vice versa. It should be also able 
to make the jump with the lowest overhead as possible to avoid audio glitches. 
Right now, what is concerning me the most is that after a couple of jumps, 
which sometimes can be more or less, the app crashes. I was able to crash it 
while running the debugger and this is what appeared in the stack trace:

libGPUSupportMercury.dylib`gpus_ReturnGuiltyForHardwareRestart:
   0x18ef91f1c <+0>:  orrw8, wzr, #0x1
   0x18ef91f20 <+4>:  movz   w9, #0xdead, lsl #16
   0x18ef91f24 <+8>:  movk   w9, #0xbeef
->  0x18ef91f28 <+12>: strw9, [x8]
   0x18ef91f2c <+16>: ret  

The crashes thread was the QSGRenderThread. This seems to be a critical bug for 
apps that need to behave this way, which I consider that is any professional 
audio app nowadays. This happens on both Qt 5.5.1 and 5.6

Before filling a bug report I would like to share this info with the list and 
have some insights about it.

Also, when the app starts I have some UIKit related warning. Not sure if they 
related with the crash. Since I don’t write UI code for cocoa anymore since 
using Qt/Qml, I deduce that this warnings come from Qt UIKit layer.

2016-04-05 00:17:37.131 DRC[307:14615] Unable to simultaneously satisfy 
constraints.
Probably at least one of the constraints in the following list is one 
you don't want. 
Try this: 
(1) look at each constraint and try to figure out which you 
don't expect; 
(2) find the code that added the unwanted constraint or 
constraints and fix it. 
(
   "",
   ""
)

Will attempt to recover by breaking constraint 


Best regards,

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] CLion to replace QtCreator?

[Nuno Santos]

> On 05 Apr 2016, at 14:19, NoMercy  wrote:
> 
> people are practically begging jetbrains to save themselves from QtCreator 
> (no offense intended but this is the case for many people)

Sorry to interfere here but I couldn’t read this without sharing my thoughts. 
Qt Creator is simply the most straightforward IDE around.

All IDE based in Java simply suck because they are all slow like a turtle. I 
personally hate any kind of Java based software because of the performance 
impact. 

It is also a paradox a JET brain software using Java to support it. A JET brain 
cannot wait for Java to render. :)


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Migration path from QGraphicsScene to QtQuick2

[Nuno Santos]

Jean,

I think you can extend QQuickItem and override the paint method and keep using 
the exact same code for painting your items.

Nuno

> On 15 Apr 2016, at 11:05, Jean-Michaël Celerier 
>  wrote:
> 
> Inspired by Ingo Schiller's problem, I am wondering if there is a "common" or 
> known pattern to enable migration from QPainter / QGraphicsItem objects to 
> QtQuick 2 ?
> 
> I have a big scene with items all drawn by hand : 
> https://github.com/OSSIA/i-score/blob/master/Documentation/iscore.png?raw=true
>  
> 
> 
> Should I reimplement QSGNode or stuff like this ? Will I have better 
> performance ? Are all nifty features (rubber band, contxt menu, etc...) 
> supported in QtQuick or does stuff need redoing ?
> 
> 
> Best,
> Jean-Michaël Celerier
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Deploying app with Qt Quick 2D Renderer failing

[Nuno Santos]

Hi,

I’m trying to deploy an app with Qt Quick 2D Renderer enabled. For that I have 
used qputenv to set QMLSCENE_DEVICE=softwarecontext

When launching the app thru Qt Creator I can see the output much better than I 
usually do with OpenGL.

However, after calling macdeployqt over it and running it normally, what I see 
is the usual OpenGL render result look.

I have tried to launch the app thru the command line and call export 
QMLSCENE_DEVICE=softwarecontext before. That result! 

Maybe macdeployqt is not installing a required module. What should I look for? 

Does anyone has a clue of what might be causing this? 

By the way, I have two errors while installing Qt Quick 2D Renderer module thru 
the Maintenance Tool:




Thanks,

Regards,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How add an Android package to qmake project file?

[Nuno Santos]

Eduard,

Open projects tab in Qt Creator. Click the create templates button. Check the 
use grade checkbox. You can then use the maven repositories as follow:

allprojects {
repositories {
jcenter()
mavenCentral()
maven { url 'http://maven.localytics.com/public' }
maven { url 
'https://github.com/kshoji/USB-MIDI-Driver/raw/master/MIDIDriver/snapshots' }
}
}

apply plugin: 'com.android.application'

dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.facebook.android:facebook-android-sdk:4.6.0'
compile 'com.localytics.android:library:3.6+'
compile 'jp.kshoji:midi-driver:0.1.4:@aar'
}


Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

> On 21 Apr 2016, at 17:34, Edward Sutton  wrote:
> 
>> 
>> 
>> >It's not done in the pro, it's done android-side in your grade or ant. Just 
>> >do it as if it were an proper SDK Android app.
> 
> I do not know how that is done.  I build all platforms Android, iOS, windows, 
> OS X using the qmake pro file.
> 
> I created a /libs subfolder under ANDROID_PACKAGE_SOURCE_DIR and copied the 
> android-support-v4.jar file.
> 
> This seems to work but expect it may cause confusion when Android 7.0 is 
> released and something breaks again.
> 
> -Ed
> 
> 
>>  
>> Sent: Thursday, April 21, 2016 at 10:35 AM
>> From: "Edward Sutton" > <mailto:edward.sut...@subsite.com>>
>> To: "Qt Interest" mailto:interest@qt-project.org>>
>> Subject: [Interest] How add an Android package to qmake project file?
>> I need to add package android.support.v4.content.ContextCompat
>>  
>> so I can fix Android 6.0 from breaking my Qt Android app.
>>  
>> Can this be done in the quake project file?
>>  
>>  
>> android-g++ {
>>  
>> message ("** android-g++ ***" )
>> ANDROID_PACKAGE_SOURCE_DIR = $$PWD/platform/android
>> QT += androidextras
>> QT += bluetooth
>>  
>> }
>>  
>>  
>> -Ed This email and any files transmitted with it from The Charles Machine 
>> Works, Inc. are confidential and intended solely for the use of the 
>> individual or entity to which they are addressed. If you have received this 
>> email in error please notify the sender. Our company accepts no liability 
>> for the contents of this email, or for the consequences of any actions taken 
>> on the basis of the information provided, unless that information is 
>> subsequently confirmed in writing. Please note that any views or opinions 
>> presented in this email are solely those of the author and do not 
>> necessarily represent those of the company. Finally, the recipient should 
>> check this email and any attachments for the presence of viruses. The 
>> company accepts no liability for any damage caused by any virus transmitted 
>> by this email. ___ Interest 
>> mailing list Interest@qt-project.org <mailto:Interest@qt-project.org> 
>> http://lists.qt-project.org/mailman/listinfo/interest 
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.qt-2Dproject.org_mailman_listinfo_interest&d=CwMFaQ&c=G4BpsyPyB19LB50bn2swXw&r=cAG2c-SQES5P2qb8IW-uwnBOCX_f2qYJIlzenFnoHUc&m=LboYNa6PS--mD0RzhqCHEcK0Xo1seM79yWW_-fQwE7E&s=BMWxH-7V3lSXeF9SDqCq6S1mNFpB8YeMMYudQzCgvlQ&e=>
> This email and any files transmitted with it from The Charles Machine Works, 
> Inc. are confidential and intended solely for the use of the individual or 
> entity to which they are addressed. If you have received this email in error 
> please notify the sender. Our company accepts no liability for the contents 
> of this email, or for the consequences of any actions taken on the basis of 
> the information provided, unless that information is subsequently confirmed 
> in writing. Please note that any views or opinions presented in this email 
> are solely those of the author and do not necessarily represent those of the 
> company. Finally, the recipient should check this email and any attachments 
> for the presence of viruses. The company accepts no liability for any damage 
> caused by any virus transmitted by this email.
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Qt signal overhead (same thread, direct connection)

[Nuno Santos]

Hi,

I have an application that generates real time audio and in a system like this, 
a interruption may cause audio glitches.

Nowadays, in iOS, audio apps can be loaded by other apps. This transition takes 
time and probably some resources too.

While playing my app with the built in arpeggiator and then switching to 
another app, the notes would stop playing for a while, creating a non desired 
break in the flow.

The curious thing is that, if I had a single note playing, the sound was not 
being broken. 

Since the sound rendering engine is the same I couldn’t understand what was 
going on.

Then I made an experiment. Arpeggiator was using a signal to send the noteOn to 
the audio render engine. I decided to call the function directly on the synth 
render engine. Guess what, the problem disappears.

Is the signal/slot mechanism tied to the event loop? How much does it take for 
a signal/slot to be called? It might not be significant on a desktop computer 
but it certainly is on a ARM device specially in this kind of performance 
sensitive contexts.

After this, I’m into changing crucial functions to callbacks to improve 
performance. Is there any advice you could give me?

Thanks,

Regards,

Nuno

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt signal overhead (same thread, direct connection)

[Nuno Santos]

Hey,

It is definitely taking to much time, enough to cause buffer drops in this 
situation. 

I have changed to a callback calling mechanism and the problem is now fixed. 

I now have this in mind when I program sensitive parts of my apps. 

Regards,

Nuno

> On 22 Apr 2016, at 17:34, Alejandro Exojo  wrote:
> 
> El Friday 22 April 2016, Nuno Santos escribió:
>> Then I made an experiment. Arpeggiator was using a signal to send the
>> noteOn to the audio render engine. I decided to call the function directly
>> on the synth render engine. Guess what, the problem disappears.
>> 
>> Is the signal/slot mechanism tied to the event loop? How much does it take
>> for a signal/slot to be called? It might not be significant on a desktop
>> computer but it certainly is on a ARM device specially in this kind of
>> performance sensitive contexts.
> 
> This paragraph in the documentation (same link Benjamin sent) is also pretty 
> enlightening:
> 
>> Compared to callbacks, signals and slots are slightly slower because of the
>> increased flexibility they provide, although the difference for real
>> applications is insignificant. In general, emitting a signal that is
>> connected to some slots, is approximately ten times slower than calling
>> the receivers directly, with non-virtual function calls. This is the
>> overhead required to locate the connection object, to safely iterate over
>> all connections (i.e. checking that subsequent receivers have not been
>> destroyed during the emission), and to marshall any parameters in a
>> generic fashion. While ten non-virtual function calls may sound like a
>> lot, it's much less overhead than any new or delete operation, for
>> example. As soon as you perform a string, vector or list operation that
>> behind the scene requires new or delete, the signals and slots overhead is
>> only responsible for a very small proportion of the complete function call
>> costs. The same is true whenever you do a system call in a slot; or
>> indirectly call more than ten functions. The simplicity and flexibility of
>> the signals and slots mechanism is well worth the overhead, which your
>> users won't even notice.
> 
> That was probably written long ago. I've read people mentioning that it might 
> be that signal emission would be slower nowadays.
> 
> Also, what type are you passing in the signal? The value is copied, so if 
> it's 
> expensive to copy, that might be a factor as well. I believe that is one of 
> the reasons why APIs like QIODevice don't send the received data through the 
> signal, but just the notification of the presence of new data. Later on you 
> have to retrieve it.
> 
> -- 
> Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2
> http://barnacity.net/ | http://disperso.net
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Ultra precise timing in Qt

[Nuno Santos]

Hi,

I have an audio app can sends midi to machines. Midi clock will set the machine 
tempo. When I have an arpeggiator running in the synth I want the machine to 
have exactly the same tempo. If the tempo is not the same, both will start to 
get out of sync. In music that is simply not acceptable.

So far I was using QElapsedTimer to measure this. One particular behaviour I 
observed was, once I started moving the virtual knobs and faders of the synth, 
it would start to get out of sync with the machine. My conclusion is that 
somehow, QElapsedTimer is tied to the event loop thus making it slower when 
other interactions are happening. Does this make sense? I haven’t looked to 
QElapsedTimer source code, i’m just guessing. Maybe I’m saying silly things.

I search for options and started using mach_absolute_time. The problem seems to 
be solved now. I have the soft synth running with the arpeggiator enabled 
sending midi clock to the machine, and they keep their tempo constant, even 
when the controls are being used or the device is under stress.

Does Qt provide any kind of cpu absolute clock for every platform? I couldn’t 
find it so far. 

Does anyone know the equivalent to mach_absolute_time in Windows and Android 
(probably the same as linux). 

Regards,

Nuno



___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Ultra precise timing in Qt

[Nuno Santos]

Alright! Even that I feel completely dumb right now, I’m happy that I don’t 
need to reinvent the wheel!!! :)

In the mean time, with all of this refactoring I have changes that could 
probably lead to better timing mechanism.

With this in mind I will do further refactor. 

Thanks for your prompt reply.

Regards

Nuno

> On 23 Apr 2016, at 18:20, Thiago Macieira  wrote:
> 
> On sábado, 23 de abril de 2016 18:06:38 PDT Nuno Santos wrote:
>> So far I was using QElapsedTimer to measure this. One particular behaviour I
>> observed was, once I started moving the virtual knobs and faders of the
>> synth, it would start to get out of sync with the machine. My conclusion is
>> that somehow, QElapsedTimer is tied to the event loop thus making it slower
>> when other interactions are happening. Does this make sense? I haven’t
>> looked to QElapsedTimer source code, i’m just guessing. Maybe I’m saying
>> silly things.
> 
> Yeah, kinda... Your description above summarises to "the more code I add, the 
> more work needs to be done".
> 
> The use of QElapsedTimer does not have any further impact on the event loop 
> besides executing more code and is not any different from any other further 
> addition of code that causes a system call. On some OSes, getting the system 
> time is a very fast operation (Linux); on others, it might be slow.
> 
>> I search for options and started using mach_absolute_time. The problem seems
>> to be solved now. I have the soft synth running with the arpeggiator
>> enabled sending midi clock to the machine, and they keep their tempo
>> constant, even when the controls are being used or the device is under
>> stress.
>> 
>> Does Qt provide any kind of cpu absolute clock for every platform? I
>> couldn’t find it so far.
> 
> Yes, it's called QElapsedTimer.
> 
>> Does anyone know the equivalent to mach_absolute_time in Windows and Android
>> (probably the same as linux).
> 
> On Windows, you use GetTickCount64 or QueryPerformanceCounter. On Android and 
> Linux, use clock_gettime for the CLOCK_MONOTONIC or CLOCK_MONOTONIC_COARSE.
> 
> Do you know how I know this? I looked into qelapsedtimer_win.cpp and 
> qelapsedtimer_unix.cpp.
> 
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Changing Android project default compilation settings

[Nuno Santos]

Hi,

I need to change the default android build settings for a project. One thing 
that I have noted is that if I add things to .pro file, the changes doesn’t 
reflect in the source code building. I have tried to change directly on .mkspec 
file and it worked. Is there any other recommended way of doing it?

I need to enable hardware floating point calculation by doing the following:

APP_CFLAGS -mhard-float -D_NDK_MATH_NO_SOFTFP=1
APP_ABI := armeabi-v7a-hard

Regards,

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] armv7a-hard-float in Qt android apps

[Nuno Santos]

Hi,

I’m trying to enable hard float computation on arm.

I think I have managed to enable it doing the following changes:

1) Set a new environment var ANDROID_ARCH_TARGET=armeabi-v7a-hard
2) Adding 

equals(ANDROID_TARGET_ARCH, armeabi-v7a-hard): \
QMAKE_CFLAGS = -Wno-psabi -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16 
-mhard-float -ffunction-sections -funwind-tables -fstack-protector 
-fno-short-enums -DANDROID -D_NDK_MATH_NO_SOFTFP=1 -Wa,--noexecstack 
-fno-builtin-memmove

3) QMAKE_LFLAGS= --sysroot=$$ANDROID_PLATFORM_ROOT_PATH 
-Wl,--no-warn-mismatch -lm_hard
4) QMAKE_LIBS_PRIVATE  = -lgnustl_shared -llog -lz -lm_hard -ldl -lc -lgcc

Code compiled and ruined fine but couldn’t notice a faster performance (I have 
profiling timers in critical parts of the application).

Has anyone done this before? 

Regards,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] armv7a-hard-float in Qt android apps

[Nuno Santos]

Ola,

Thanks for your reply.

While Qt code may be compiled with support for hard float, the qmake.specs file 
for android doesn’t show that and, in general, it seems that hard float support 
is disabled by default in android:

QMAKE_CFLAGS = -Wno-psabi -march=armv7-a -mfloat-abi=softfp -mfpu=vfp 
-ffunction-sections -funwind-tables -fstack-protector -fno-short-enums 
-DANDROID -Wa,--noexecstack -fno-builtin-memmove

I have found some questions/answer around the internet suggesting the following:

QMAKE_CFLAGS = -Wno-psabi -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16 
-mhard-float -ffunction-sections -funwind-tables -fstack-protector 
-fno-short-enums -DANDROID -D_NDK_MATH_NO_SOFTFP=1 -Wa,--noexecstack 
-fno-builtin-memmove

How can I have sure that it is in fact enabled?

Regards,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

> On 29 Apr 2016, at 12:55, Ola Røer Thorsen  wrote:
> 
> 2016-04-29 10:11 GMT+02:00 Nuno Santos  <mailto:nunosan...@imaginando.pt>>:
> 
> Code compiled and ruined fine but couldn’t notice a faster performance (I 
> have profiling timers in critical parts of the application).
> 
> Has anyone done this before? 
> 
> 
> As far as I know Qt is built with qreal as double as a default setting. 
> 
> In case your cpu only does single precision floats in hardware:
> 
> Maybe try to build Qt with qreal as single precision floats?
> I think the Qt configure option is "-qreal float", please check to be sure. 
> 
> Makes a notable difference on my ancient arm omap3 processor, at least. 
> 
> Also I'd recommend using the gcc warnings
> -Wdouble-promotion
> -Wfloat-conversion
> and make sure you are just using single precision floats as much as possible. 
> Lots of performance is lost if you keep mixing single- and double precision. 
> 
> float a = 1.0f;
> float b = 2.0*a; // BAD!
> float b = 2.0f*a; // Good!
> 
> Make sure you are using single-precision math functions (use std::sin, 
> std::abs, not cmath sin, abs, etc). The warnings above will show you all 
> these cases. 
> 
> Cheers,
> Ola
> 
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] armv7a-hard-float in Qt android apps

[Nuno Santos]

Thiago,

> On 29 Apr 2016, at 17:12, Thiago Macieira  wrote:
> 
> So I have to ask:
> a) are you sure your system wasn't already hard-float?

I don’t have a clue

> b) if it wasn't, are the hard-float libs for EVERYTHING available on the 
>   system? And does the lib loader know how to find them?

I don’t have a clue

I was able to compile my code with the hard-float settings but it doesn’t seem 
to speed up. For the contrary. I think it is slowing down.

This is unknown territory for me and I don’t know what I am doing.

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] armv7a-hard-float in Qt android apps

[Nuno Santos]

Ok Thiago, many thanks! 

> On 29 Apr 2016, at 17:35, Thiago Macieira  wrote:
> 
> On sexta-feira, 29 de abril de 2016 17:19:03 PDT Nuno Santos wrote:
>>> So I have to ask:
>>> a) are you sure your system wasn't already hard-float?
>> 
>> I don’t have a clue
>> 
>>> b) if it wasn't, are the hard-float libs for EVERYTHING available on the 
>>> 
>>>  system? And does the lib loader know how to find them?
>> 
>> I don’t have a clue
> 
> Then I recommend not pursuing this line of development until you find out 
> more.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Compiler optimisation flags on Android

[Nuno Santos]

Hi,

Below are the CFLAGS for Android 
(Qt/5.6/android_armv7/mkspecs/android-g++/qmake.conf)

I’m wondering why there are no optimisation settings for arm rather than size. 
Is there any specific reason? 

QMAKE_CFLAGS_WARN_ON= -Wall -Wno-psabi -W
QMAKE_CFLAGS_WARN_OFF   = -Wno-psabi
equals(ANDROID_TARGET_ARCH, x86) {
QMAKE_CFLAGS_RELEASE   = -O2
QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO= -g -O2
QMAKE_CFLAGS_DEBUG = -g
} else: equals(ANDROID_TARGET_ARCH, x86_64) {
QMAKE_CFLAGS_RELEASE   = -O2
QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO= -g -O2
QMAKE_CFLAGS_DEBUG = -g
} else: equals(ANDROID_TARGET_ARCH, mips) {
QMAKE_CFLAGS_RELEASE   = -O2
QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO= -g -O2
QMAKE_CFLAGS_DEBUG = -g -fno-omit-frame-pointer
} else: equals(ANDROID_TARGET_ARCH, mips64) {
QMAKE_CFLAGS_RELEASE   = -O2
QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO= -g -O2
QMAKE_CFLAGS_DEBUG = -g -fno-omit-frame-pointer
} else: equals(ANDROID_TARGET_ARCH, arm64-v8a) {
QMAKE_CFLAGS_RELEASE   = -O2
QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO= -g -O2
QMAKE_CFLAGS_DEBUG = -g -fno-omit-frame-pointer
} else { # arm
QMAKE_CFLAGS_RELEASE   = -Os -fomit-frame-pointer 
-fno-strict-aliasing -finline-limit=64
QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO= -g -Os -fomit-frame-pointer 
-fno-strict-aliasing -finline-limit=64
QMAKE_CFLAGS_DEBUG = -g -marm -O0 
-fno-omit-frame-pointer
equals(ANDROID_TARGET_ARCH, armeabi):if(equals(NDK_TOOLCHAIN_VERSION, 
4.8)|equals(NDK_TOOLCHAIN_VERSION, 4.9)) {
DEFINES += QT_OS_ANDROID_GCC_48_WORKAROUND
} else {
QMAKE_CFLAGS_RELEASE += -mthumb
QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -mthumb
}
}

Regards,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Back button crashes Qt app on Android

[Nuno Santos]

Hi,

I have noticed the if I press the back button in a Qt Android app, it crashes. 

Does anyone here had the same problem?

Regards,

Nuno

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiler optimisation flags on Android

[Nuno Santos]

I mean -O2, like the others

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

> On 03 May 2016, at 06:27, Thiago Macieira  wrote:
> 
> On segunda-feira, 2 de maio de 2016 22:07:03 PDT Nuno Santos wrote:
>> Hi,
>> 
>> Below are the CFLAGS for Android
>> (Qt/5.6/android_armv7/mkspecs/android-g++/qmake.conf)
>> 
>> I’m wondering why there are no optimisation settings for arm rather than
>> size. Is there any specific reason?
> 
> Why should there be?
> 
>> } else { # arm
>>QMAKE_CFLAGS_RELEASE   = -Os -fomit-frame-pointer
>> -fno-strict-aliasing -finline-limit=64 
>>QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO   = -g -Os -fomit-frame-pointer 
>>-fno-strict-aliasing -finline-limit=64
>>QMAKE_CFLAGS_DEBUG = -g -marm -O0 -fno-omit-frame-
>>pointer 
>>equals(ANDROID_TARGET_ARCH, armeabi):if(equals(NDK_TOOLCHAIN_VERSION,
>> 4.8)|equals(NDK_TOOLCHAIN_VERSION, 4.9)) {
>>DEFINES += QT_OS_ANDROID_GCC_48_WORKAROUND
>>} else {
>>QMAKE_CFLAGS_RELEASE += -mthumb
>>QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -mthumb
>>}
>> }
> 
> This section you pasted contradicts your statement. There are more 
> optimisation flags besides -Os.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiler optimisation flags on Android

[Nuno Santos]

Because, from my experience with the code compiled for Intel, putting -O3 made 
a huge difference on the processing code of my audio app. But the same might 
not be valid for arm. That’s why I’m asking. 

I’m trying to squeeze the most of the C++ code performance on Android.

> On 03 May 2016, at 18:05, Thiago Macieira  wrote:
> 
> Em terça-feira, 3 de maio de 2016, às 18:00:07 PDT, Nuno Santos escreveu:
>> I mean -O2, like the others
> 
> You didn't answer why you think that it's important to use -O2 instead of -Os.
> 
> The reason why it's using -Os instead of -O2 was probably because the 
> maintainers of the Android port thought that optimising for size was 
> important, for some reason, on ARM (see also the use of Thumb). That way, 
> binaries would be smaller.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Back button crashes Qt app on Android

[Nuno Santos]

It seems that back button by default deletes the activity. It seems that I’m 
not able to override the back button action and therefore, it is killing my 
activity. During this delete force, it is crashing the app. 

Any special remarks in order to override the back button function on a Qt 
Android app?

I’m doing this:

@Override
public void onBackPressed()
{
Log.d(“APP", "onBackPressed");

super.onPause();
}

Nuno

> On 03 May 2016, at 15:09, Nuno Santos  wrote:
> 
> Hi,
> 
> I have noticed the if I press the back button in a Qt Android app, it 
> crashes. 
> 
> Does anyone here had the same problem?
> 
> Regards,
> 
> Nuno
> 

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiler optimisation flags on Android

[Nuno Santos]

Thiago,

Thanks for your explanation.

I will try to understand if it is bringing me benefits or not. 

Regards,

Nuno 

> On 03 May 2016, at 18:18, Thiago Macieira  wrote:
> 
> On terça-feira, 3 de maio de 2016 18:14:11 PDT Nuno Santos wrote:
>> Because, from my experience with the code compiled for Intel, putting -O3
>> made a huge difference on the processing code of my audio app. But the same
>> might not be valid for arm. That’s why I’m asking.
> 
> -O3 not only enables all of -O2, but also enables optimisations that increase 
> code size considerably. One of them is -ftree-vectorize, which is one of the 
> reasons why your code and QtCore benefit a lot from it.
> 
> I have no clue whether GCC's -ftree-vectorize support on ARM is any good. In 
> any case, I doubt that you can count on Neon support on all those Android 
> devices anyway, so it's likely that the gain is minimal anyway.
> 
> PS: QtCore and QtGui are compiled with CONFIG += optimize_full, which enables 
> -O3.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

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

[Nuno Santos]

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 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 mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>> 
> For the SDK Version:
> 
> Have you set the Version from QtCreator - Projects - Build Settings -
> Build Android APK -> ...22 ...23
> 
> ekke
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Enabling NEON on a Qt Android app

[Nuno Santos]

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 


#include 
...
...
if (android_getCpuFamily() == ANDROID_CPU_FAMILY_ARM && 
(android_getCpuFeatures() & ANDROID_CPU_ARM_FEATURE_NEON) != 0)
{
// use NEON-optimized routines
...
}
else
{
// use non-NEON fallback routines instead
...
}

One curious things is that I was unable to have android_getCpuFamily and 
android_getCpuFeatures detected by the compiler.

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 the existing libraries. Of course 
if that application needs more libs, Ministro will download only those that are 
missing.
Ministro can detect if the device armv5 CPU has VFP or if the device armv7 CPU 
has NEON and it can download libs specific to that device CPU. Even if your 
application is not built with these CPU features, just using Qt libs built with 
them will make it run faster (on armv5, VFP really makes the difference, it 
will be way much faster). Currently these libs are not available, but I intend 
to publish them starting with 5.4.
The article has a couple of years. Is it still valid?

I’m completely aware that I would need to refactor my code in order to take 
advantage of NEON, but i’m getting to a point where I can’t do much more to 
improve performance.

Has anyone used NEON within a Qt Android app? Please advise.

Regards,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

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

[Nuno Santos]

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? 
> 
> 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 include files 
> built 
> with and without Neon support into the same binary if those sources are C++.
> 
> I don't know Android API, but if you can't find a suitable function to tell 
> you 
> whether Neon is possible, you can always just read from /proc/cpuinfo or from 
> /proc/self/auxv.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] AndroidManifest Minimum required API not working as expected

[Nuno Santos]

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

I’m selecting Android 5.0 (API 21) in Android Manifest and it is compiling 
against 17.

I have deleted all the build directories as well as all the project .pro.user 
and selected API 21 again. Hit qmake and builded. It is now building against 9:

-isystem /Users/nsantos/android/ndk/platforms/android-9

Why is this happening? What does control Android NDK API usage?

Thanks,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] AndroidManifest Minimum required API not working as expected

[Nuno Santos]

That doesn’t seem to be true. At least with the following Qt Creator:

Qt Creator 3.6.1

Based on Qt 5.6.0 (Clang 7.0 (Apple), 64 bit)

Built on Mar 14 2016 09:38:07

From revision 53b8ca08bf




I had to open the generated Makefile and make a global replace of android-9 for 
android-21 to be able to build with API 21

> On 09 May 2016, at 21:10, Igor Mironchik  wrote:
> 
> Hi,
> 
> Do you build with QtCreator? If so then when QtCreator configures project it 
> invokes tools/android Android NDK tool and select highest API available and 
> build with such settings.
> 
> On 09.05.2016 22:47, Nuno Santos wrote:
>> Nuno Santos
>> Founder / CEO / CTO
>> www.imaginando.pt <http://www.imaginando.pt/>
>> +351 91 621 69 62
>> 
>> I’m selecting Android 5.0 (API 21) in Android Manifest and it is compiling 
>> against 17.
>> 
>> I have deleted all the build directories as well as all the project 
>> .pro.user and selected API 21 again. Hit qmake and builded. It is now 
>> building against 9:
>> 
>> -isystem /Users/nsantos/android/ndk/platforms/android-9
>> 
>> Why is this happening? What does control Android NDK API usage?
>> 
>> Thanks,
>> 
>> Nuno
>> 
>> 
>> ___
>> Interest mailing list
>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>> http://lists.qt-project.org/mailman/listinfo/interest 
>> <http://lists.qt-project.org/mailman/listinfo/interest>
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] AndroidManifest Minimum required API not working as expected

[Nuno Santos]

Even more weird...

➜  ~ cat app.pro.user | grep Sdk
  android-23
  android-23
  android-23
➜  ~

> On 09 May 2016, at 22:03, Igor Mironchik  wrote:
> 
> Can you open *.user file and search for android record like this:
> 
> android-9
> 
> If you will see here android-9 then you project will be built with API 9, I 
> guess...
> 
> On 09.05.2016 23:35, Nuno Santos wrote:
>> That doesn’t seem to be true. At least with the following Qt Creator:
>> 
>> Qt Creator 3.6.1
>> 
>> Based on Qt 5.6.0 (Clang 7.0 (Apple), 64 bit)
>> 
>> Built on Mar 14 2016 09:38:07
>> 
>> From revision 53b8ca08bf
>> 
>> 
>> 
>> 
>> I had to open the generated Makefile and make a global replace of android-9 
>> for android-21 to be able to build with API 21
>> 
>>> On 09 May 2016, at 21:10, Igor Mironchik < 
>>> <mailto:igor.mironc...@gmail.com>igor.mironc...@gmail.com 
>>> <mailto:igor.mironc...@gmail.com>> wrote:
>>> 
>>> Hi,
>>> 
>>> Do you build with QtCreator? If so then when QtCreator configures project 
>>> it invokes tools/android Android NDK tool and select highest API available 
>>> and build with such settings.
>>> 
>>> On 09.05.2016 22:47, Nuno Santos wrote:
>>>> Nuno Santos
>>>> Founder / CEO / CTO
>>>> www.imaginando.pt <http://www.imaginando.pt/>
>>>> +351 91 621 69 62
>>>> 
>>>> I’m selecting Android 5.0 (API 21) in Android Manifest and it is compiling 
>>>> against 17.
>>>> 
>>>> I have deleted all the build directories as well as all the project 
>>>> .pro.user and selected API 21 again. Hit qmake and builded. It is now 
>>>> building against 9:
>>>> 
>>>> -isystem /Users/nsantos/android/ndk/platforms/android-9
>>>> 
>>>> Why is this happening? What does control Android NDK API usage?
>>>> 
>>>> Thanks,
>>>> 
>>>> Nuno
>>>> 
>>>> 
>>>> ___
>>>> Interest mailing list
>>>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>>>> http://lists.qt-project.org/mailman/listinfo/interest 
>>>> <http://lists.qt-project.org/mailman/listinfo/interest>
>>> 
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>>> http://lists.qt-project.org/mailman/listinfo/interest 
>>> <http://lists.qt-project.org/mailman/listinfo/interest>
>> 
> 

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] AndroidManifest Minimum required API not working as expected

[Nuno Santos]

I have been using Gradle all the time for more than 6 months now. 

I have been noticing some random problems, but lately I have been having the 
need to change the API more regularly and the problem become evident.

> On 10 May 2016, at 07:26, Gianluca  wrote:
> 
> Please, can you tell us if all these problems appear using “ant” or using 
> “gradle” ?
> (Old Android build was with “ant”, now ant is deprecated and you should use 
> only “gradle” … but Qt still support both)
> 
> Il giorno 10/mag/2016, alle ore 05:04, NoRulez  <mailto:noru...@me.com>> ha scritto:
> 
>> Hello,
>> 
>> I've the same problem when building with CMake on the command line. I want 
>> target android-21 but android-23 is used. It seems that there is maybe a bug 
>> somewhere.
>> 
>> 
>> Am 09.05.2016 um 23:17 schrieb Igor Mironchik > <mailto:igor.mironc...@gmail.com>>:
>> 
>>> Really weird...
>>> 
>>> What is command lines when you compiling?
>>> 
>>> Is there android-9 or android-23 in pathes?
>>> 
>>> On 10.05.2016 00:12, Nuno Santos wrote:
>>>> Even more weird...
>>>> 
>>>> ➜  ~ cat app.pro.user | grep Sdk
>>>>   android-23
>>>>   android-23
>>>>   android-23
>>>> ➜  ~
>>>> 
>>>>> On 09 May 2016, at 22:03, Igor Mironchik < 
>>>>> <mailto:igor.mironc...@gmail.com>igor.mironc...@gmail.com 
>>>>> <mailto:igor.mironc...@gmail.com>> wrote:
>>>>> 
>>>>> Can you open *.user file and search for android record like this:
>>>>> 
>>>>> android-9
>>>>> 
>>>>> If you will see here android-9 then you project will be built with API 9, 
>>>>> I guess...
>>>>> 
>>>>> On 09.05.2016 23:35, Nuno Santos wrote:
>>>>>> That doesn’t seem to be true. At least with the following Qt Creator:
>>>>>> 
>>>>>> Qt Creator 3.6.1
>>>>>> 
>>>>>> Based on Qt 5.6.0 (Clang 7.0 (Apple), 64 bit)
>>>>>> 
>>>>>> Built on Mar 14 2016 09:38:07
>>>>>> 
>>>>>> From revision 53b8ca08bf
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> I had to open the generated Makefile and make a global replace of 
>>>>>> android-9 for android-21 to be able to build with API 21
>>>>>> 
>>>>>>> On 09 May 2016, at 21:10, Igor Mironchik >>>>>> <mailto:igor.mironc...@gmail.com>> wrote:
>>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> Do you build with QtCreator? If so then when QtCreator configures 
>>>>>>> project it invokes tools/android Android NDK tool and select highest 
>>>>>>> API available and build with such settings.
>>>>>>> 
>>>>>>> On 09.05.2016 22:47, Nuno Santos wrote:
>>>>>>>> Nuno Santos
>>>>>>>> Founder / CEO / CTO
>>>>>>>> www.imaginando.pt <http://www.imaginando.pt/>
>>>>>>>> +351 91 621 69 62
>>>>>>>> 
>>>>>>>> I’m selecting Android 5.0 (API 21) in Android Manifest and it is 
>>>>>>>> compiling against 17.
>>>>>>>> 
>>>>>>>> I have deleted all the build directories as well as all the project 
>>>>>>>> .pro.user and selected API 21 again. Hit qmake and builded. It is now 
>>>>>>>> building against 9:
>>>>>>>> 
>>>>>>>> -isystem /Users/nsantos/android/ndk/platforms/android-9
>>>>>>>> 
>>>>>>>> Why is this happening? What does control Android NDK API usage?
>>>>>>>> 
>>>>>>>> Thanks,
>>>>>>>> 
>>>>>>>> Nuno
>>>>>>>> 
>>>>>>>> 
>>>>>>>> ___
>>>>>>>> Interest mailing list
>>>>>>>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>>>>>>>> http://lists.qt-project.org/mailman/listinfo/interest 
>>>>>>>> <http://lists.qt-project.org/mailman/listinfo/interest>
>>>>>>> 
>>>>>>> ___
>>>>>>> Interest mailing list
>>>>>>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>>>>>>> http://lists.qt-project.org/mailman/listinfo/interest 
>>>>>>> <http://lists.qt-project.org/mailman/listinfo/interest>
>>>>>> 
>>>>> 
>>>> 
>>> 
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>>> http://lists.qt-project.org/mailman/listinfo/interest 
>>> <http://lists.qt-project.org/mailman/listinfo/interest>
>> ___
>> Interest mailing list
>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>> http://lists.qt-project.org/mailman/listinfo/interest
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] AndroidManifest Minimum required API not working as expected

[Nuno Santos]

I think this problem is on qmake because the Qt Makefile is using android-9 
instead of android-21. I need API 21 for NDK things and not for Java things, 
and that must be specified on the Qt Makefile which is generated by qmake.

> On 10 May 2016, at 07:38, Gianluca  wrote:
> 
> If you use gradle and there is some problems on setting properly it using Qt 
> Creator, you can override some settings adding the gradle.properties file to 
> your Android source directory.
> 
> I got problem on selecting the right Java version for compile java code and 
> this is my gradle.properties that solved the issue … I think you can change 
> and select also the sdk to use easily:
> 
> org.gradle.java.home=/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home
> 
> androidBuildToolsVersion=22.0.1
> androidCompileSdkVersion=23
> buildDir=build
> qt5AndroidDir=__qt5__android__files__
> 
> I do not put this into the repository, but I maintain them on machine basis, 
> so that each machine has it’s own gradle.properties to use
> 
> Ciao,
> Gianluca.
> 
> 
> Il giorno 10/mag/2016, alle ore 07:33, Nuno Santos  <mailto:nunosan...@imaginando.pt>> ha scritto:
> 
>> I have been using Gradle all the time for more than 6 months now. 
>> 
>> I have been noticing some random problems, but lately I have been having the 
>> need to change the API more regularly and the problem become evident.
>> 
>>> On 10 May 2016, at 07:26, Gianluca >> <mailto:gmax...@gmail.com>> wrote:
>>> 
>>> Please, can you tell us if all these problems appear using “ant” or using 
>>> “gradle” ?
>>> (Old Android build was with “ant”, now ant is deprecated and you should use 
>>> only “gradle” … but Qt still support both)
>>> 
>>> Il giorno 10/mag/2016, alle ore 05:04, NoRulez >> <mailto:noru...@me.com>> ha scritto:
>>> 
>>>> Hello,
>>>> 
>>>> I've the same problem when building with CMake on the command line. I want 
>>>> target android-21 but android-23 is used. It seems that there is maybe a 
>>>> bug somewhere.
>>>> 
>>>> 
>>>> Am 09.05.2016 um 23:17 schrieb Igor Mironchik >>> <mailto:igor.mironc...@gmail.com>>:
>>>> 
>>>>> Really weird...
>>>>> 
>>>>> What is command lines when you compiling?
>>>>> 
>>>>> Is there android-9 or android-23 in pathes?
>>>>> 
>>>>> On 10.05.2016 00:12, Nuno Santos wrote:
>>>>>> Even more weird...
>>>>>> 
>>>>>> ➜  ~ cat app.pro.user | grep Sdk
>>>>>>   android-23
>>>>>>   android-23
>>>>>>   android-23
>>>>>> ➜  ~
>>>>>> 
>>>>>>> On 09 May 2016, at 22:03, Igor Mironchik < 
>>>>>>> <mailto:igor.mironc...@gmail.com>igor.mironc...@gmail.com 
>>>>>>> <mailto:igor.mironc...@gmail.com>> wrote:
>>>>>>> 
>>>>>>> Can you open *.user file and search for android record like this:
>>>>>>> 
>>>>>>> android-9
>>>>>>> 
>>>>>>> If you will see here android-9 then you project will be built with API 
>>>>>>> 9, I guess...
>>>>>>> 
>>>>>>> On 09.05.2016 23:35, Nuno Santos wrote:
>>>>>>>> That doesn’t seem to be true. At least with the following Qt Creator:
>>>>>>>> 
>>>>>>>> Qt Creator 3.6.1
>>>>>>>> 
>>>>>>>> Based on Qt 5.6.0 (Clang 7.0 (Apple), 64 bit)
>>>>>>>> 
>>>>>>>> Built on Mar 14 2016 09:38:07
>>>>>>>> 
>>>>>>>> From revision 53b8ca08bf
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> I had to open the generated Makefile and make a global replace of 
>>>>>>>> android-9 for android-21 to be able to build with API 21
>>>>>>>> 
>>>>>>>>> On 09 May 2016, at 21:10, Igor Mironchik >>>>>>>> <mailto:igor.mironc...@gmail.com>> wrote:
>>>>>>>>> 
>>>>>>>>> Hi,
>>>>>>>>> 
>>>>>>>>> Do you build with QtCreator? If so then when Q

Re: [Interest] AndroidManifest Minimum required API not working as expected

[Nuno Santos]

Who generates the Makefile for C++ code compiling? Is grade involved? My 
conviction is that grade is only involved in the java related parts.

> On 10 May 2016, at 10:50, Gian Maxera  wrote:
> 
> I don’t think the problem is on makefile … but on the tool are using.
> I want to insist on check if you are using gradle … because I don’t have any 
> of your problem with default settings of Qt Creator and using gradle.
> 
> When I create a new project with Qt Creator and I set to use gradle … the app 
> name is correct and I can change the sdks.
> 
> 
>> On 10 May 2016, at 10:00, NoRulez mailto:noru...@me.com>> 
>> wrote:
>> 
>> I think this too, because I can't override the android-23 nor the QtApp name
>> 
>> Am 10.05.2016 um 10:06 schrieb Nuno Santos > <mailto:nunosan...@imaginando.pt>>:
>> 
>>> I think this problem is on qmake because the Qt Makefile is using android-9 
>>> instead of android-21. I need API 21 for NDK things and not for Java 
>>> things, and that must be specified on the Qt Makefile which is generated by 
>>> qmake.
>>> 
>>>> On 10 May 2016, at 07:38, Gianluca >>> <mailto:gmax...@gmail.com>> wrote:
>>>> 
>>>> If you use gradle and there is some problems on setting properly it using 
>>>> Qt Creator, you can override some settings adding the gradle.properties 
>>>> file to your Android source directory.
>>>> 
>>>> I got problem on selecting the right Java version for compile java code 
>>>> and this is my gradle.properties that solved the issue … I think you can 
>>>> change and select also the sdk to use easily:
>>>> 
>>>> org.gradle.java.home=/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home
>>>> 
>>>> androidBuildToolsVersion=22.0.1
>>>> androidCompileSdkVersion=23
>>>> buildDir=build
>>>> qt5AndroidDir=__qt5__android__files__
>>>> 
>>>> I do not put this into the repository, but I maintain them on machine 
>>>> basis, so that each machine has it’s own gradle.properties to use
>>>> 
>>>> Ciao,
>>>> Gianluca.
>>>> 
>>>> 
>>>> Il giorno 10/mag/2016, alle ore 07:33, Nuno Santos 
>>>> mailto:nunosan...@imaginando.pt>> ha scritto:
>>>> 
>>>>> I have been using Gradle all the time for more than 6 months now. 
>>>>> 
>>>>> I have been noticing some random problems, but lately I have been having 
>>>>> the need to change the API more regularly and the problem become evident.
>>>>> 
>>>>>> On 10 May 2016, at 07:26, Gianluca >>>>> <mailto:gmax...@gmail.com>> wrote:
>>>>>> 
>>>>>> Please, can you tell us if all these problems appear using “ant” or 
>>>>>> using “gradle” ?
>>>>>> (Old Android build was with “ant”, now ant is deprecated and you should 
>>>>>> use only “gradle” … but Qt still support both)
>>>>>> 
>>>>>> Il giorno 10/mag/2016, alle ore 05:04, NoRulez >>>>> <mailto:noru...@me.com>> ha scritto:
>>>>>> 
>>>>>>> Hello,
>>>>>>> 
>>>>>>> I've the same problem when building with CMake on the command line. I 
>>>>>>> want target android-21 but android-23 is used. It seems that there is 
>>>>>>> maybe a bug somewhere.
>>>>>>> 
>>>>>>> 
>>>>>>> Am 09.05.2016 um 23:17 schrieb Igor Mironchik >>>>>> <mailto:igor.mironc...@gmail.com>>:
>>>>>>> 
>>>>>>>> Really weird...
>>>>>>>> 
>>>>>>>> What is command lines when you compiling?
>>>>>>>> 
>>>>>>>> Is there android-9 or android-23 in pathes?
>>>>>>>> 
>>>>>>>> On 10.05.2016 00:12, Nuno Santos wrote:
>>>>>>>>> Even more weird...
>>>>>>>>> 
>>>>>>>>> ➜  ~ cat app.pro.user | grep Sdk
>>>>>>>>>   android-23
>>>>>>>>>   android-23
>>>>>>>>>   android-23
>>>>>>>>> ➜  ~
>>>>>>>>> 
>>>>>>>>>> On 09 May 2016, at 22:03, Igor Mironchik < 
>>

Re: [Interest] AndroidManifest Minimum required API not working as expected

[Nuno Santos]

From what I can see in the compile output window in QtCreator is:

1) QtCreator calls make on the shadow build directory. This will execute the 
Makefile generated by qmake and compile the C++ code.
2) QtCreator calls "/Users/nsantos/Qt/5.6/android_armv7/bin/androiddeployqt" 
--input 
/tmp/build-drc-Android_for_armeabi_v7a_GCC_4_9_Qt_5_6_0-Release/android-libDRC.so-deployment-settings.json
 --output 
/tmp/build-drc-Android_for_armeabi_v7a_GCC_4_9_Qt_5_6_0-Release/android-build 
--deployment bundled --android-platform android-23 --jdk 
/Library/Java/JavaVirtualMachines/jdk1.7.0_65.jdk/Contents/Home —gradle

This makes me believe that there is no relation between the Makefile and gradle 
and/or ant build process

> On 10 May 2016, at 11:33, Gian Maxera  wrote:
> 
> I suppose that qmake is generating different Makefiles depending on what is 
> using for build the java part.
> 
> So, my supposition is:
>  - when you select “ant” as java builder, then Qt Creator generate a Makefile 
> for using “ant” … and this may contain some bugs that doesn’t allow to change 
> the Qt app name and the Android SDKs
>  - when you select “gradle” as java builder, then Qt Creator generate a 
> (different) Makefile for using “gradle” … and this may be bug-free (because I 
> didn’t have any problem on setting Android SDKs) … and using “gradle” allow 
> to change other aspect of java building overriding gradle.properties.
> 
> 
>> On 10 May 2016, at 11:18, Nuno Santos > <mailto:nunosan...@imaginando.pt>> wrote:
>> 
>> Who generates the Makefile for C++ code compiling? Is grade involved? My 
>> conviction is that grade is only involved in the java related parts.
>> 
>>> On 10 May 2016, at 10:50, Gian Maxera >> <mailto:gmax...@gmail.com>> wrote:
>>> 
>>> I don’t think the problem is on makefile … but on the tool are using.
>>> I want to insist on check if you are using gradle … because I don’t have 
>>> any of your problem with default settings of Qt Creator and using gradle.
>>> 
>>> When I create a new project with Qt Creator and I set to use gradle … the 
>>> app name is correct and I can change the sdks.
>>> 
>>> 
>>>> On 10 May 2016, at 10:00, NoRulez mailto:noru...@me.com>> 
>>>> wrote:
>>>> 
>>>> I think this too, because I can't override the android-23 nor the QtApp 
>>>> name
>>>> 
>>>> Am 10.05.2016 um 10:06 schrieb Nuno Santos >>> <mailto:nunosan...@imaginando.pt>>:
>>>> 
>>>>> I think this problem is on qmake because the Qt Makefile is using 
>>>>> android-9 instead of android-21. I need API 21 for NDK things and not for 
>>>>> Java things, and that must be specified on the Qt Makefile which is 
>>>>> generated by qmake.
>>>>> 
>>>>>> On 10 May 2016, at 07:38, Gianluca >>>>> <mailto:gmax...@gmail.com>> wrote:
>>>>>> 
>>>>>> If you use gradle and there is some problems on setting properly it 
>>>>>> using Qt Creator, you can override some settings adding the 
>>>>>> gradle.properties file to your Android source directory.
>>>>>> 
>>>>>> I got problem on selecting the right Java version for compile java code 
>>>>>> and this is my gradle.properties that solved the issue … I think you can 
>>>>>> change and select also the sdk to use easily:
>>>>>> 
>>>>>> org.gradle.java.home=/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home
>>>>>> 
>>>>>> androidBuildToolsVersion=22.0.1
>>>>>> androidCompileSdkVersion=23
>>>>>> buildDir=build
>>>>>> qt5AndroidDir=__qt5__android__files__
>>>>>> 
>>>>>> I do not put this into the repository, but I maintain them on machine 
>>>>>> basis, so that each machine has it’s own gradle.properties to use
>>>>>> 
>>>>>> Ciao,
>>>>>> Gianluca.
>>>>>> 
>>>>>> 
>>>>>> Il giorno 10/mag/2016, alle ore 07:33, Nuno Santos 
>>>>>> mailto:nunosan...@imaginando.pt>> ha scritto:
>>>>>> 
>>>>>>> I have been using Gradle all the time for more than 6 months now. 
>>>>>>> 
>>>>>>> I have been noticing some random problems, but lately I have been 
>>>>>>> having the need to change the API more regularly and the problem 

[Interest] Event filter not working all the time (filter android default back button action)

[Nuno Santos]

Hi,

I have the following event filter to filter the default back button Action on a 
Android app. I’m attaching this filter to the app QWindow.

It works, but not all the times! I was wondering why. Does anyone had the need 
to do something similar and can tell me why it is not working flawless all the 
time? 

I need to filter the default back button action in order to avoid the app 
crash. 
 
bool eventFilter(QObject *obj, QEvent *event)
{

if (event->type()==QEvent::KeyPress)
{
QKeyEvent* key = static_cast(event);

if (key->key()==Qt::Key_Back)
{
//qDebug() << "ignore default back button action on Android";
event->accept();

return true;
}
}

return QObject::eventFilter(obj, event);
}

Nuno

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.6 QML on iOS: Crash on start up

[Nuno Santos]

Qt 5.6 works fine on iOS. 

Don’t know why do you use cmake and not regular QtCreator solution.

I would start by starting a new project on QtCreator and see if it has the same 
behaviour.

It works for me! 

Regards,

Nuno

> On 11 May 2016, at 05:55, NoRulez  wrote:
> 
> Hello,
> 
> I compiled my first QML app for iOS. After I copied it to my device and start 
> it, it only flickers for a second and exit with SIGABRT.
> 
> I doesn't find anything useful in the iPhone logs.
> I've an iPhone 6s with iOS 9.3 installed. The build machine is 10.11.4 with 
> Xcode 7.3.1 and Qt5.6 for iOS from the Online Installer and CMake 3.5.2. The 
> toolchain file I used is from https://github.com/cristeab/ios-cmake
> 
> Any hints?
> 
> For forgotten or further information please ask
> 
> Thanks in advance
> Best regards
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Blind binding crash on Qml instantiation

[Nuno Santos]

Hi,

I’m having a blind qml crash. I have been commenting the code on/off all day 
long and I can’t seem to find a pattern, something I know exactly what it is. 
What is the procedure to find such problems? 

When I manage to catch a crash with the debugger this is what I can find:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtQml0x00010ca9a0a4 
QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, 
QFlags) + 596
1   org.qt-project.QtQml0x00010ca99bf8 
QQmlBinding::update(QFlags) + 952
2   org.qt-project.QtQml0x00010caa9b30 
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) + 272
3   org.qt-project.QtQml0x00010ca34fa0 
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) + 1376
4   org.qt-project.QtQml0x00010ca35d31 
QQmlIncubationController::incubateFor(int) + 129
5   org.qt-project.QtQuick  0x00010bed2f05 
QQuickWindowIncubationController::incubate() + 69
6   org.qt-project.QtCore   0x00010d066670 
QObject::event(QEvent*) + 48
7   org.qt-project.QtCore   0x00010d03a80f 
QCoreApplicationPrivate::notify_helper(QObject*, QEvent*) + 303
8   org.qt-project.QtCore   0x00010d03a46d 
QCoreApplication::notify(QObject*, QEvent*) + 45
9   org.qt-project.QtCore   0x00010d03a3f4 
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164
10  org.qt-project.QtCore   0x00010d091662 
QTimerInfoList::activateTimers() + 1266
11  libqcocoa.dylib 0x00010f933772 
QCocoaEventDispatcherPrivate::activateTimersSourceCallback(void*) + 18
12  com.apple.CoreFoundation0x7fff981d6881 
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
13  com.apple.CoreFoundation0x7fff981b5fbc 
__CFRunLoopDoSources0 + 556
14  com.apple.CoreFoundation0x7fff981b54df __CFRunLoopRun + 927
15  com.apple.CoreFoundation0x7fff981b4ed8 CFRunLoopRunSpecific 
+ 296
16  com.apple.HIToolbox 0x7fff8a7af935 
RunCurrentEventLoopInMode + 235
17  com.apple.HIToolbox 0x7fff8a7af76f 
ReceiveNextEventCommon + 432
18  com.apple.HIToolbox 0x7fff8a7af5af 
_BlockUntilNextEventMatchingListInModeWithFilter + 71
19  com.apple.AppKit0x7fff970f3df6 _DPSNextEvent + 1067
20  com.apple.AppKit0x7fff970f3226 -[NSApplication 
_nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
21  com.apple.AppKit0x7fff970e7d80 -[NSApplication run] 
+ 682
22  libqcocoa.dylib 0x00010f93437f 
QCocoaEventDispatcher::processEvents(QFlags) + 
2191
23  org.qt-project.QtCore   0x00010d0367a1 
QEventLoop::exec(QFlags) + 401
24  org.qt-project.QtCore   0x00010d03aa65 
QCoreApplication::exec() + 341
25  com.imaginando.LK   0x00010b416317 main + 1879 
(main.cpp:249)
26  com.imaginando.LK   0x00010b3bccb4 start + 52

Regards,

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Blind binding crash on Qml instantiation

[Nuno Santos]

That’s the question! Completely blind

I have a complex C+ structure with property. Each property can have more than 
one property. 

I have a few guesses but couldn’t confirm any of them.

> On 07 Jun 2016, at 18:37, Jason H  wrote:
> 
> 
>> 
>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
>> 0   org.qt-project.QtQml 0x00010ca9a0a4 
>> QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, 
>> QFlags) + 596
>> 1   org.qt-project.QtQml 0x00010ca99bf8 
>> QQmlBinding::update(QFlags) + 952
>> 2   org.qt-project.QtQml 0x00010caa9b30 
>> QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) + 272
>> 3   org.qt-project.QtQml 0x00010ca34fa0 
>> QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) + 1376
>> 4   org.qt-project.QtQml 0x00010ca35d31 
>> QQmlIncubationController::incubateFor(int) + 129
>> 5   org.qt-project.QtQuick   0x00010bed2f05 
>> QQuickWindowIncubationController::incubate() + 69
> 
> So what property and value is it trying to write?

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Qt Screen.pixelDensity and Android devices

[Nuno Santos]

Qt/Android developers,

Do you think all devices correctly report Screen.pixelDensity?

I’m working on a  HP 21 Slate and it has a pixel density of around 8.5.

The display resolution is 1920x1080. Dividing 1920 by 8.5 gives 225mm but the 
screen has 480mm width. 

I have checked devicePixelRatio and it is one. From documentation, 
devicePixelRatio is only for Apple screens.

So… do you think it is possible to consistently find out the size of the screen 
on all devices?

Thanks,

Regards,

Nuno

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt Screen.pixelDensity and Android devices

[Nuno Santos]

5.6 

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

> On 06 Jul 2016, at 17:14, Jason H  wrote:
> 
> No, but it is supposed to work Any Day Now(tm) (5.7 or 5.8?)
>  
> Sent: Wednesday, July 06, 2016 at 11:32 AM
> From: "Nuno Santos" 
> To: "Qt Project MailingList" 
> Subject: [Interest] Qt Screen.pixelDensity and Android devices
> Qt/Android developers,
>  
> Do you think all devices correctly report Screen.pixelDensity?
>  
> I’m working on a  HP 21 Slate and it has a pixel density of around 8.5.
>  
> The display resolution is 1920x1080. Dividing 1920 by 8.5 gives 225mm but the 
> screen has 480mm width. 
>  
> I have checked devicePixelRatio and it is one. From documentation, 
> devicePixelRatio is only for Apple screens.
>  
> So… do you think it is possible to consistently find out the size of the 
> screen on all devices?
>  
> Thanks,
>  
> Regards,
>  
> Nuno
> ___ Interest mailing list 
> Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Computer and touch screen devices used in Qt videos

[Nuno Santos]

Hi,

Does anyone knows which devices are used in Qt videos? And the respective touch 
screen devices?

Regards,

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Problems customising Slider Qt 5.7 when Qml is loaded by a loader - Object destroyed during incubation

[Nuno Santos]

Hi,

Yesterday I started exploring Qt 5.7 Quick Controls 2.0

I’m happy as it solves many problems I was having with the 1.2 controls. 

When I was about to customize the new Slider i started running into problems -> 
Object destroyed during incubation

I tried to isolate the problem but couldn’t find any reason for it. My main 
view is loaded by a loader that starts loading after a splash is show. 

If I instantiate the main view directly the Slider customisation doesn’t give 
problems. As soon as I use the loader again the Object destroyed during 
incubation is show again. 

Is anyone having this problem also?

Best regards,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Problems customising Slider Qt 5.7 when Qml is loaded by a loader - Object destroyed during incubation

[Nuno Santos]

Mitch,

Thanks for the share. It seems that this bug was reported in several forms but 
couldn’t find one that was resolved already.

Do you know if this was already sorted out by Qt team?

Regards,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

> On 26 Jul 2016, at 11:51, Mitch Curtis  wrote:
> 
> Looks like this bug: https://bugreports.qt.io/browse/QTBUG-50992 
> <https://bugreports.qt.io/browse/QTBUG-50992>
>  
> From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org] On 
> Behalf Of Nuno Santos
> Sent: Tuesday, 26 July 2016 10:56 AM
> To: Qt Project MailingList 
> Subject: [Interest] Problems customising Slider Qt 5.7 when Qml is loaded by 
> a loader - Object destroyed during incubation
>  
> Hi,
>  
> Yesterday I started exploring Qt 5.7 Quick Controls 2.0
>  
> I’m happy as it solves many problems I was having with the 1.2 controls. 
>  
> When I was about to customize the new Slider i started running into problems 
> -> Object destroyed during incubation
>  
> I tried to isolate the problem but couldn’t find any reason for it. My main 
> view is loaded by a loader that starts loading after a splash is show. 
>  
> If I instantiate the main view directly the Slider customisation doesn’t give 
> problems. As soon as I use the loader again the Object destroyed during 
> incubation is show again. 
>  
> Is anyone having this problem also?
>  
> Best regards,
>  
> Nuno Santos
> Founder / CEO / CTO
> www.imaginando.pt <http://www.imaginando.pt/>
> +351 91 621 69 62

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Statically linking an open-source application with Qt?

[Nuno Santos]

To compile and deploy a statically linked Qt you need a comercial license.

Nuno

> On 26 Jul 2016, at 16:15, Vik k  wrote:
> 
> Hey, I wrote an open source application using Qt and now I want to statically 
> link it to the Qt library. My question is, is it legal to do so?
> 
> On the website I am going to provide several download links to precompiled 
> versions of my app for Windows, Mac and Linux and a link to the GitHub 
> repository containing the source code of the application.
> 
> My application will have no about section tho (as a matter of fact it does 
> not have a menubar at all), is it also okay to write that I used Qt on the 
> website & in the GitHub repo?
> 
> Thanks,
> Vik.
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Statically linking an open-source application with Qt?

[Nuno Santos]

Vik,

I have commercial products and I want to have peaceful sleep at night, so I 
have bought the commercial license. 

Since Qt provides all the the source code and all the information to build Qt 
from source is around, of course you can do it. If it is legally permitted, I 
don’t know. I don’t have all the information to give a precise answer, sorry. 

Maybe you should contact Qt commercial team and expose your problem. 

Regards,

Nuno

> On 26 Jul 2016, at 16:27, Vik k  wrote:
> 
> Hey Nuno,
> 
> I've found this link: 
> https://stackoverflow.com/questions/12654613/static-linking-qt-with-open-source-version
>  
> <https://stackoverflow.com/questions/12654613/static-linking-qt-with-open-source-version>
> They say that I need to provide object files so user can relink the 
> application and it should be fine, in my case I provide the whole source, so 
> shouldn't it be totally fine?
> 
> Vik
> 
> On Tue, Jul 26, 2016 at 5:25 PM, Nuno Santos  <mailto:nunosan...@imaginando.pt>> wrote:
> To compile and deploy a statically linked Qt you need a comercial license.
> 
> Nuno
> 
> > On 26 Jul 2016, at 16:15, Vik k  > <mailto:digitl...@gmail.com>> wrote:
> >
> > Hey, I wrote an open source application using Qt and now I want to 
> > statically link it to the Qt library. My question is, is it legal to do so?
> >
> > On the website I am going to provide several download links to precompiled 
> > versions of my app for Windows, Mac and Linux and a link to the GitHub 
> > repository containing the source code of the application.
> >
> > My application will have no about section tho (as a matter of fact it does 
> > not have a menubar at all), is it also okay to write that I used Qt on the 
> > website & in the GitHub repo?
> >
> > Thanks,
> > Vik.
> > ___
> > Interest mailing list
> > Interest@qt-project.org <mailto:Interest@qt-project.org>
> > http://lists.qt-project.org/mailman/listinfo/interest 
> > <http://lists.qt-project.org/mailman/listinfo/interest>
> 
> 

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Statically linking an open-source application with Qt?

[Nuno Santos]

My bad then! Sorry!

Nuno

> On 27 Jul 2016, at 07:58, Jean-Michaël Celerier 
>  wrote:
> 
> 
> On Tue, Jul 26, 2016 at 5:20 PM, Olivier B. 
>  > wrote:
> I am not sure you are even able to link all Qt statically. Won't you at least 
> need platform plugins, image plugins, etc as shared libraries?
> 
> It's possible and fairly easy to do : just do ./configure -static when 
> building Qt.
> The compiler will complain as long as you don't explicitely link with all the 
> required plug-ins.
> 
> NunoSantos : this is FUD. You just need to comply to the license, be it GPL 
> or commercial. The virtue of the code being GPL prevents artificial 
> restrictions such as these.
> 
> You can even ship proprietary apps linked statically with Qt, as Vik 
> mentioned, and sleep good at night.
> 
> Best,
> Jean-Michaël
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Using QtQuickControls 2 within a static build of Qt 5.7

[Nuno Santos]

Hi,

I’m not being able to use QtQuickControls 2 in a static build of Qt. In order 
to register the QtQuick stuff within Qt 5.6 I had to manually link with the 
plugin lib and initialise the plugins manually. I think this was because of a 
bug: https://bugreports.qt.io/browse/QTBUG-35754 


Apparently the bug was fixed and I should be able to use normally however there 
are no instructions for that so I’m using same registering process I had for 
QtQuickControls with some nuances and now I have this:

Q_IMPORT_PLUGIN(QtQuickControls1Plugin)
Q_IMPORT_PLUGIN(QtQuickControls2Plugin)

…

qobject_cast(qt_static_plugin_QtQuickControls1Plugin().instance())->registerTypes("QtQuick.Controls");
qobject_cast(qt_static_plugin_QtQuickControls1Plugin().instance())->registerTypes("QtQuick.Controls.Styles");
qobject_cast(qt_static_plugin_QtQuickControls1Plugin().instance())->registerTypes("QtQuick.Controls.Private");
qobject_cast(qt_static_plugin_QtQuickControls2Plugin().instance())->registerTypes("QtQuick.Controls”);

However, it complains about not knowing nothing about, e.g. Slider. It also 
gives an error: qmlRegisterType requires absolute URLs. I have digged the 
source down and the qmlRegisterType functions has the following validation:

if (url.isRelative()) {
// User input check must go here, because QQmlPrivate::qmlregister is 
also used internally for composite types
qWarning("qmlRegisterType requires absolute URLs.");
return 0;
}

So I supposed the types end up not being registered anyway. By the time the 
plugin is registered, the following url is being passed to the first 
registration: "qrc/ApplicationWindow.qml”

What am I missing here?

Thx!

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Fwd: Google Play warning: Your app is using an incorrect implementation of in-app billing

[Nuno Santos]

I have just received the email below from Google Play. Has anyone had the same 
report?

Since I use QtPurchasing to handle my purchases, I was wondering if this 
something I need to add, or something that needs to be added to the lib itself.

Nuno
> Hello Google Play Developer,
> 
> We detected that your app(s) listed at the end of this email are invoking the 
> in-app billing service without setting a target package for the intent. This 
> can enable a malicious package to bypass the Play store billing system and 
> access items that have not been purchased.
> 
> Next Steps
> 
> If you are using IabHelper, please start using the latest SDK.
> If you are manually invoking the in-app billing service, make sure you are 
> calling Intent.setPackage(“com.android.vending”) on any intents to 
> "com.android.vending.billing.InAppBillingService.BIND".
> Sign in to your Developer Console and submit the updated version of your app.
> Check back after five hours - we’ll show a warning message if the app hasn’t 
> been updated correctly.
> We’re here to help
> 
> If you have other technical questions about the vulnerability, you can post 
> to Stack Overflow and use the tag “android-security.” For clarification on 
> steps you need to take to resolve this issue, you can contact our developer 
> support team.
> 
> Regards,
> 
> The Google Play Team
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] JIT is disabled for QML. Property bindings and animations will be very slow. Visit https://wiki.qt.io/V4 to learn about possible solutions for your platform.

[Nuno Santos]

Hi,

Since I have upgraded to Qt 5.7, the following message appears on iOS:

JIT is disabled for QML. Property bindings and animations will be very slow. 
Visit https://wiki.qt.io/V4 to learn about possible solutions for your platform.

This didn’t happened before. Was it disabled already but we didn’t knew about 
it?

Thanks,

Regards,

Nuno

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Qt 5.7 QuickControls 2 are not multitouch??

[Nuno Santos]

Hey,

One thing that made me create my own controls was the lack of multitouch 
support, this is, I cannot use two sliders at the same time. Believe me, there 
are cases in you will want that!

For my surprise, it seems that QtQuickControls 2.0 still doesn’t support 
multitouch. Am I missing something?

Thx,

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Using QtQuickControls 2 within a static build of Qt 5.7

[Nuno Santos]

Mitch,

No, I haven’t. I have been digging. This is what I found. qmake is handling 
correctly the case of a app template, generating the appropriated 
plugin_import.cpp files. However, if the template is a lib, it is not. This is 
what happens:

qmlRegisterType was saying that it requires absolute URL's. Therefore, I have 
added a qDebug() to know what was being passed in a case of a statically linked 
app. What I found was this as a baseUrl: 
qrc:/qt-project.org/imports/QtQuick/Controls.2. I have then searched for the 
source for typeUrl() which is used during the QQuickControls2Plugin 
initialization to set the selector baseUrl and for the static case that exists 
there. It was simply returning "qrc". I have changed to 
"qrc:/qt-project.org/imports/QtQuick/Controls.2". Results: it works now.
QUrl QQuickStylePlugin::typeUrl(const QString &name) const
{
#ifdef QT_STATIC
QString url = 
QLatin1String("qrc:/qt-project.org/imports/QtQuick/Controls.2") + 
baseUrl().path();
//QString url = QLatin1String("qrc") + baseUrl().path();
#else
QString url = baseUrl().toString();
#endif
if (!name.isEmpty())
url += QLatin1Char('/') + name;
return QUrl(url);
}
Obviously, this is an hack. The question is. In the case of app template, in 
which qmake generates the files and everything is done by Qt. Who fills the 
baseUrl? Why isn't the baseUrl being filled correctly in the case of a lib? I 
can live with this hack but I would prefer to use a stock version without 
hacks. Should I create a bug report regarding the qmake lib template case 
handling and this detail also?


> On 28 Jul 2016, at 13:01, Mitch Curtis  wrote:
> 
> Do you have any issues creating a standard Qt Quick Controls 2 application 
> against a static Qt? I just tried with a very basic application and it worked 
> without issues (Ubuntu 16.04, Qt 5.7).
>  
> From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org] On 
> Behalf Of Nuno Santos
> Sent: Wednesday, 27 July 2016 4:26 PM
> To: Qt Project MailingList 
> Subject: [Interest] Using QtQuickControls 2 within a static build of Qt 5.7
>  
> Hi,
>  
> I’m not being able to use QtQuickControls 2 in a static build of Qt. In order 
> to register the QtQuick stuff within Qt 5.6 I had to manually link with the 
> plugin lib and initialise the plugins manually. I think this was because of a 
> bug: https://bugreports.qt.io/browse/QTBUG-35754 
> <https://bugreports.qt.io/browse/QTBUG-35754>
>  
> Apparently the bug was fixed and I should be able to use normally however 
> there are no instructions for that so I’m using same registering process I 
> had for QtQuickControls with some nuances and now I have this:
>  
> Q_IMPORT_PLUGIN(QtQuickControls1Plugin)
> Q_IMPORT_PLUGIN(QtQuickControls2Plugin)
>  
> …
>  
> qobject_cast(qt_static_plugin_QtQuickControls1Plugin().instance())->registerTypes("QtQuick.Controls");
> qobject_cast(qt_static_plugin_QtQuickControls1Plugin().instance())->registerTypes("QtQuick.Controls.Styles");
> qobject_cast(qt_static_plugin_QtQuickControls1Plugin().instance())->registerTypes("QtQuick.Controls.Private");
> qobject_cast(qt_static_plugin_QtQuickControls2Plugin().instance())->registerTypes("QtQuick.Controls”);
>  
> However, it complains about not knowing nothing about, e.g. Slider. It also 
> gives an error: qmlRegisterType requires absolute URLs. I have digged the 
> source down and the qmlRegisterType functions has the following validation:
>  
> if (url.isRelative()) {
>   // User input check must go here, because QQmlPrivate::qmlregister 
> is also used internally for composite types
>   qWarning("qmlRegisterType requires absolute URLs.");
>   return 0;
> }
>  
> So I supposed the types end up not being registered anyway. By the time the 
> plugin is registered, the following url is being passed to the first 
> registration: "qrc/ApplicationWindow.qml”
>  
> What am I missing here?
>  
> Thx!
>  
> Nuno

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Using QtQuickControls 2 within a static build of Qt 5.7

[Nuno Santos]

I have described the problem on my last email. When the target is a lib and not 
an app things don’t happen as expected. My target is a lib and not a an app.

> On 31 Jul 2016, at 21:50, Petar Koretić  wrote:
> 
> How are you building your application?
> I can also state that I have no problems using static qt with quick controls 
> 2 (gallery example - qtquickcontrols2/examples/quickcontrols2/gallery).
> 
> On Sun, Jul 31, 2016 at 1:01 PM, Nuno Santos  <mailto:nunosan...@imaginando.pt>> wrote:
> Mitch,
> 
> No, I haven’t. I have been digging. This is what I found. qmake is handling 
> correctly the case of a app template, generating the appropriated 
> plugin_import.cpp files. However, if the template is a lib, it is not. This 
> is what happens:
> 
> qmlRegisterType was saying that it requires absolute URL's. Therefore, I have 
> added a qDebug() to know what was being passed in a case of a statically 
> linked app. What I found was this as a baseUrl: 
> qrc:/qt-project.org/imports/QtQuick/Controls.2 
> <http://qt-project.org/imports/QtQuick/Controls.2>. I have then searched for 
> the source for typeUrl() which is used during the QQuickControls2Plugin 
> initialization to set the selector baseUrl and for the static case that 
> exists there. It was simply returning "qrc". I have changed to 
> "qrc:/qt-project.org/imports/QtQuick/Controls.2 
> <http://qt-project.org/imports/QtQuick/Controls.2>". Results: it works now.
> QUrl QQuickStylePlugin::typeUrl(const QString &name) const
> {
> #ifdef QT_STATIC
> QString url = 
> QLatin1String("qrc:/qt-project.org/imports/QtQuick/Controls.2 
> <http://qt-project.org/imports/QtQuick/Controls.2>") + baseUrl().path();
> //QString url = QLatin1String("qrc") + baseUrl().path();
> #else
> QString url = baseUrl().toString();
> #endif
> if (!name.isEmpty())
> url += QLatin1Char('/') + name;
> return QUrl(url);
> }
> Obviously, this is an hack. The question is. In the case of app template, in 
> which qmake generates the files and everything is done by Qt. Who fills the 
> baseUrl? Why isn't the baseUrl being filled correctly in the case of a lib? I 
> can live with this hack but I would prefer to use a stock version without 
> hacks. Should I create a bug report regarding the qmake lib template case 
> handling and this detail also?
> 
> 
>> On 28 Jul 2016, at 13:01, Mitch Curtis > <mailto:mitch.cur...@qt.io>> wrote:
>> 
>> Do you have any issues creating a standard Qt Quick Controls 2 application 
>> against a static Qt? I just tried with a very basic application and it 
>> worked without issues (Ubuntu 16.04, Qt 5.7).
>>  
>> From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org 
>> <mailto:interest-bounces+mitch.curtis=qt...@qt-project.org>] On Behalf Of 
>> Nuno Santos
>> Sent: Wednesday, 27 July 2016 4:26 PM
>> To: Qt Project MailingList > <mailto:interest@qt-project.org>>
>> Subject: [Interest] Using QtQuickControls 2 within a static build of Qt 5.7
>>  
>> Hi,
>>  
>> I’m not being able to use QtQuickControls 2 in a static build of Qt. In 
>> order to register the QtQuick stuff within Qt 5.6 I had to manually link 
>> with the plugin lib and initialise the plugins manually. I think this was 
>> because of a bug: https://bugreports.qt.io/browse/QTBUG-35754 
>> <https://bugreports.qt.io/browse/QTBUG-35754>
>>  
>> Apparently the bug was fixed and I should be able to use normally however 
>> there are no instructions for that so I’m using same registering process I 
>> had for QtQuickControls with some nuances and now I have this:
>>  
>> Q_IMPORT_PLUGIN(QtQuickControls1Plugin)
>> Q_IMPORT_PLUGIN(QtQuickControls2Plugin)
>>  
>> …
>>  
>> qobject_cast(qt_static_plugin_QtQuickControls1Plugin().instance())->registerTypes("QtQuick.Controls");
>> qobject_cast(qt_static_plugin_QtQuickControls1Plugin().instance())->registerTypes("QtQuick.Controls.Styles");
>> qobject_cast(qt_static_plugin_QtQuickControls1Plugin().instance())->registerTypes("QtQuick.Controls.Private");
>> qobject_cast(qt_static_plugin_QtQuickControls2Plugin().instance())->registerTypes("QtQuick.Controls”);
>>  
>> However, it complains about not knowing nothing about, e.g. Slider. It also 
>> gives an error: qmlRegisterType requires absolute URLs. I have digged the 
>> source down and the qmlRegisterType functions has the following validation:
>>  
>> if (url.isRelative()) {
>>   // User input che

Re: [Interest] debug symbols in OSX application builds

[Nuno Santos]

Is this procedure valid for iOS as well? I have the same problem with my 
deployed apps. I can’t see where they crashes from crash reports. 

> On 01 Aug 2016, at 08:14, Hamish Moffatt  wrote:
> 
> Yup, got it. So it seems the correct approach for getting annotated crash 
> dumps on Mac is to extract the symbols at build time before strip, using 
> dsymutil, save the resulting .dSYM package forever, and then annotate the 
> crash dump later using Xcode, symbolicatecrash, Xsymbolicate or some other 
> tool with the saved symbols.
> 
> The hardest part seems to be annotating the dump later. Most of the tools 
> don't work.

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Qt 5.7 - iOS - module "QtGraphicalEffects" plugin "qtgraphicaleffectsplugin" not found

[Nuno Santos]

Hi,

I’m trying to use QtGraphicalEffects on iOS but i’m having:

module "QtGraphicalEffects" plugin "qtgraphicaleffectsplugin" not found

In fact it is not linking with the plugin. Is this a know problem with Qt 5.7 
and iOS??

Thanks,

Regards,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.7 - iOS - module "QtGraphicalEffects" plugin "qtgraphicaleffectsplugin" not found

[Nuno Santos]

I think I have just found a bug in qmlimportscanner.

In order to qmlimportscanner correctly include the necessary plugins, it need 
to have a Qt resources file added to the .pro resources. 

However, in my case, I have shared resources across apps. To do it so, I need 
to have a .pri which has resources. 

It seems that qmlimportscanner ignores .pri resources and it is not able to 
correctly link with the necessary plugin. 

To test this theory I have added a dummy qml file with an empty item and the 
QtGraphicalEffects import line and it launched correctly. 

Before submitting a bug I would love to have community feedback.

Best regards,

Nuno

> On 10 Aug 2016, at 17:15, Nuno Santos  wrote:
> 
> Hi,
> 
> I’m trying to use QtGraphicalEffects on iOS but i’m having:
> 
> module "QtGraphicalEffects" plugin "qtgraphicaleffectsplugin" not found
> 
> In fact it is not linking with the plugin. Is this a know problem with Qt 5.7 
> and iOS??
> 
> Thanks,
> 
> Regards,
> 
> Nuno
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.7 - iOS - module "QtGraphicalEffects" plugin "qtgraphicaleffectsplugin" not found

[Nuno Santos]

Thanks Ben for sharing your experience.

Don’t you think this behaviour should be improved? I think I will submit this a 
feature suggestion.

> On 11 Aug 2016, at 11:58, Ben Lau  wrote:
> 
> 
> I think qmlimportscanner only scan QML file within the project directory 
> regardless of is it used / referred by .pro or resource file. All QML files 
> in sibling directory will be ignored.
> 
> I have got similar problem. So far I fix it by adding extra import statement 
> in the main.qml . And leave a comment "Don't remove it" to warn other 
> developer not to remove those import statements even they are not needed by 
> main.qml.
> 
> On 11 August 2016 at 00:37, Nuno Santos  <mailto:nunosan...@imaginando.pt>> wrote:
> I think I have just found a bug in qmlimportscanner.
> 
> In order to qmlimportscanner correctly include the necessary plugins, it need 
> to have a Qt resources file added to the .pro resources. 
> 
> However, in my case, I have shared resources across apps. To do it so, I need 
> to have a .pri which has resources. 
> 
> It seems that qmlimportscanner ignores .pri resources and it is not able to 
> correctly link with the necessary plugin. 
> 
> To test this theory I have added a dummy qml file with an empty item and the 
> QtGraphicalEffects import line and it launched correctly. 
> 
> Before submitting a bug I would love to have community feedback.
> 
> Best regards,
> 
> Nuno
> 
>> On 10 Aug 2016, at 17:15, Nuno Santos > <mailto:nunosan...@imaginando.pt>> wrote:
>> 
>> Hi,
>> 
>> I’m trying to use QtGraphicalEffects on iOS but i’m having:
>> 
>> module "QtGraphicalEffects" plugin "qtgraphicaleffectsplugin" not found
>> 
>> In fact it is not linking with the plugin. Is this a know problem with Qt 
>> 5.7 and iOS??
>> 
>> Thanks,
>> 
>> Regards,
>> 
>> Nuno
>> ___
>> Interest mailing list
>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>> http://lists.qt-project.org/mailman/listinfo/interest 
>> <http://lists.qt-project.org/mailman/listinfo/interest>
> 
> 
> ___
> Interest mailing list
> Interest@qt-project.org <mailto:Interest@qt-project.org>
> http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
> 
> 

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.7 - iOS - module "QtGraphicalEffects" plugin "qtgraphicaleffectsplugin" not found

[Nuno Santos]

I have created the following bug report:

https://bugreports.qt.io/browse/QTBUG-55259 


> On 11 Aug 2016, at 14:05, Ben Lau  wrote:
> 
> 
> 
> On 11 August 2016 at 20:54, J-P Nurmi mailto:jpnu...@qt.io>> 
> wrote:
>> On 11 Aug 2016, at 14:43, Ben Lau > > wrote:
>> 
>> 
>> I think so. I would suggest to add a new variable called "QML_SCAN_PATH" for 
>> qmake. And let's qmlimportscanner scan those directory too. Moreover, due to 
>> QTBUG-48480, it may also need a variable QML_EXCLUDE_SCAN_PATH too.
>> 
>> [QTBUG-48480] Qt5QuickTest should not be linked in iOS target for non-unit 
>> test program - Qt Bug Tracker 
> There’s already QML_IMPORT_PATH that is only (?) used by Qt Creator for 
> resolving imports. Perhaps the same variable could be used for 
> qmlimportscanner...
> 
> --
> J-P Nurmi
> 
> 
> I just thought QML_IMPORT_PATH will also include system QML path. But it 
> don't. So it should be a good idea to use QML_IMPORT_PATH. 
> 
> p.s I still need a variable like QML_EXCLUDE_PATH to fix QTBUG-48480.
> 
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Receiving audio through USB frame grabber and playing it

[Nuno Santos]

SampleType defines how each sample is represented, the min and max value.

For instance, in my audio applications, I use floating point sample type 
because I wan’t to generate samples between -1 and 1. 

Working with a normalised value is a very convenient way of making 
calculations, but on some system you might prefer to use another type..

It’s up to you. You just need to be consistent. If you say that the Sample Type 
is unsigned int, you must ensure that the boundaries of your values are in 
between the max and mim values of the type you choose.

Nuno

> On 12 Aug 2016, at 07:32, Anisha Kaul  wrote:
> 
> Thanks for the response and apologies for my error. 
> 
> This morning I discovered that I was able to hear on 24 bit samples but not 
> on 16 bit sample because I hadn't raised volume to its maximum.
> 
> Now, with 16 bit samples I am able to hear the "buzzing sound". Nothing more 
> than that.
> 
> Now the settings are as follows:
> desiredFormat1.setChannelCount(2);
> desiredFormat1.setCodec("audio/pcm");
> desiredFormat1.setSampleType(QAudioFormat::UnSignedInt);
> desiredFormat1.setSampleRate(44100);
> desiredFormat1.setSampleSize(16);
> 
> 
> I do not know whether I use unsigned int, or signed int? How is that decided? 
> anyways I tried both, it didn't work.
> 
> On 12 August 2016 at 11:01, Maurice Kalinowski  > wrote:
> Have you considered converting manually between 16 and 24 bit samplesizes?
> 
>  
> 
> Obviously you pass the wrong sample size to the output, and that one takes 
> data as is as this is just a byte stream. That is why you need to check that 
> either the formats are compatible or do a conversion. This is nothing Qt 
> Multimedia should handle by default.
> 
>  
> 
> “but input works only with 16 and output only with 24.”
> 
> How did you identify/verify this?
> 
>  
> 
> Maurice
> 
>  
> 
>   <>
> From: Interest [mailto:interest-bounces+maurice.kalinowski 
> =qt...@qt-project.org 
> ] On Behalf Of Anisha Kaul
> Sent: Thursday, August 11, 2016 5:40 PM
> To: interest@qt-project.org 
> Subject: [Interest] Receiving audio through USB frame grabber and playing it
> 
>  
> 
>  
> 
> HI, 
> 
>  
> 
> Following is the re-producable example:
> 
>  
> 
> **header file:
> 
>  
> 
> #ifndef AUDIOOUTPUT
> 
> #define AUDIOOUTPUT
> 
> 
> 
> #include 
> 
> #include 
> 
> #include 
> 
> 
> 
> class Output: public QObject
> 
> {
> 
> private:
> 
> Q_OBJECT
> 
> 
> 
> public:
> 
> Output();
> 
> ~Output() {}
> 
> 
> 
> QAudioOutput* audioOutpu;
> 
> QAudioInput* audioInpu;
> 
> 
> 
> public slots:
> 
> handleStateChanged(QAudio::State newState);
> 
> handleStateChanged0(QAudio::State newState);
> 
> };
> 
> 
> 
> #endif // AUDIOOUTPUT
> 
>  
> 
>  
> 
> **Source file:*
> 
>  
> 
> #include 
> 
> #include "audiooutput.h"
> 
> 
> 
> Output::Output()
> 
> {
> 
> foreach (const QAudioDeviceInfo &deviceInfo, 
> QAudioDeviceInfo::availableDevices(QAudio::AudioInput))
> 
> qDebug() << "Device name in: " << deviceInfo.deviceName();
> 
> 
> 
> foreach (const QAudioDeviceInfo &deviceInfo, 
> QAudioDeviceInfo::availableDevices(QAudio::AudioOutput))
> 
> qDebug() << "Device name out: " << deviceInfo.deviceName();
> 
> 
> 
> QAudioDeviceInfo d;
> 
> QList l = d.availableDevices(QAudio::AudioInput);
> 
> 
> 
> qDebug() << l.first().supportedCodecs();
> 
> qDebug() << l.first().supportedChannelCounts();
> 
> qDebug() << l.first().supportedSampleTypes();
> 
> qDebug() << l.first().supportedSampleRates();
> 
> qDebug() << l.first().supportedSampleSizes();
> 
> 
> 
> QAudioFormat desiredFormat;
> 
> desiredFormat.setChannelCount(5);
> 
> desiredFormat.setCodec("audio/pcm");
> 
> desiredFormat.setSampleType(QAudioFormat::SignedInt);
> 
> desiredFormat.setSampleRate(44100);
> 
> desiredFormat.setSampleSize(16);
> 
> 
> 
> QAudioDeviceInfo info(l.first());
> 
> if (!info.isFormatSupported(desiredFormat)) {
> 
>qWarning() << "Default format not supported, trying to use the 
> nearest.";
> 
>desiredFormat = info.nearestFormat(desiredFormat);
> 
>}
> 
> 
> 
> audioInpu = new QAudioInput(l.first(), desiredFormat, this);
> 
> connect(audioInpu, SIGNAL(stateChanged(QAudio::State)), this, 
> SLOT(handleStateChanged0(QAudio::State)));
> 
> audioInpu->setVolume(500);
> 
> 
> 
> QAudioDeviceInfo d1;
> 
> QList l1 = d1.availableDevices(QAudio::AudioOut

[Interest] Qt 5.7 Android - Keyboard keeps popping up after sending it down

[Nuno Santos]

Hi,

I’m having a problem with keyboard input on Android. When I select an input 
box, the keyboard pops in. After typing I press the keyboard button to send it 
down but it insists in popping up.

Has anyone had this issue? I think I hadn’t this issue on Qt 5.6. 

Any suggestions?

Thanks,

Regards,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.7 Android - Keyboard keeps popping up after sending it down

[Nuno Santos]

Curiously, it doesn’t happen on a simple project with just an TextInput. 
However, it happens in my project where I have the TextInput wrapped in another 
items. I can’t seem to find the relation between the problem and the context.

> On 16 Aug 2016, at 13:07, ekke gentz  wrote:
> 
> 
> just tried in one of my apps
> Qt5.7 QtQuickControls2 
> works as expected
> from BlackBerry Virtual keyboard
> Android 6.0.1
> 
> have you tried another keyboard ?
> 
> Von meinem BlackBerry gesendet – dem sichersten Smartphone für Android oder 
> BlackBerry 10
> Von:nunosan...@imaginando.pt
> Gesendet:16. August 2016 1:54 nachm.
> An:interest@qt-project.org
> Betreff:[Interest] Qt 5.7 Android - Keyboard keeps popping up after sending 
> it down
> 
> Hi,
> 
> I’m having a problem with keyboard input on Android. When I select an input 
> box, the keyboard pops in. After typing I press the keyboard button to send 
> it down but it insists in popping up.
> 
> Has anyone had this issue? I think I hadn’t this issue on Qt 5.6. 
> 
> Any suggestions?
> 
> Thanks,
> 
> Regards,
> 
> Nuno
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.7 Android - Keyboard keeps popping up after sending it down

[Nuno Santos]

What kind of items can do that?

I’m now using a standard TextInput on my MainView and the problem contains. 

Still digging...

> On 16 Aug 2016, at 16:20, ekke gentz  wrote:
> 
> perhaps your textfield is in an Item grabbing the focus and so you cannot 
> leave the field
> 
> Von meinem BlackBerry gesendet – dem sichersten Smartphone für Android oder 
> BlackBerry 10
> Von:nunosan...@imaginando.pt
> Gesendet:16. August 2016 5:10 nachm.
> An:e...@ekkes-corner.org
> Cc:interest@qt-project.org
> Betreff:Re: [Interest] Qt 5.7 Android - Keyboard keeps popping up after 
> sending it down
> 
> Curiously, it doesn’t happen on a simple project with just an TextInput. 
> However, it happens in my project where I have the TextInput wrapped in 
> another items. I can’t seem to find the relation between the problem and the 
> context.
> 
>> On 16 Aug 2016, at 13:07, ekke gentz > > wrote:
>> 
> 
> 
> just tried in one of my apps
> Qt5.7 QtQuickControls2 
> works as expected
> from BlackBerry Virtual keyboard
> Android 6.0.1
> 
> have you tried another keyboard ?
> 
> Von meinem BlackBerry gesendet – dem sichersten Smartphone für Android oder 
> BlackBerry 10
> Von:nunosan...@imaginando.pt 
> Gesendet:16. August 2016 1:54 nachm.
> An:interest@qt-project.org 
> Betreff:[Interest] Qt 5.7 Android - Keyboard keeps popping up after sending 
> it down
> 
> Hi,
> 
> I’m having a problem with keyboard input on Android. When I select an input 
> box, the keyboard pops in. After typing I press the keyboard button to send 
> it down but it insists in popping up.
> 
> Has anyone had this issue? I think I hadn’t this issue on Qt 5.6. 
> 
> Any suggestions?
> 
> Thanks,
> 
> Regards,
> 
> Nuno
> ___
> Interest mailing list
> Interest@qt-project.org 
> http://lists.qt-project.org/mailman/listinfo/interest
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.7 Android - Keyboard keeps popping up after sending it down

[Nuno Santos]

Found the problem… 

I have a fake touches injector on my app so that the cpu doesn’t scale down.

Since the TextInput is still selected, every time the fake touch is injected, 
it pops in again. I need to release the focus of the TextInput item after 
closing the keyboard.

> On 16 Aug 2016, at 17:49, Nuno Santos  wrote:
> 
> What kind of items can do that?
> 
> I’m now using a standard TextInput on my MainView and the problem contains. 
> 
> Still digging...
> 
>> On 16 Aug 2016, at 16:20, ekke gentz > <mailto:e...@ekkes-corner.org>> wrote:
>> 
>> perhaps your textfield is in an Item grabbing the focus and so you cannot 
>> leave the field
>> 
>> Von meinem BlackBerry gesendet – dem sichersten Smartphone für Android oder 
>> BlackBerry 10
>> Von:nunosan...@imaginando.pt <mailto:nunosan...@imaginando.pt>
>> Gesendet:16. August 2016 5:10 nachm.
>> An:e...@ekkes-corner.org <mailto:e...@ekkes-corner.org>
>> Cc:interest@qt-project.org <mailto:interest@qt-project.org>
>> Betreff:Re: [Interest] Qt 5.7 Android - Keyboard keeps popping up after 
>> sending it down
>> 
>> Curiously, it doesn’t happen on a simple project with just an TextInput. 
>> However, it happens in my project where I have the TextInput wrapped in 
>> another items. I can’t seem to find the relation between the problem and the 
>> context.
>> 
>>> On 16 Aug 2016, at 13:07, ekke gentz >> <mailto:e...@ekkes-corner.org>> wrote:
>>> 
>> 
>> 
>> just tried in one of my apps
>> Qt5.7 QtQuickControls2 
>> works as expected
>> from BlackBerry Virtual keyboard
>> Android 6.0.1
>> 
>> have you tried another keyboard ?
>> 
>> Von meinem BlackBerry gesendet – dem sichersten Smartphone für Android oder 
>> BlackBerry 10
>> Von:nunosan...@imaginando.pt <mailto:nunosan...@imaginando.pt>
>> Gesendet:16. August 2016 1:54 nachm.
>> An:interest@qt-project.org <mailto:interest@qt-project.org>
>> Betreff:[Interest] Qt 5.7 Android - Keyboard keeps popping up after sending 
>> it down
>> 
>> Hi,
>> 
>> I’m having a problem with keyboard input on Android. When I select an input 
>> box, the keyboard pops in. After typing I press the keyboard button to send 
>> it down but it insists in popping up.
>> 
>> Has anyone had this issue? I think I hadn’t this issue on Qt 5.6. 
>> 
>> Any suggestions?
>> 
>> Thanks,
>> 
>> Regards,
>> 
>> Nuno
>> ___
>> Interest mailing list
>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>> http://lists.qt-project.org/mailman/listinfo/interest 
>> <http://lists.qt-project.org/mailman/listinfo/interest>
>> 
>> ___
>> Interest mailing list
>> Interest@qt-project.org <mailto:Interest@qt-project.org>
>> http://lists.qt-project.org/mailman/listinfo/interest
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Qt Android / InputMethod / Instrumentation Fake Keyboard Input

[Nuno Santos]

Hi,

One of my apps is an audio app. As many know, Android has audio problems. One 
of the hacks used to avoid glitching and crackling in the sound is to fake user 
input to avoid CPU frequency downscaling. 

This hack raises another problem. When I tap on a TextInput the Android 
keyboard pops in. When I finish my writing I press the enter key and its gets 
down but the fake input is making it pop again. 

I already have installed a eventFilter to make my qt app ignore the fake input 
but the keyboard insistis in popping up even when the TextInput hasn’t the 
focus anymore.

I can’t seem to find a consistent workaround for this. 

Any help would be appreciated.

Best regards,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Qt Android Service example

[Nuno Santos]

Hi,

Is there any public example on how to do a Qt Android Service?

Thanks,

Regards,

Nuno

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt Android Service example

[Nuno Santos]

I have come across this page by searching in google for qt android service but 
this isn’t a complete example...

> On 17 Aug 2016, at 19:56, Jason H  wrote:
> 
> Should be, only since 5.7
> http://doc.qt.io/qt-5/androidservices.html
>  
> Sent: Wednesday, August 17, 2016 at 1:02 PM
> From: "Nuno Santos" 
> To: "Qt Project MailingList" 
> Subject: [Interest] Qt Android Service example
> Hi,
>  
> Is there any public example on how to do a Qt Android Service?
>  
> Thanks,
>  
> Regards,
>  
> Nuno
> ___ Interest mailing list 
> Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt Android Service example

[Nuno Santos]

Can you provide me an example on how to do it? 

> On 18 Aug 2016, at 15:02, Jason H  wrote:
> 
> It is kinda jarring how they drop you off into the Android documentation like 
> that.
>  
> What I have is a Qt app (QtAppplication, QtActivity) with a Android service. 
>  
> Sent: Wednesday, August 17, 2016 at 5:41 PM
> From: "Nuno Santos" 
> To: "Jason H" 
> Cc: "Qt Project MailingList" 
> Subject: Re: [Interest] Qt Android Service example
> I have come across this page by searching in google for qt android service 
> but this isn’t a complete example...
>  
> On 17 Aug 2016, at 19:56, Jason H > 
> wrote:
>  
> Should be, only since 5.7
> http://doc.qt.io/qt-5/androidservices.html 
> <http://doc.qt.io/qt-5/androidservices.html>
>  
> Sent: Wednesday, August 17, 2016 at 1:02 PM
> From: "Nuno Santos"  >
> To: "Qt Project MailingList"  >
> Subject: [Interest] Qt Android Service example
> Hi,
>  
> Is there any public example on how to do a Qt Android Service?
>  
> Thanks,
>  
> Regards,
>  
> Nuno
> ___ Interest mailing list 
> Interest@qt-project.org  
> http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt Android Service example

[Nuno Santos]

Really simple stuff. I need a background service that injects input events on 
the system to avoid CPU scaling down. For that I use the instrumentation class.

> On 18 Aug 2016, at 16:20, Jason H  wrote:
> 
> Let's backup. What are you trying to do with a service?
>  
> Sent: Thursday, August 18, 2016 at 10:13 AM
> From: "Nuno Santos" 
> To: "Jason H" 
> Cc: "Qt Project MailingList" 
> Subject: Re: [Interest] Qt Android Service example
> Can you provide me an example on how to do it? 
>  
> On 18 Aug 2016, at 15:02, Jason H > 
> wrote:
>  
> It is kinda jarring how they drop you off into the Android documentation like 
> that.
>  
> What I have is a Qt app (QtAppplication, QtActivity) with a Android service. 
>  
> Sent: Wednesday, August 17, 2016 at 5:41 PM
> From: "Nuno Santos"  >
> To: "Jason H" >
> Cc: "Qt Project MailingList"  >
> Subject: Re: [Interest] Qt Android Service example
> I have come across this page by searching in google for qt android service 
> but this isn’t a complete example...
>  
> On 17 Aug 2016, at 19:56, Jason H > wrote:
>  
> Should be, only since 5.7
> http://doc.qt.io/qt-5/androidservices.html 
> <http://doc.qt.io/qt-5/androidservices.html>
>  
> Sent: Wednesday, August 17, 2016 at 1:02 PM
> From: "Nuno Santos" >
> To: "Qt Project MailingList" >
> Subject: [Interest] Qt Android Service example
> Hi,
>  
> Is there any public example on how to do a Qt Android Service?
>  
> Thanks,
>  
> Regards,
>  
> Nuno
> ___ Interest mailing list 
> Interest@qt-project.org <> 
> http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Location when the App is Killed/Terminated/Suspended

[Nuno Santos]

I think didFinishLaunchingWithOptions will only get called when the app is 
first loaded. 

Have you tried the following ones?

- (void)applicationWillResignActive:(UIApplication *)application;
- (void)applicationDidEnterBackground:(UIApplication *)application;
-(void)applicationWillTerminate:(UIApplication *)application;

Nuno

> On 22 Aug 2016, at 23:19, Manoel Neto  wrote:
> 
> Hi Jason, thanks for your reply. My problem is not how to build
> AppDelegate (I did this and it is ok  when the app is active or in
> background.). The question is: how to call
> didFinishLaunchingWithOptions "when the ap is Killed, suspended or
> terminated." ? Apple says that if an app uses "The significant-change
> location service", iOS will wake it up if there's a location update to
> be delivered, even if the app is terminated. But i cant make it work
> using QT.
> 
> Best R,
> 
> Manoel
> 
> On Mon, Aug 22, 2016 at 6:54 PM, Jason H  > wrote:
>> @implementation QtAppDelegate
>> 
>> +(QtAppDelegate *)sharedQtAppDelegate{
>>static dispatch_once_t pred;
>>static QtAppDelegate *shared = nil;
>>dispatch_once(&pred, ^{
>>shared = [[super alloc] init];
>>});
>>return shared;
>> }
>> 
>> ...
>> 
>> 
>> void QtAppDelegateInitialize()
>> {
>>[[UIApplication sharedApplication] setDelegate:[QtAppDelegate 
>> sharedQtAppDelegate]];
>> }
>> 
>> 
>> // int main() {
>> 
>> #if defined(Q_OS_IOS)
>>QtAppDelegateInitialize();
>> #endif
>> 
>> 
>>> Sent: Monday, August 22, 2016 at 4:47 PM
>>> From: "Manoel Neto" 
>>> To: interest@qt-project.org
>>> Subject: [Interest] Location when the App is Killed/Terminated/Suspended
>>> 
>>> Hi ,
>>>   I'm building an APP using QT/QML for IOS / Android and need to use
>>> location when the APP is Killed, suspended or terminated. For IOS i
>>> did an Objective C implementation and used
>>> startMonitoringSignificantLocationChanges method  from
>>> CLLocationManager class.
>>> 
>>> Briefly, I extended the QIOSApplicationDelegate to have access to the
>>> didFinishLaunchingWithOptions method. There i check the option key "
>>> UIApplicationLaunchOptionsLocationKey" and, if ok, start monitoring
>>> Location using a LocationManager Delegate. The Background App Refresh
>>> is enable for the Location updates to work in the background.
>>> 
>>> I folow an example code (in IOS) tha works great even when the app is
>>> Killed, suspended or terminated.  The only diference from my QT code
>>> is that in QT i use QIOSApplicationDelegate instead of system delegate
>>> in IOS. But in QT the didFinishLaunchingWithOptions is never called
>>> when the ap is Killed, suspended or terminated.
>>> 
>>> - (BOOL)application:(UIApplication *)application
>>> didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
>>> .
>>>shareModel = [LocationManager sharedManager];
>>>   if ([launchOptions 
>>> objectForKey:UIApplicationLaunchOptionsLocationKey]) {
>>>[shareModel startMonitoringLocation];
>>>   }
>>> }
>>> 
>>> Any suggestion?
>>> 
>>> Best R,
>>> Manoel
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Manoel Carvalho Marques Neto
>>> manoelne...@gmail.com
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/interest
>>> 
> 
> 
> 
> -- 
> Manoel Carvalho Marques Neto
> manoelne...@gmail.com 
> ___
> Interest mailing list
> Interest@qt-project.org 
> http://lists.qt-project.org/mailman/listinfo/interest 
> 
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Location when the App is Killed/Terminated/Suspended

[Nuno Santos]

Manoel,

Maybe you need to enable a specific capability. For instance, in audio, to have 
audio being played when the app is suspended you need to enable background 
audio. Sometimes, this capabilities are only possible being enabled by using 
xcode, therefore you need to use qmake to generate the xcode project.

Also, have you seen my last email? To know when the app is terminated or 
suspended you need to implement this calls on your app delegate:

- (void)applicationWillResignActive:(UIApplication *)application;
- (void)applicationDidEnterBackground:(UIApplication *)application;
-(void)applicationWillTerminate:(UIApplication *)application;

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

> On 23 Aug 2016, at 13:21, Manoel Neto  wrote:
> 
> Hi Jason,
>Thanks again for your interest in my problem. But as i said, i did
> my Delegate and it works good. I did something like this:
> 
> #include 
> 
> @interface QIOSApplicationDelegate
> 
> @end
> 
> 
> @interface QIOSApplicationDelegate(QtAppDelegate) // Put here the name
> of your delegate...i used "QtAppDelegate"
> 
> @end
> 
> 
> @implementation QIOSApplicationDelegate (QtAppDelegate)
> 
> - (BOOL)application:(UIApplication *)application
> didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
> 
> {
> 
> NSLog(@"It Works!! When the app did finish launch ");
> 
> return YES;
> 
> }
> @end
> 
> Using this code, you dont have to set the delegate in main. It works
> perfectly ONLY WHEN the APP is in FOREGROUND /ACTIVE or in BACKGROUND.
> My problem is that i need to use this delegate to get LOCATION when
> the app is KILLED/TERMINATED/SUSPENDED.
> 
> See this link 
> http://mobileoop.com/getting-location-updates-for-ios-7-and-8-when-the-app-is-killedterminatedsuspended.
> Here the author gives an example of how to do this using Objective C.
> I did the same example using QT...the code compiles and run perfectly
> ony when the app is  FOREGROUND /ACTIVE or in BACKGROUND...but not
> when the app is KILLED/TERMINATED/SUSPENDED.
> 
> Any idea?
> 
> Best R,
> 
> Manoel
> 
> On Tue, Aug 23, 2016 at 12:08 AM, Jason H  wrote:
>> See also: https://bugreports.qt.io/browse/QTBUG-38184
>> 
>> 
>> Sent: Monday, August 22, 2016 at 11:04 PM
>> From: "Jason H" 
>> To: "Nuno Santos" 
>> Cc: interest@qt-project.org
>> 
>> Subject: Re: [Interest] Location when the App is Killed/Terminated/Suspended
>> I wish I understood more about this:
>> 
>> 
>> QIOSIntegration::QIOSIntegration()
>> 
>>: m_fontDatabase(new QCoreTextFontDatabase)
>> 
>>, m_clipboard(new QIOSClipboard)
>> 
>>, m_inputContext(0)
>> 
>>, m_platformServices(new QIOSServices)
>> 
>>, m_accessibility(0)
>> 
>>, m_debugWindowManagement(false)
>> 
>> {
>> 
>>if (![UIApplication sharedApplication]) {
>> 
>>qFatal("Error: You are creating QApplication before calling
>> UIApplicationMain.\n" \
>> 
>>   "If you are writing a native iOS application, and only want
>> to use Qt for\n" \
>> 
>>   "parts of the application, a good place to create
>> QApplication is from within\n" \
>> 
>>   "'applicationDidFinishLaunching' inside your UIApplication
>> delegate.\n");
>> 
>>}
>> 
>> Thre is also:
>> 
>> @implementation QIOSApplicationDelegate
>> 
>> - (BOOL)application:(UIApplication *)application openURL:(NSURL *)url
>> sourceApplication:(NSString *)sourceApplication annotation:(id)annotation
>> 
>> {
>> 
>>Q_UNUSED(application);
>> 
>>Q_UNUSED(sourceApplication);
>> 
>>Q_UNUSED(annotation);
>> 
>> 
>> 
>>if (!QGuiApplication::instance())
>> 
>>return NO;
>> 
>> 
>> 
>>QIOSIntegration *iosIntegration = QIOSIntegration::instance();
>> 
>>Q_ASSERT(iosIntegration);
>> 
>> 
>> 
>>QIOSServices *iosServices = static_cast> *>(iosIntegration->services());
>> 
>> 
>> 
>>return iosServices->handleUrl(QUrl::fromNSURL(url));
>> 
>> }
>> 
>> 
>> 
>> @end
>> 
>> 
>> 
>> Which makes me thing you need to inherit from QIOSApplicationDelegate wiht
>> your delegate and somehow assign your delegate to be the application
>> delegate.
>> 
>> But I don't know much about iOS internals.
>>

[Interest] Qt Android App and Notifications - Black screen after tapping a notification with app open on background.

[Nuno Santos]

Hi,

When my app has a notification I want to tap on the notification and open the 
app. If the app is closed, it works correctly. When the app is open in the 
background, it gets a black screen.

Has anyone had this problem in the past? Any suggestion?

Thanks,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Includue Additional PLISTs?

[Nuno Santos]

A plist is a resource like any other. For instance, an icon is a resource and 
I’m including the icons with qmake this way:

ios_icon.files = $$files($$PWD/ios/icons/AppIcon*.png)
QMAKE_BUNDLE_DATA += ios_icon

Hope this helps! ;)

Nuno

> On 30 Aug 2016, at 16:25, Jason H  wrote:
> 
> I am integrating Google Cloud Messaging, and need to include a 
> GoogleService-Info.plist file.
> I currently get the error: Could not locate configuration file: 
> 'GoogleService-Info.plist'.
> 
> How can I tell qmake to include it? I already have an Info.plist.
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt Android App and Notifications - Black screen after tapping a notification with app open on background.

[Nuno Santos]

My launch mode is singleTop. I had singleTask but I have changed to singleTop 
without success. I don’t know the reason for having singleTask. I don’t 
remember. 
Also, I use Parse to receive and handle push notifications so I have the 
following filter to change the background color of the notification on Lollipop

import com.parse.ParsePushBroadcastReceiver;
import android.app.Notification;
import android.content.Context;
import android.content.Intent;
import android.os.Build;
import android.util.Log;

public class IPushBroadcastReceiver extends ParsePushBroadcastReceiver
{
@Override
protected Notification getNotification(Context context, Intent intent)
{
Notification notification = super.getNotification(context, intent);

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP)
{
notification.color = 0xff00;
}

return notification;
}
}

> On 30 Aug 2016, at 16:28, Jason H  wrote:
> 
> I don't have a problem with notifcations like that.
> What are you doing to bring your activity to the front?
> I'd suspect you start an intent, and have the SINGLE_TOP flag on the 
> activity, or something like that?
>  
> Sent: Tuesday, August 30, 2016 at 11:12 AM
> From: "Nuno Santos" 
> To: "Qt Project MailingList" 
> Subject: [Interest] Qt Android App and Notifications - Black screen after 
> tapping a notification with app open on background.
> Hi,
>  
> When my app has a notification I want to tap on the notification and open the 
> app. If the app is closed, it works correctly. When the app is open in the 
> background, it gets a black screen.
>  
> Has anyone had this problem in the past? Any suggestion?
>  
> Thanks,
>  
> Nuno
> ___ Interest mailing list 
> Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt Android App and Notifications - Black screen after tapping a notification with app open on background.

[Nuno Santos]

None. Everything is done by Parse SDK. But in the snippet bellow I can override 
things.

> On 30 Aug 2016, at 17:03, Jason H  wrote:
> 
> What code are you using to show your activity from the notification?
>  
> Sent: Tuesday, August 30, 2016 at 11:32 AM
> From: "Nuno Santos" 
> To: "Jason H" 
> Cc: "Qt Project MailingList" 
> Subject: Re: [Interest] Qt Android App and Notifications - Black screen after 
> tapping a notification with app open on background.
> My launch mode is singleTop. I had singleTask but I have changed to singleTop 
> without success. I don’t know the reason for having singleTask. I don’t 
> remember. 
> Also, I use Parse to receive and handle push notifications so I have the 
> following filter to change the background color of the notification on 
> Lollipop
>  
> import com.parse.ParsePushBroadcastReceiver;
> import android.app.Notification;
> import android.content.Context;
> import android.content.Intent;
> import android.os.Build;
> import android.util.Log;
>  
> public class IPushBroadcastReceiver extends ParsePushBroadcastReceiver
> {
> @Override
> protected Notification getNotification(Context context, Intent intent)
> {
> Notification notification = super.getNotification(context, intent);
>  
> if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP)
> {
> notification.color = 0xff00;
> }
>  
> return notification;
> }
> }
>  
>  
> On 30 Aug 2016, at 16:28, Jason H > 
> wrote:
>  
> I don't have a problem with notifcations like that.
> What are you doing to bring your activity to the front?
> I'd suspect you start an intent, and have the SINGLE_TOP flag on the 
> activity, or something like that?
>  
> Sent: Tuesday, August 30, 2016 at 11:12 AM
> From: "Nuno Santos"  >
> To: "Qt Project MailingList"  >
> Subject: [Interest] Qt Android App and Notifications - Black screen after 
> tapping a notification with app open on background.
> Hi,
>  
> When my app has a notification I want to tap on the notification and open the 
> app. If the app is closed, it works correctly. When the app is open in the 
> background, it gets a black screen.
>  
> Has anyone had this problem in the past? Any suggestion?
>  
> Thanks,
>  
> Nuno
> ___ Interest mailing list 
> Interest@qt-project.org  
> http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Includue Additional PLISTs?

[Nuno Santos]

Yeah! ;)

> On 30 Aug 2016, at 17:03, Jason H  wrote:
> 
> Thanks, I got this working :-)
>  
> Sent: Tuesday, August 30, 2016 at 11:30 AM
> From: "Nuno Santos" 
> To: "Jason H" 
> Cc: "Interests Qt" 
> Subject: Re: [Interest] Includue Additional PLISTs?
> A plist is a resource like any other. For instance, an icon is a resource and 
> I’m including the icons with qmake this way:
>  
> ios_icon.files = $$files($$PWD/ios/icons/AppIcon*.png)
> QMAKE_BUNDLE_DATA += ios_icon
>  
> Hope this helps! ;)
>  
> Nuno
>  
> On 30 Aug 2016, at 16:25, Jason H > 
> wrote:
>  
> I am integrating Google Cloud Messaging, and need to include a 
> GoogleService-Info.plist file.
> I currently get the error: Could not locate configuration file: 
> 'GoogleService-Info.plist'.
> 
> How can I tell qmake to include it? I already have an Info.plist.
> 
> ___
> Interest mailing list
> Interest@qt-project.org 
> http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt Android App and Notifications - Black screen after tapping a notification with app open on background.

[Nuno Santos]

I have the following error:

error: no suitable constructor found for 
Intent(IPushBroadcastReceiver,Class)

It seems not being able to consider my activity class valid. What am I doing 
wrong?

> On 30 Aug 2016, at 17:19, Jason H  wrote:
> 
> I sent incomplete Code before:
> This is  how I set the Notification:
> private void displayNotification(final String message) {
>Intent notificationIntent = new Intent(this, MyQtActivity.class);
>notificationIntent.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP | 
> Intent.FLAG_ACTIVITY_SINGLE_TOP);
>int requestID = (int) System.currentTimeMillis();
>PendingIntent contentIntent = PendingIntent.getActivity(this, requestID, 
> notificationIntent,
>  PendingIntent.FLAG_UPDATE_CURRENT);
> 
>// Display a notification with an icon, message as content, and default 
> sound. It also
>// opens the app when the notification is clicked.
>NotificationCompat.Builder builder = new 
> NotificationCompat.Builder(this).setSmallIcon(
>  R.drawable.icon)
>  .setContentTitle(getString(R.string.push_demo_title))
>  .setContentText(message)
>  .setDefaults(Notification.DEFAULT_SOUND)
>  .setAutoCancel(true)
>  .setContentIntent(contentIntent);
> 
>NotificationManager notificationManager = (NotificationManager) 
> getSystemService(Context.NOTIFICATION_SERVICE);
> 
>notificationManager.notify(0, builder.build());
> }
>  
> But I don't know how Parse handles it. I might try to take the 
> notificationIntent above and just startIntent() it from the handler and see 
> what you get.
>  
> Sent: Tuesday, August 30, 2016 at 12:04 PM
> From: "Nuno Santos" 
> To: "Jason H" 
> Cc: "Qt Project MailingList" 
> Subject: Re: [Interest] Qt Android App and Notifications - Black screen after 
> tapping a notification with app open on background.
> None. Everything is done by Parse SDK. But in the snippet bellow I can 
> override things.
>  
>  
> On 30 Aug 2016, at 17:03, Jason H > 
> wrote:
>  
> What code are you using to show your activity from the notification?
>  
> Sent: Tuesday, August 30, 2016 at 11:32 AM
> From: "Nuno Santos"  >
> To: "Jason H" >
> Cc: "Qt Project MailingList"  >
> Subject: Re: [Interest] Qt Android App and Notifications - Black screen after 
> tapping a notification with app open on background.
> My launch mode is singleTop. I had singleTask but I have changed to singleTop 
> without success. I don’t know the reason for having singleTask. I don’t 
> remember. 
> Also, I use Parse to receive and handle push notifications so I have the 
> following filter to change the background color of the notification on 
> Lollipop
>  
> import com.parse.ParsePushBroadcastReceiver;
> import android.app.Notification;
> import android.content.Context;
> import android.content.Intent;
> import android.os.Build;
> import android.util.Log;
>  
> public class IPushBroadcastReceiver extends ParsePushBroadcastReceiver
> {
> @Override
> protected Notification getNotification(Context context, Intent intent)
> {
> Notification notification = super.getNotification(context, intent);
>  
> if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP)
> {
> notification.color = 0xff00;
> }
>  
> return notification;
> }
> }
>  
>  
> On 30 Aug 2016, at 16:28, Jason H > wrote:
>  
> I don't have a problem with notifcations like that.
> What are you doing to bring your activity to the front?
> I'd suspect you start an intent, and have the SINGLE_TOP flag on the 
> activity, or something like that?
>  
> Sent: Tuesday, August 30, 2016 at 11:12 AM
> From: "Nuno Santos" >
> To: "Qt Project MailingList" >
> Subject: [Interest] Qt Android App and Notifications - Black screen after 
> tapping a notification with app open on background.
> Hi,
>  
> When my app has a notification I want to tap on the notification and open the 
> app. If the app is closed, it works correctly. When the app is open in the 
> background, it gets a black screen.
>  
> Has anyone had this problem in the past? Any suggestion?
>  
> Thanks,
>  
> Nuno
> ___ Interest mailing list 
> Interest@qt-project.org <> 
> http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] qt 5.7 broken on mac os x

[Nuno Santos]

What do you mean by underlines?

I’m using stock Qt 5.7 on Mac OSX without problems.

Nuno

> On 30 Aug 2016, at 22:12, Sylvain Pointeau  wrote:
> 
> Hello,
> 
> I just installed qt 5.7 on my mac os x and qt creator underlines all qml 
> libs...
> when is qt 5.7.1 planned?
> 
> best regards,
> Sylvain ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Starting remote process. Unable to start "com.acme.org"

[Nuno Santos]

Hi,

From one moment to another I simply cannot have the console output of a Qt 
Android application it says:

Starting remote process.  Unable to start “com.acme.org"

However the app is started…

I don’t know what to do. This has never happened before.

Does anyone has a clue?

Thanks,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Starting remote process. Unable to start "com.acme.org"

[Nuno Santos]

The device in which I’m having problems is running Android 7 (API 24)

When I use a older device running KitKat, it works. 

Any ideas what this could be?

Thx,

Nuno

> On 08 Sep 2016, at 16:53, Nuno Santos  wrote:
> 
> Hi,
> 
> From one moment to another I simply cannot have the console output of a Qt 
> Android application it says:
> 
> Starting remote process.  Unable to start “com.acme.org 
> <http://com.acme.org/>"
> 
> However the app is started…
> 
> I don’t know what to do. This has never happened before.
> 
> Does anyone has a clue?
> 
> Thanks,
> 
> Nuno
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Pixelated canvas on Qt 5.7 and iOS devices ... still?

[Nuno Santos]

Hi,

I was wondering if there is already a way of not having pixelated canvas drawn 
on iOS. I was hoping Qt 5.7 would fix that. Is there any special thing I need 
to do?

Regards,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt <http://www.imaginando.pt/>
+351 91 621 69 62___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] A question about QtQuick.Control 2.0 ComboBox customisation

[Nuno Santos]

Hi,

I’m customising a QtQuick.Control 2.0 ComboBox and I’m facing myself with the 
following problem:

I don’t know how to close the ComboBox when using a another element than 
ItemDelegate. The customisation page says the following:

http://doc.qt.io/qt-5/qtquickcontrols2-customize.html#customizing-combobox 
<http://doc.qt.io/qt-5/qtquickcontrols2-customize.html#customizing-combobox>

delegate: ItemDelegate {
width: control.width
text: modelData
font.weight: control.currentIndex === index ? Font.DemiBold : Font.Normal
highlighted: control.highlightedIndex == index
}

But I need to use a rectangle in order to have a different background color of 
the combobox drop down, so I’m doing the following:

delegate: Rectangle {
width: control.width
height: label.paintedHeight+10
color: controller.settings.baseColor

Text {
id: label
anchors.fill: parent
anchors.margins: 10
text: modelData
font.family: opensans.name
font.pixelSize: 14
verticalAlignment: Text.AlignVCenter
color: 
control.highlightedIndex==index?controller.settings.highlightColor:"white"
}

MouseArea {
anchors.fill: parent
onClicked: {
control.currentIndex=index
}
}
}

But now, how do I close the combo box? Any ideas?

Regards,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] A question about QtQuick.Control 2.0 ComboBox customisation

[Nuno Santos]

Thanks so much for this tip!! I would never get there. I couldn’t find 
documentation for popup. Where is it defined? 

Best regards,

Nuno

> On 27 Sep 2016, at 17:22, J-P Nurmi  wrote:
> 
>> On 27 Sep 2016, at 17:40, Nuno Santos > <mailto:nunosan...@imaginando.pt>> wrote:
>> 
>> Hi,
>> 
>> I’m customising a QtQuick.Control 2.0 ComboBox and I’m facing myself with 
>> the following problem:
>> 
>> I don’t know how to close the ComboBox when using a another element than 
>> ItemDelegate. The customisation page says the following:
>> 
>> http://doc.qt.io/qt-5/qtquickcontrols2-customize.html#customizing-combobox 
>> <http://doc.qt.io/qt-5/qtquickcontrols2-customize.html#customizing-combobox>
>> 
>> delegate: ItemDelegate {
>> width: control.width
>> text: modelData
>> font.weight: control.currentIndex === index ? Font.DemiBold : Font.Normal
>> highlighted: control.highlightedIndex == index
>> }
>> 
>> But I need to use a rectangle in order to have a different background color 
>> of the combobox drop down, so I’m doing the following:
>> 
>> delegate: Rectangle {
>> width: control.width
>> height: label.paintedHeight+10
>> color: controller.settings.baseColor
>> 
>> Text {
>> id: label
>> anchors.fill: parent
>> anchors.margins: 10
>> text: modelData
>> font.family: opensans.name
>> font.pixelSize: 14
>> verticalAlignment: Text.AlignVCenter
>> color: 
>> control.highlightedIndex==index?controller.settings.highlightColor:"white"
>> }
>> 
>> MouseArea {
>> anchors.fill: parent
>> onClicked: {
>> control.currentIndex=index
>> }
>> }
>> }
>> 
>> But now, how do I close the combo box? Any ideas?
> 
> 
> Hi,
> 
> The most straight-forward way is to add “control.popup.close()” in the 
> existing MouseArea onClicked handler. Alternatively, switch to AbstractButton 
> and kill the MouseArea altogether:
> 
> delegate: AbstractButton {
> width: control.width
> height: label.paintedHeight+10
> padding: 10
> background: Rectangle {
> color: controller.settings.baseColor
> }
> contentItem: Text {
> id: label
> // ...
> }
> }
> 
> --
> J-P Nurmi
> 
> ___
> Interest mailing list
> Interest@qt-project.org <mailto:Interest@qt-project.org>
> http://lists.qt-project.org/mailman/listinfo/interest 
> <http://lists.qt-project.org/mailman/listinfo/interest>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] QT Android: qApp->applicationName() returning lib name even after settings QCoreApplicaton::setApplication name

[Nuno Santos]

Hi,

I’m facing myself with a simple problem. 

I’m settings QCoreApplication::setApplication(NAME) but when I ask for 
qApp->applicationName, the result is a libTARGET.so

Isn’t it supposed to set the name to NAME?

Thanks,

Regards,

Nuno___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QT Android: qApp->applicationName() returning lib name even after settings QCoreApplicaton::setApplication name

[Nuno Santos]

Thiago,

Thanks for your reply.

Is there any specific place to call this? I’m calling at my main controller 
constructor

This is my main.cpp

int main(int argc, char **argv)
{
QGuiApplication app(argc, argv);

Controller controller(&app);

QQmlApplicationEngine engine;
engine.rootContext()->setContextProperty("controller", &controller);
engine.load(QUrl(QStringLiteral("qrc:/qml/main.qml")));

return app.exec();
}

This is controller constructor:

Controller::Controller(QObject *parent) :
QObject(parent)
{
QCoreApplication::setOrganizationName("Imaginando");
QCoreApplication::setApplicationName("TKFX");
}

Since my app is contracted with QGuiApplication, should I call 
QGuiApplication::setApplicationName instead? Might that be the problem?

Thanks,

Regards,

Nuno

> On 29 Sep 2016, at 19:48, Thiago Macieira  wrote:
> 
> On quinta-feira, 29 de setembro de 2016 18:57:01 PDT Nuno Santos wrote:
>> Hi,
>> 
>> I’m facing myself with a simple problem.
>> 
>> I’m settings QCoreApplication::setApplication(NAME) but when I ask for
>> qApp->applicationName, the result is a libTARGET.so
>> 
>> Isn’t it supposed to set the name to NAME?
> 
> It is and it does that. Your problem is elsewhere.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Qt & iPhone 6 Plus

[Nuno Santos]

Hi,

I have recently my apps on iPhone 6 Plus. I didn’t find the image sharp. Does 
anyone feels the same?

I’m wondering if there is something of operation I need to make my app support 
it. 

Is there any special procedure I’m not aware of?

Thanks,

Regards,

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt & iPhone 6 Plus

[Nuno Santos]

What about text, rectangles which are built type? Don’t you feel them a bit 
blurred? 

On Android everything looks really sharp.

> On 5 Oct 2016, at 17:46, maitai  wrote:
> 
> Hello,
> Here, for macos and iOS I have:
> 
> QCoreApplication::setAttribute(Qt::AA_UseHighDpiPixmaps, true);
> 
> Then all my images are defined 3 times (for example img1.png, i...@2x.png, 
> i...@3x.png at different sizes), plus if I generate an image I manage 
> devicePixelRatio() programmatically.
> 
> That way retina screens are taken in consideration.
> 
> Philippe
> 
> Le 05-10-2016 18:13, Nuno Santos a écrit :
>> Hi,
>> I have recently my apps on iPhone 6 Plus. I didn’t find the image
>> sharp. Does anyone feels the same?
>> I’m wondering if there is something of operation I need to make my app
>> support it.
>> Is there any special procedure I’m not aware of?
>> Thanks,
>> Regards,
>> Nuno
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] macdeploy and lib dependencies

[Nuno Santos]

Hi,

I’m linking my app with a lib that has other dependencies. While macdeployqt is 
able to copy and rename the main lib file, it isn’t able to do it for it’s 
dependencies. This is causing the bundle to have system dependencies. How can 
one trick macdeployqt to do the same for the lib dependencies? Renaming libs by 
hand is a tedious job and I always tend to avoid it. Any ideas?

Thanks!

Regards,

Nuno

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Is it possible to use clang toolchain to build Qt Android apps?

[Nuno Santos]

Hi,

I was wondering if clang toolchain is supported by Qt to build Android apps. 

The android SDK has the clang toolchain but one doesn’t seem to be able to set 
it under Qt Creator settings. 

Regards,

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest