Qt-contributors-summit-2013-Adaptable-UI-2-: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Categorize) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
[[Category:QtCS2013]] | |||
==Additions to previous sessions:== | |||
Android assets:/// behaves a little differently. Will still overload assets:/// despite this. May wish to suggest qrc: to more people, as that is the most cross-platform. | |||
<span class="caps">DPI</span> should still be that the logical <span class="caps">DPI</span> is exposed, but for text size the platform Label should use platform hints where available to give a good default size for text | |||
==Topics we ran out of time for:== | |||
* platform vars like longPressDelay | |||
* Flickable with a pluggable backend | |||
* MultiScreen and MultiWindow <span class="caps">API</span>s | |||
Latest revision as of 17:16, 6 January 2017
| 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. |
Additions to previous sessions:
Android assets:/// behaves a little differently. Will still overload assets:/// despite this. May wish to suggest qrc: to more people, as that is the most cross-platform.
DPI should still be that the logical DPI is exposed, but for text size the platform Label should use platform hints where available to give a good default size for text
Topics we ran out of time for:
- platform vars like longPressDelay
- Flickable with a pluggable backend
- MultiScreen and MultiWindow APIs