On terça-feira, 5 de março de 2013 08.54.35, André Somers wrote:
> Op 5-3-2013 8:41, Thiago Macieira schreef:
> > On terça-feira, 5 de março de 2013 08.38.17, André Somers wrote:
> >> I'd appreciate a reply on the point that when using a QFutureWatcher,
> >> you don't know if the future is already
Op 5-3-2013 8:41, Thiago Macieira schreef:
> On terça-feira, 5 de março de 2013 08.38.17, André Somers wrote:
>> I'd appreciate a reply on the point that when using a QFutureWatcher,
>> you don't know if the future is already done or not at the moment you
>> connect.
> It's not done, by constructio
On Mar 5, 2013, at 8:38 AM, André Somers
wrote:
>
> I'd appreciate a reply on the point that when using a QFutureWatcher,
> you don't know if the future is already done or not at the moment you
> connect.
The intended usage of QFutureWatcher is that you set it up with connections
before st
On terça-feira, 5 de março de 2013 08.38.17, André Somers wrote:
> I'd appreciate a reply on the point that when using a QFutureWatcher,
> you don't know if the future is already done or not at the moment you
> connect.
It's not done, by construction.
--
Thiago Macieira - thiago.macieira (AT) inte
On Mar 4, 2013, at 11:56 PM, Thiago Macieira wrote:
>
> Oh, and if you want simple, one more thing occurred to me:
>
> runFunction([]() { main(); then(); });
>
> If you need the return value:
> runFunction([]() { then(main()); });
>
> I will not accept "C++11 isn't available for everyone" as
Op 4-3-2013 23:56, Thiago Macieira schreef:
> On segunda-feira, 4 de março de 2013 14.49.15, Thiago Macieira wrote:
>>> I think the proposed API addition is actually quite natural. It is not
>>> without precedent (QTimer::singleShot()), and would result in quite
>>> simple, readable code.
>> I disa
Hi,
On 03/05/2013 01:51 AM, Alan Alpert wrote:
> whoops, missed reply-all
>
> On Mon, Mar 4, 2013 at 4:51 PM, Alan Alpert <4163654...@gmail.com> wrote:
>> On Mon, Mar 4, 2013 at 1:36 AM, Dominik Holland
>> wrote:
>>> Hi all,
>>>
>>> i'm currently in a project where i try to access a lazy C++ mode
whoops, missed reply-all
On Mon, Mar 4, 2013 at 4:51 PM, Alan Alpert <4163654...@gmail.com> wrote:
> On Mon, Mar 4, 2013 at 1:36 AM, Dominik Holland
> wrote:
>> Hi all,
>>
>> i'm currently in a project where i try to access a lazy C++ model from
>> within QML.
>>
>> The basics are working well bu
On segunda-feira, 4 de março de 2013 14.49.15, Thiago Macieira wrote:
> > I think the proposed API addition is actually quite natural. It is not
> > without precedent (QTimer::singleShot()), and would result in quite
> > simple, readable code.
>
> I disagree on both accounts. It's not natural: ther
On segunda-feira, 4 de março de 2013 22.00.34, Andre Somers wrote:
> The point is to get notification when a job is done in the simples way
> possible. Nothing more, nothing less, without having to check the status
> of the future.
I understand what you want, but I don't want that. QFutureWatcher
> Yes, very much like that, but updated to also support the Qt5 like way
> of connecting.
>> Yes, that could work. To make it truly optional though, the main
>> parallel function would have to be pre-bound by the programmer (e.g.
>> using https://codereview.qt-project.org/#change,45294), since the
Op 4-3-2013 21:21, Thiago Macieira schreef:
> On segunda-feira, 4 de março de 2013 17.25.35, André Somers wrote:
>> QFuture runFunction(QFunction then, QFunction main);
>> QFuture runFunction(QFuntion then, QFuntion main);
>> QFuture runFunction(QFunction main);
> I think this is going too far. If
On segunda-feira, 4 de março de 2013 17.25.35, André Somers wrote:
> QFuture runFunction(QFunction then, QFunction main);
> QFuture runFunction(QFuntion then, QFuntion main);
> QFuture runFunction(QFunction main);
I think this is going too far. If you want to chain jobs, we need a more
complex job
Op 4-3-2013 16:17, Sze Howe Koh schreef:
> On 2 March 2013 18:17, Andre Somers wrote:
>> Actually, how do you feel about adding an optional _then_ argument to
>> the list of arguments of the functions in QtConcurrent and whatever is
>> decided to replace the QtConcurrent::run feature? Such a _then
On 2 March 2013 18:17, Andre Somers wrote:
> Actually, how do you feel about adding an optional _then_ argument to
> the list of arguments of the functions in QtConcurrent and whatever is
> decided to replace the QtConcurrent::run feature? Such a _then_ argument
> could be a slot signature, a func
On 3/4/13 13:16 , Samuel Rødal wrote:
> On 03/04/2013 01:08 PM, Sorvig Morten wrote:
>>
>> On Mar 4, 2013, at 8:13 AM, Samuel Rødal
>> wrote:
>>>
>>> What about things such as offscreen platform plugins used for
>>> testing? Or what about a theoretical platform plugin that would
>>> stream renderi
On Mon, Mar 4, 2013 at 11:11 AM, Konstantin Ritt wrote:
> ...and no one has answered to the original question of the topic ;)
>
Well, the original request for a playground module does not make any sense
to me because it is either QtCore or QtSystems material.
I guess Thiago and Lorn will figure
On Thursday 28 February 2013 18:35:23 Sze Howe Koh wrote:
> So, TBB is the shiniest at the moment, as it can replace all of
> QtConcurrent's functionality and more. I'm happy to set up the project
> to Qt-ify TBB, if people think it's a good idea and if we get a legal
> green light.
What exactly d
...and no one has answered to the original question of the topic ;)
Konstantin
2013/3/4 Knoll Lars :
> In general, I think we need to have another look at Qt SystemInfo for 5.2,
> and get this all sorted. The split between what's in Qt Core and what's in
> system info is a bit arbitrary, and it
On 03/04/2013 01:08 PM, Sorvig Morten wrote:
>
> On Mar 4, 2013, at 8:13 AM, Samuel Rødal wrote:
>>
>> What about things such as offscreen platform plugins used for testing?
>> Or what about a theoretical platform plugin that would stream rendering
>> commands to somewhere else? Imagine running wa
On 4 March 2013 18:49, Knoll Lars wrote:
> On 2/28/13 5:01 PM, "Thiago Macieira" wrote:
>>On quinta-feira, 28 de fevereiro de 2013 18.35.23, Sze Howe Koh wrote:
>>> On 23 February 2013 00:16, Thiago Macieira
>>wrote:
>>"Some legal team" does not help, of course. But I did a little more
>>digging
On Mar 4, 2013, at 8:13 AM, Samuel Rødal wrote:
>
> What about things such as offscreen platform plugins used for testing?
> Or what about a theoretical platform plugin that would stream rendering
> commands to somewhere else? Imagine running wayland clients on Mac or
> Windows for instance,
On 03/02/2013 01:06 PM, Olivier Goffart wrote:
> If i understand the test properly, it waits two seconds for a window to
> receive some events. But it may very well happen that the seconds are not
> enough, because the tests are run on some busy virtual machine or because the
> window manager i
Thanks Lars and all!
Indeed I can! Yohoo!
Andreas
2013/3/4 Knoll Lars
> Congratulations Andreas!
>
> I should have just fixed the permissions in Jira. Andreas, can you check
> that you can now edit bugs etc.?
>
> Thanks,
> Lars
>
> On 2/28/13 11:29 PM, "Laszlo Papp" wrote:
>
> >Yes. See these
In general, I think we need to have another look at Qt SystemInfo for 5.2,
and get this all sorted. The split between what's in Qt Core and what's in
system info is a bit arbitrary, and it would be good to get this sorted
and cleared.
Cheers,
Lars
On 3/1/13 11:28 PM, "Thiago Macieira" wrote:
>O
Congratulations Andreas!
I should have just fixed the permissions in Jira. Andreas, can you check
that you can now edit bugs etc.?
Thanks,
Lars
On 2/28/13 11:29 PM, "Laszlo Papp" wrote:
>Yes. See these for an examples:
>
>https://bugreports.qt-project.org/browse/QTJIRA-195
>https://bugreports.
Yes, congratulations. I've also made you the component lead for
declarative in Jira now :)
Cheers,
Lars
On 2/28/13 8:44 PM, "Alan Alpert" <4163654...@gmail.com> wrote:
>It's been 15 working days, so I think it passed. I'll go update the
>wiki, and triage some declarative bugs ;) .
>
>--
>Alan Al
On 2/28/13 5:01 PM, "Thiago Macieira" wrote:
>On quinta-feira, 28 de fevereiro de 2013 18.35.23, Sze Howe Koh wrote:
>> On 23 February 2013 00:16, Thiago Macieira
>wrote:
>> > On sexta-feira, 22 de fevereiro de 2013 19.26.06, Sze Howe Koh wrote:
>> >> Actually, I just realized that the open-so
Hi,
just thought I would post a quick update on where we stand with this set
of features:
On 18/12/2012 13:34, Sean Harmer wrote:
Hi,
I would like to start a discussion on the future level of support for OpenGL
enablers in Qt for those that are interested. So here goes...
I would like to ad
Hi all,
i'm currently in a project where i try to access a lazy C++ model from
within QML.
The basics are working well but when it comes to setting the
currentIndex it becomes a bit odd.
If i implemented everything well the lazy model always reports the
element count it currently has loaded b
30 matches
Mail list logo
