[Development] QThread usage/guidance
Tony Van Eerd
tvaneerd at rim.com
Tue Oct 9 19:20:59 CEST 2012
> -----Original Message-----
> From: development-bounces+tvaneerd=rim.com at qt-project.org
> [mailto:development-bounces+tvaneerd=rim.com at 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 or the forums instead.
>
> In principle this is true. However, recurring questions regarding that
> topic
> indicate that the respective documentation is either incomplete,
> misleading or
> wrong and documentation is part of the development effort.
>
Thanks. Between the doc issues and the previous discussion about 'bugs' in finish(), I thought this was the place to discuss it, but I'm new here, so I wasn't sure.
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://codereview.qt-project.org/#change,36301,patchset=3 and http://qt-project.org/forums/viewthread/20691/ , just says
"This signal is emitted when the thread has finished executing."
I know it only matters for DirectConnections, but it isn't clear whether the signals originate from the QThread's thread, or, uh, the QThread's thread. ie the QThread's affinity thread (which would be true, I suppose, for normal objects) or on the thread managed by the QThread.
And if I had other comments on the docs, where's the best place? Maybe the forum (http://qt-project.org/forums/viewthread/20691/)?
Tony
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
More information about the Development
mailing list