Difference between revisions of "Qt-contributors-summit-2013-QObject"
From Qt Wiki
AutoSpider (talk | contribs) (Decode HTML entity names) |
m (Categorize) |
||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | {{Cleanup | reason=Auto-imported from ExpressionEngine.}} | ||
| − | + | [[Category:QtCS2013]] | |
- We agree that we focus on C++11 and new<br /> features requires it | - We agree that we focus on C++11 and new<br /> features requires it | ||
Latest revision as of 17:24, 6 January 2017
- We agree that we focus on C++11 and new
features requires it - We want to add the overload
connect(ob1, &ddd::fff, receiver, []{}, Qt::QueuedConnection); - For function such as QTimer::singleShot, we can add the
two template overload and some helper code in (private?) API
to share the complicated template code. Or just use QSlot<…>
QTimer::singleShot(int, QSlot<void()>) - implement
template<typename …Args>
QMetaObject::queuedInvoke(QObject, Ret(T::*)(Args…), Args…)
template<typename …Args>
QMetaObject::blockingQueuedInvoke(QObject, Ret(T::*)(Args…), Args…) -> Ret Templateed QObject: – investigate what are the use case to see what kind of features we want to support or not. (Not to open too many cans of worms
features requires it - We want to add the overload
connect(ob1, &ddd::fff, receiver, []{}, Qt::QueuedConnection); - For function such as QTimer::singleShot, we can add the
two template overload and some helper code in (private?) API
to share the complicated template code. Or just use QSlot<…>
QTimer::singleShot(int, QSlot<void()>) - implement
template<typename …Args>
QMetaObject::queuedInvoke(QObject, Ret(T::*)(Args…), Args…)
template<typename …Args>
QMetaObject::blockingQueuedInvoke(QObject, Ret(T::*)(Args…), Args…) -> Ret Templateed QObject: – investigate what are the use case to see what kind of features we want to support or not. (Not to open too many cans of worms
