The 8 mistakes of QtQuick newcomers
summary
Eight concrete pitfalls and fixes for Qt Quick newcomers: bad JavaScript habits lead to untyped, blocking code so limit JavaScript to event handlers and favor declarative bindings; component.onCompleted order is undefined so centralize finalization; use Loader + Repeater for automatic instantiation and memory management instead of manual create/destroy; opacity 0 still costs rendering so set visible=false at animation end via ScriptAction; prefer framework animations over timers and use NumberAnimation/rotation instead of Timer-driven frame updates; keep business logic in C++ models and UI in QML, and move heavy drawing to QQuickItem/OpenGL when needed.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 4:20JavaScript is your friend
- 8:26Compromise on completed
- 10:22JavaScript fuzzyness
- 13:47Loader
- 21:17Visibility
- 25:16Dont over generalize
- 29:17Use animation not timers
- 31:50Scope mixing
- 39:30Visibility opacity binding
- 40:00Dont stand on switches
- 40:23Noise
- 42:50JavaScript
- 43:15Worker Script
- 44:00Performance
- 47:15Rectangle
- 48:15Gammaray
related talks
49mQt Quick Best Practices and Design Patterns
01h 22mQt Quick - Introduction to Qt Quick (part 1/4)
30mThe building blocks of QML, and how to use it with C++
53mQt Quick Best Practices and Design Patterns
01h 29mQt Quick - Animations and Visual Effects (part 3/4)
01h 00mHow to optimise Qt Quick 2 applications for maximum performance
01h 21mQt Quick - User Interaction - User Input and States (part 2/4)
24mThe Roadmap: Next Generation Qt (part 2/2)