tl;dr: we should stop teaching QObject::moveToThread as the recommended qt threading method reason: you can't safely use the same object in same-thread use and multi-thread use. it requires a special thread-aware object or glue code
the [non auto-generated] QThread::run method also sucks because the _user_ will end up making a ton of useless QThread subclasses i propose more hackery. a moc hack, to be specific (because a preprocessor macro can't have Q_OBJECT in it) what is a PORTABLE way to save arguments (as auto-generated/invisible-to-user QThread subclass *constructor* argument(s)) to be passed in during the "object" instantiation/construction args from inside QThread::run? My concerns: 1) implitly shared reference count being 3 instead of 2 2) pointers becoming null before QThread::run is active 3) tons of other scenarios i am probably missing Is Q_ARG/QGenericArgument what I want? Or should I steal the code from however signals/slots does it? d3fault
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
