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