Re: [Development] QThread usage/guidance

2012-10-10 Thread Tony Van Eerd
> -Original Message- > From: Giuseppe D'Angelo [mailto:dange...@gmail.com] > Sent: Wednesday, October 10, 2012 12:46 PM > To: Tony Van Eerd > Cc: Sze Howe Koh; development@qt-project.org > Subject: Re: [Development] QThread usage/guidance > > On 10 October 201

Re: [Development] QThread usage/guidance

2012-10-10 Thread Giuseppe D'Angelo
On 10 October 2012 18:20, Olivier Goffart wrote: > > If you connect to an object living in the finishing thread, it will be a > direct conection. And obviously instead of reading > connect(thread, SIGNAL(finished()), worker, SLOT(deleteLater())); I read > connect(thread, SIGNAL(finished()), th

Re: [Development] QThread usage/guidance

2012-10-10 Thread Olivier Goffart
On Wednesday 10 October 2012 17:45:51 Giuseppe D'Angelo wrote: > On 10 October 2012 16:00, Tony Van Eerd wrote: > > I don't have any use cases, but I can't imagine the example recommendation > > of > > > > connect(thread, SIGNAL(finished()), worker, SLOT(deleteLater())); > > > > working as expec

Re: [Development] QThread usage/guidance

2012-10-10 Thread Giuseppe D'Angelo
On 10 October 2012 16:00, Tony Van Eerd wrote: > I don't have any use cases, but I can't imagine the example recommendation > of > > connect(thread, SIGNAL(finished()), worker, SLOT(deleteLater())); > > working as expected unless deleteLater() happens on the same thread as > finished(), via a dire

Re: [Development] QThread usage/guidance

2012-10-10 Thread Tony Van Eerd
> -Original Message- > From: Olivier Goffart [mailto:oliv...@woboq.com] > > > So I'd like to understand how it works. Maybe that means looking > more at > > the code than the docs. But the code can change - the real > "contract" is > > in the docs. > > Depends of the point of view... To

Re: [Development] QThread usage/guidance

2012-10-10 Thread Olivier Goffart
On Wednesday 10 October 2012 15:00:15 Tony Van Eerd wrote: > I don't have any use cases, but I can't imagine the example recommendation > of > > connect(thread, SIGNAL(finished()), worker, SLOT(deleteLater())); > > working as expected unless deleteLater() happens on the same thread as > finished(

Re: [Development] QThread usage/guidance

2012-10-10 Thread Tony Van Eerd
agic that clarity. IMO. From: Sze Howe Koh [mailto:szehowe@gmail.com] Sent: Tuesday, October 09, 2012 11:12 PM To: Tony Van Eerd Cc: development@qt-project.org Subject: Re: [Development] QThread usage/guidance On Wed, Oct 10, 2012 at 1:20 AM, Tony Van Eerd mailto:tvane...@rim.com>> wr

Re: [Development] QThread usage/guidance

2012-10-09 Thread Sze Howe Koh
On Wed, Oct 10, 2012 at 1:20 AM, Tony Van Eerd wrote: > Speaking of docs, should the docs for the started() and finished() signals > note which thread these signals are sent from? ie finished(), even in > http://doc-snapshot.qt-project.org/5.0/qthread.html#finished and I think > in https://coder

Re: [Development] QThread usage/guidance

2012-10-09 Thread Sze Howe Koh
On Tue, Oct 9, 2012 at 4:49 PM, Giuseppe D'Angelo wrote: > On 9 October 2012 03:56, Sze Howe Koh wrote: > > That's a great idea! Is there a way to see a list of all doc notes > > available? > > Not yet , https://bugreports.qt-project.org/browse/QTWEBSITE-471 . > You could start by http://qt-proje

Re: [Development] QThread usage/guidance

2012-10-09 Thread Tony Van Eerd
> -Original Message- > From: development-bounces+tvaneerd=rim@qt-project.org > [mailto:development-bounces+tvaneerd=rim@qt-project.org] On Behalf > Of Kevin Krammer > > > > This mailing list is not really for question on how to use Qt. You > should > > use the interest mailing-list

Re: [Development] QThread usage/guidance

2012-10-09 Thread Giuseppe D'Angelo
On 9 October 2012 03:56, Sze Howe Koh wrote: > That's a great idea! Is there a way to see a list of all doc notes > available? Not yet , https://bugreports.qt-project.org/browse/QTWEBSITE-471 . You could start by http://qt-project.org/doc/all_notes_rss , then for each author pick the docnotes the

Re: [Development] QThread usage/guidance

2012-10-08 Thread Sze Howe Koh
On Sun, Oct 7, 2012 at 4:55 PM, André Somers wrote: > I think that there are probably a lot of useful bits and pieces that > really need to go into the main docs in the docnotes. Would it be a good > idea to go over them and see what gems are there? > > André > That's a great idea! Is there a wa

Re: [Development] QThread usage/guidance

2012-10-07 Thread André Somers
Op 7 okt. 2012 om 02:20 heeft Sze Howe Koh het volgende geschreven: > On Sun, Oct 7, 2012 at 4:13 AM, Giuseppe D'Angelo wrote: > On 6 October 2012 16:46, Kevin Krammer wrote: > > > > Because it clearly states that QTcpSocket instances returned by that method > > cannot be used from another t

Re: [Development] QThread usage/guidance

2012-10-06 Thread Sze Howe Koh
On Sun, Oct 7, 2012 at 4:13 AM, Giuseppe D'Angelo wrote: > On 6 October 2012 16:46, Kevin Krammer wrote: > > > > Because it clearly states that QTcpSocket instances returned by that > method > > cannot be used from another thread, making either that note very wrong or > > recommendation of moveTo

Re: [Development] QThread usage/guidance

2012-10-06 Thread Sze Howe Koh
On Sat, Oct 6, 2012 at 11:46 PM, Kevin Krammer wrote: > > This mailing list is not really for question on how to use Qt. You should > > use the interest mailing-list or the forums instead. > > In principle this is true. However, recurring questions regarding that > topic > indicate that the respec

Re: [Development] QThread usage/guidance

2012-10-06 Thread Giuseppe D'Angelo
On 6 October 2012 16:46, Kevin Krammer wrote: > > Because it clearly states that QTcpSocket instances returned by that method > cannot be used from another thread, making either that note very wrong or > recommendation of moveToThread() very dangerous. Last time I checked (4.7.something) that pie

Re: [Development] QThread usage/guidance

2012-10-06 Thread Kevin Krammer
On Friday, 2012-10-05, Olivier Goffart wrote: > On Friday 05 October 2012 15:24:40 Tony Van Eerd wrote: > > So that is the 'recommended' style then? > > Depends what you want to do. > If your task is CPU bounded, you can use QtConcurrent. > If you don't need to event loop, you can reimplement the

Re: [Development] QThread usage/guidance

2012-10-05 Thread Olivier Goffart
012 10:54 AM > > To: development@qt-project.org > > Cc: Tony Van Eerd > > Subject: Re: [Development] QThread usage/guidance > > > > On Friday 05 October 2012 14:31:51 Tony Van Eerd wrote: > > > > > What was the final resolution (if any) of the e

Re: [Development] QThread usage/guidance

2012-10-05 Thread Tony Van Eerd
So that is the 'recommended' style then? > -Original Message- > From: Olivier Goffart [mailto:oliv...@woboq.com] > Sent: Friday, October 05, 2012 10:54 AM > To: development@qt-project.org > Cc: Tony Van Eerd > Subject: Re: [Development] QThread usage/guidan

Re: [Development] QThread usage/guidance

2012-10-05 Thread Olivier Goffart
On Friday 05 October 2012 14:31:51 Tony Van Eerd wrote: > What was the final resolution (if any) of the email thread > "QThread::finished() race → fixing QThread" > http://lists.qt-project.org/pipermail/development/2011-November/000284.html > > > In particular as seen in > http://mayaposch.wordp

[Development] QThread usage/guidance

2012-10-05 Thread Tony Van Eerd
What was the final resolution (if any) of the email thread "QThread::finished() race → fixing QThread" http://lists.qt-project.org/pipermail/development/2011-November/000284.html In particular as seen in http://mayaposch.wordpress.com/2011/11/01/how-to-really-truly-use-qthreads-the-full-explan