Make UI components that behave like you want them to with QML
summary
Describes three practical solutions to QML two‑way binding breakage when UI controls and C++ controllers race or the back end is slow or rejects changes: propose-value (component emits a proposed value, controller accepts and keeps the binding), unbreakable binding (component uses an internal boolean object so external bindings never break), and a C++ two-way-binding component that keeps properties in sync and can timeout/revert; shows which common hacks fail and which scale in large applications.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:28Problem with two-way binding
- 4:37Designing good API for components
- 8:38Non-working solutions
- 10:58Proposed value approach
- 15:22Unbreakable binding approach
- 20:35Explicit two-way binding
- 25:12Conclusion and Q&A
related talks
53mQt Quick Best Practices and Design Patterns
49mQt Quick Best Practices and Design Patterns
54mQML prototyping: Creating production ready and reusable code
01h 08mQt Quick Components: The Future of Qt Widgets
01h 22mArranging Items, QML Components and Debugging QML (part 4/4)
46mQt Quick Controls Re engineered
01h 21mQt Quick - User Interaction - User Input and States (part 2/4)
53mChoosing your UI weapon - C++ vs. QML vs. HTML5