I did some more research on this. Qt WebEngine in 5.4.2 is based on Chrome 37
(see
http://code.qt.io/cgit/qt/qtwebengine.git/tree/tools/scripts/version_resolver.py?h=5.4.2).
The Chrome bluetooth and bluetoothLowEnergy APIs were added in Chrome 37. So
theoretically this support may be in Qt 5.4.
And to avoid memory leak just give to the Widget the parent. And when
parent will die he will delete your Widget. It's just as example...
But to answer to your question more clearly we need to know some more
details. Such as what widget is doing, when he should die, and so on...
On 12.06.2015
In your case the 'temp' object will be deleted upon quitting function
foo(), so the signalTriggered() is never emitted. In previous version, it
would have been living longer because of memory leak you mentioned.
On Fri, Jun 12, 2015 at 4:52 PM, Berkay Elbir wrote:
>
> Hello all;
>
> We recently
Hello all;
We recently joined a new project, which is full with idiom like: ,
void foo(){
Widget* temp = new Widget;
connect(temp, &Widget::signalTriggerred,[this, temp ]()
{
do cool staff...
}}
As you can see no delete nothing, I am afraid even user class "Widget" is
in
Hi,
> Hi,
>
> I have finally managed to compile WinRT 32 with some quirks around the
> path. Trying to migrate one of my apps to WinRT resulted in some problems:
>
> 1 - It seems that ButtonStyle for QtQuickControls button is not available. Is
> this normal?
>qt.winrtrunner.app:
> file:///C:
