Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Delphi GUI Programming with FireMonkey

You're reading from   Delphi GUI Programming with FireMonkey Unleash the full potential of the FMX framework to build exciting cross-platform apps with Embarcadero Delphi

Arrow left icon
Product type Paperback
Published in Oct 2020
Publisher Packt
ISBN-13 9781788624176
Length 546 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Andrea Magni Andrea Magni
Author Profile Icon Andrea Magni
Andrea Magni
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Section 1: Delphi GUI Programming Frameworks
2. Introducing the FireMonkey Framework FREE CHAPTER 3. Exploring Similarities and Differences with VCL 4. Section 2: The FMX Framework in Depth
5. Mastering Basic Components 6. Discovering Lists and Advanced Components 7. Using FireDAC in FMX Applications 8. Implementing Data Binding 9. Understanding FMX Style Concept 10. Divide and Conquer with TFrameStand 11. Building Responsive UIs 12. Orchestrating Transitions and Animations 13. Section 3: Pushing to The Top: Advanced Topics
14. Building Responsive Applications 15. Exploring Cross-Platform Services 16. Learning about FMX 3D Capabilities 17. Other Books You May Enjoy

Understanding the thread safety of UI frameworks

The most popular UI frameworks out there (including VCL and FMX) are not thread-safe.

Thread safety is the ability something (like a piece of code, a library, a framework, or something else) has to properly work in a context where multiple concurrent threads are involved. Properly work here means having no runtime errors, memory leaks, memory overwriting, and so on. It does not mean it is the most efficient way to accomplish the task.

Everything is run in a single thread that will be the owner of all UI objects and the executor of all UI-related tasks. The reason is that a thread-safe UI environment would likely require a lot of synchronization. Synchronization is what is needed to avoid collisions while dealing with the same object and multiple threads. There are a number of techniques related to synchronization but, to get the concept, we can consider one of the simplest forms of synchronization.

When a resource is (or has to be) shared...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image