Thanks, does that mean that the moc-generated signal member function is made fully thread safe?
2016-08-26 10:36 GMT+02:00 Igor Mironchik <igor.mironc...@gmail.com>: > Hi, > > On 26.08.2016 11:33, Etienne Sandré-Chardonnal wrote: > > Hi, > > I have an object which subclasses QThread for performing an asynchronous > operation. Before any objection rises about that, I know that for most uses > QThread subclassing is not the way to go, and creating an object which is > pushed to a regular QThread is better, and I'm doing it 99% of the time, > but here it was more straightforward to simply subclass QThread and > overload run(), and no event loop is needed. This works fine. > > Now I would like the run() function to make the QThread subclass emit > signals. If I just do "emit mySignal()" inside run(), my guess is this will > not work unless there is a special mechanism handling this. > > > You can do it. > > > Can I do this, or do I need a full event loop, an object living inside the > QThread, and a queued connection between signals? (ie the regular QThread > use) > > Thanks! > > > _______________________________________________ > Interest mailing > listInterest@qt-project.orghttp://lists.qt-project.org/mailman/listinfo/interest > > > -- > Best Regards, > Igor Mironchik. > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
