Book Image

Delphi GUI Programming with FireMonkey

By : Andrea Magni
4 (1)
Book Image

Delphi GUI Programming with FireMonkey

4 (1)
By: Andrea Magni

Overview of this book

FireMonkey (FMX) is a cross-platform application framework that allows developers to create exciting user interfaces and deliver applications on multiple operating systems (OS). This book will help you learn visual programming with Delphi and FMX. Starting with an overview of the FMX framework, including a general discussion of the underlying philosophy and approach, you’ll then move on to the fundamentals and architectural details of FMX. You’ll also cover a significant comparison between Delphi and the Visual Component Library (VCL). Next, you’ll focus on the main FMX components, data access/data binding, and style concepts, in addition to understanding how to deliver visually responsive UIs. To address modern application development, the book takes you through topics such as animations and effects, and provides you with a general introduction to parallel programming, specifically targeting UI-related aspects, including application responsiveness. Later, you’ll explore the most important cross-platform services in the FMX framework, which are essential for delivering your application on multiple platforms while retaining the single codebase approach. Finally, you’ll learn about FMX’s built-in 3D functionalities. By the end of this book, you’ll be familiar with the FMX framework and be able to build effective cross-platform apps.
Table of Contents (18 chapters)
Section 1: Delphi GUI Programming Frameworks
Section 2: The FMX Framework in Depth
Section 3: Pushing to The Top: Advanced Topics

Learning about the Queue approach

The other option we have in order for a piece of code to be executed within the context of a specific thread (the main/UI thread specifically) is the Queue approach. Basically, it relies on the capability of the threads to maintain a queue of pieces of code to be executed.

This capability has some pitfalls; for example, event in the queue of a thread that gets destroyed, either because it has come to its end or has been terminated from outside, or maybe it has been disposed of and never been executed. But again, I am not going to discuss corner cases here. In most UI-related situations, you most likely want to queue code executions within the main/UI thread, which are extremely unlikely to be terminated before you need that code to be actually executed.

Look at the Queue part in Figure 11.1. From the diagram of code execution in the three situations (no sync, Sync, and Queue), you can notice how the gray code gets executed in the context of the UI thread...