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

Understanding a thread's lifespan

Each thread instance has a Boolean field, namely Terminated, that can be set through a call of the public Terminate method. You may think to call Terminate, which will have some immediate effect, like stopping the thread or brutally killing it, but this is not the case. Calling Terminate will simply set the Terminated field to True and call the TerminatedSet protected procedure as a consequence.

Beware, the Terminate method will execute in the context of the caller thread (that is, the main/UI thread) and so will happen for the consequent TThread.TerminatedSet method execution.

It is the thread code's responsibility to periodically check whether somebody (from outside) asked for premature termination of the thread. This might be done between steps of a multi-step operation, for example, or if the thread has a control loop, at the end of each iteration of the loop. A simple way...