The following code generates warning about memcpy on object type:
QList images;
QList future = QtConcurrent::blockingMapped(images, scaled);
The warning:
In file included from /Qt/5.0/qtbase/include/QtCore/qvector.h:1:
/Qt/5.0/qtbase/include/QtCore/../../src/corelib/tools/qvector.h:459
On Sun, Sep 30, 2012 at 2:24 AM, Chris Meyer wrote:
> On Sat, Sep 29, 2012 at 11:04 AM, João Abecasis
> wrote:
> > João Abecasis wrote:
> >> Chris Meyer wrote:
> >>> The documentation promotes the idea of using 'moveToThread' as a
> >>> preferred threading mechanism. However, we've found that mov
Hi,
I have read recently that qt5 will be available thru angle/Directx and
there is work in progress about a wmf backend dxva. when will it be
available in git ?
Will it be possible to have a public access to directx surface to
reimplement some custom video decoding with dxva ?
___
On Sat, Sep 29, 2012 at 11:04 AM, João Abecasis wrote:
> João Abecasis wrote:
>> Chris Meyer wrote:
>>> The documentation promotes the idea of using 'moveToThread' as a
>>> preferred threading mechanism. However, we've found that moveToThread
>>> is full of pitfalls.
>>>
>>> Particularly, an objec
I am having problem using lambda in QtConcurrent::map() function. The
following code:
#include
int foo(int i) { return i+1; }
void moo(QList list)
{
QtConcurrent::mapped(list, [](int i){ return foo(i); });
}
produces errors below with Clang 3.1. Is lambda supported in map()? Or
do I ne
João Abecasis wrote:
> Chris Meyer wrote:
>> The documentation promotes the idea of using 'moveToThread' as a
>> preferred threading mechanism. However, we've found that moveToThread
>> is full of pitfalls.
>>
>> Particularly, an object must be deleted on the thread on which it
>> resides. This mak
Chris Meyer wrote:
> The documentation promotes the idea of using 'moveToThread' as a
> preferred threading mechanism. However, we've found that moveToThread
> is full of pitfalls.
>
> Particularly, an object must be deleted on the thread on which it
> resides. This makes it difficult to manage the
On Sat, Sep 29, 2012 at 12:59 AM, Sze Howe Koh wrote:
> Hi all,
>
> As part of the effort to polishing the documentation for Qt 5
> (http://community.kde.org/Qt5/Documentation), I'm taking on the
> QThread-related docs, which have been outdated since Qt 4.4, causing much
> confusion across the int
Great suggestion, thanks. I've incorporated that into the draft.
Sze-Howe
On Sat, Sep 29, 2012 at 7:22 PM, wrote:
> On Sat, 29 Sep 2012 15:59:29 +0800, Sze Howe Koh
> wrote:
>
> >If you could spare a few
> >minutes to read it and provide comments, either on the forum of this
> >mailing list,
On Sat, 29 Sep 2012 15:59:29 +0800, Sze Howe Koh
wrote:
>If you could spare a few
>minutes to read it and provide comments, either on the forum of this
>mailing list, I would be very grateful.
Since it is QT5 docs, you might want to encourage using the new QT5
syntax for connecting objects, whi
Hi all,
As part of the effort to polishing the documentation for Qt 5 (
http://community.kde.org/Qt5/Documentation), I'm taking on the
QThread-related docs, which have been outdated since Qt 4.4, causing much
confusion across the internet.
Before submitting it to Gerrit, I'd like to ask for help
Hi,
providing a code coverage analysis of Qt is a living project and so we would be
happy of any feedback of the Qt developers.
Issues and suggestions can be addressed to the Squish Coco forum:
http://www.froglogic.com/forum/viewforum.php?f=10
We found that it is better to not put issues on metr
12 matches
Mail list logo
