Qt-contributors-summit-2013-QObject: Difference between revisions
Jump to navigation
Jump to search
AutoSpider (talk | contribs) (Add "cleanup" tag) |
AutoSpider (talk | contribs) (Decode HTML entity names) |
||
| Line 3: | Line 3: | ||
- 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 | ||
- We want to add the overload<br /> connect(ob1, & | - We want to add the overload<br /> connect(ob1, &ddd::fff, receiver, []{}, Qt::QueuedConnection); | ||
- For function such as QTimer::singleShot, we can add the<br /> two template overload and some helper code in (private?) <span class="caps">API</span><br /> to share the complicated template code. Or just use QSlot | - For function such as QTimer::singleShot, we can add the<br /> two template overload and some helper code in (private?) <span class="caps">API</span><br /> to share the complicated template code. Or just use QSlot<…><br /> QTimer::singleShot(int, QSlot<void()>) | ||
- implement<br /> template | - implement<br /> template<typename …Args><br /> QMetaObject::queuedInvoke(QObject, Ret(T::*)(Args…), Args…)<br /> template<typename …Args><br /> 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 | 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 | ||
Revision as of 17:40, 12 March 2015
| This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
- 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