Friday, July 30, 2021

Delphi: Inheriting Parent Properties

The ability to inherit Parent properties is very convenient. Let's say you have a form with several controls on that form. If you wanted to change the default font from "Tahoma" to "Segoe UI" wouldn't it be nice to only have to make that change in one spot and voila, the change happens everywhere?

Well that is what inheriting the Parent properties is all about.

Unfortunately, not all the Parent properties get inherited. The font color is one of those properties that gets inherited by some controls but not all controls. I created this short video to show what happens to some of the most used VCL controls when you change the forms Font Color and Font Family.

So, be careful and don't assume that one single change to the forms properties will get propagated throughout your entire application.

Semper Fi,
Gunny Mike

Saturday, July 17, 2021

CodeRage 3 Replays - Oldies but Goodies

This morning I was looking for a video on how to debug an application with the Delphi IDE. I came across a two-minute video on YouTube by Francois Gaillard. It was a teaser video intended to pique your interest for the segment he did at Code Rage 3. Unfortunately, there was not a link to the full blown presentation.

I found a link to the Code Rage 3 replays on the way back machine. You can find the original webpage using this link.

There are a lot of really interesting replays from Code Rage 3. Unfortunately, the recordings are done using Adobe Flash which has been discontinued. However all is not lost. You can download a stand-alone Flash Player from the Adobe website using this link

Delphi Debugging for Dummies by Francois Gaillard

After you download and unzip the replays you will see two ".swf" files. one called Session.swf and one called Session_controller.swf. Make sure to open the Session_controller.swf using the Flash Player program downloaded from the Adobe site. This will give you the the status bar with play and pause buttons along with the thumbtack progress bar.

Below is the list of Code Rage 3 presentation with download links.

Delphi / RAD Studio

C++ Builder

Delphi Prism


Delphi for PHP



Database Tools

General Topics

Sessions Presented in Spanish

Sessions Presented in Portuguese

Semper Fi
Gunny Mike

The link to the stand-alone Adobe Flash Player came from an article called "How to Play Adobe Flash SWF Files Outside Your Web Browser" on

Saturday, June 5, 2021

Mobile Storage Access (Note to Self)

 I am nowhere near creating apps for the mobile community. That doesn't mean I won't be in the future. So, I'm writing this as a "Note to Self" so when the time comes I'll have a nice handy reference.

If you are currently developing mobile apps you may find this discussion on Delphi-PRAXiS helpful and interesting.

How do users easily bring their desktop data to mobile devices?

You may also want to view the following YouTube video called Storage access with Android 11

Semper Fi
Gunny Mike

Sunday, April 25, 2021

Delphi Form/Code Separation (CodeRage 9 2014)

I just re-watched an excellent video by David Schwartz on form/code separation. Schwartz gave this presentation during a 2014 Code Rage 9 session. 

Schwartz says the majority of Delphi Form-to-Form code he has seen uses what he calls "Back-Door" injection. Where all the data movement to and from controls is handled at the form level. This is in contrast with the “normal” use of properties to enforce encapsulation in the movement of data into and out of objects. He discusses "Constructor" injection and "Property" injection pointing out the pros and cons of both. 

I'm one of these "back-door" injection coders. I've never used properties. I'm learning how to use them. Here are my main reasons for not using them in the past:

  • Short how-two Delphi videos... "You can do all of this with no code".
  • They seem overly complicated to type.
  • Ignorance on the benefits provided.
Perhaps the IDE's Code Completion ( Ctrl + Shift + C ) would make creating properties and all the getters and setters a lot easier. I'll look into this. 

Help Wanted: If you know of any tutorials or videos specifically aimed at creating and using Properties please add them in the comments. Thank you.

Demo Code: The link to the demo code at the end of this video is broken. I have a copy of the demo code, Schwartz emailed it to me. I'm waiting for his permission to make it available as a download on this post. It does require the Konopka Signature Controls (formerly Raize components). 

I found this very interesting.

Have You Embraced Your Inner Software Plumber Yet?
David Schwartz

Here are time jumps to specific sections:

00:41 Overview:
14:35 Summary

External References:

Saturday, April 24, 2021

Delphi Tip of the Day - Toggle Visibility On/Off

I'm porting over one of my Delphi 5 VCL, desktop applications to FMX. The target audience are Windows and macOS users. I'm not focused on mobile at this juncture. I'm spending quite a bit of time on the User Experience (UX). I guess you would call this approach "Desktop UX First".

I want to give the user the option of showing or hiding panels. I've decided to place this functionality in two places:

  1. On the main menu as an option.
  2. On the bottom tool bar as a button.
The first thing that came to mind was testing the "IsChecked" state of the main menu option. I slept on it and came back to the drawing board the next day. Instead of thinking about trapping clicks, I thought about what the intent of the click really was. And the answer is to show or hide the panel.

If the user clicks either the main menu option or the toolbar button I want the panel to show or hide. Both of these options need to work together behind the scenes. The intent of either click focuses on the "visibility" of the panel. And wouldn't you know, TPanel has a Visible property.

Visible is a boolean value, meaning it has only two states. True/False. And in Delphi there is a very cleaver way to toggle the state of a boolean value. This can be a little tricky to wrap your had around at first. However, once you understand it, you'll love it.

Boolean Value becomes not Boolean Value;
Boolean Value (True) becomes not Boolean Value (True);
Boolean Value (False) becomes not Boolean Value (False);
Boolean Value := not Boolean Value;

Panel.Visibile becomes not Panel.Visibile;
Panel.Visibile (True) becomes not Panel.Visibile (True);
Panel.Visibile (False) becomes not Panel.Visibile (False);
Panel.Visibile := not Panel.Visibile;

The statement Panel.Visibile := not Panel.Visibile; 
toggles the value, back and forth between True and False.

Let's see how to put this to use in the real world. In Delphi create a new FMX application. 
Click File > New > Multi-Device Application - Delphi and choose Blank Application.

Add the following components:
TPanel x2

Structure the components so they are parented like this:

Your form should look similar to this:

The goal is to toggle the Left Panel visibility. When you first run the application the form opens with the default settings. We want both the MenuItem (Show Left Panel) and the ToolBar Button to work together.

Hiding the Left Panel the form changes accordingly.

Regardless of which method was used to Show/Hide the left panel both items stay in synch by calling on procedure ToggleLeftPanelOnOff.

I'm testing the Sender to make sure it was invoked by either a TMenuItem or a TButton control before I toggle the panel visibility. Although it's not displayed here this allows for calling ToggleLeftPanelOnOff from inside the form's OnShow method in essence setting the correct values without toggling the panels visibility.

Here is the program code:

unit Unit1;


  System.SysUtils, System.Types, System.UITypes, System.Classes, System.Variants,
  FMX.Types, FMX.Controls, FMX.Forms, FMX.Graphics, FMX.Dialogs, FMX.StdCtrls,
  FMX.Controls.Presentation, FMX.Menus;

  TForm1 = class(TForm)
    MainMenu1: TMainMenu;
    StatusBar1: TStatusBar;
    pnlLeft: TPanel;
    pnlMain: TPanel;
    splLeft: TSplitter;
    tbarMain: TToolBar;
    btnTBarLeft: TButton;
    mnuFile: TMenuItem;
    menuOptions: TMenuItem;
    mnuShowLeftPanel: TMenuItem;
    mnuClose: TMenuItem;
    procedure mnuCloseClick(Sender: TObject);
    procedure mnuShowLeftPanelClick(Sender: TObject);
    procedure btnTBarLeftClick(Sender: TObject);
    { Private declarations }
    { Public declarations }
   procedure ToggleLeftPanelOnOff(Sender: TObject);

  Form1: TForm1;


{$R *.fmx}

procedure TForm1.btnTBarLeftClick(Sender: TObject);

procedure TForm1.mnuCloseClick(Sender: TObject);

procedure TForm1.mnuShowLeftPanelClick(Sender: TObject);

procedure TForm1.ToggleLeftPanelOnOff(Sender: TObject);
  // ==================================================================
  // Only toggle visibility if invoked by a menuitem or button click.
  // ==================================================================
  if (Sender is TMenuItem) or (Sender is TButton) then
    pnlLeft.Visible := not pnlLeft.visible;

  // ==================================================================
  // Set menuitem and button properties
  // ==================================================================
  if pnlLeft.Visible then
    mnuShowLeftPanel.IsChecked := True;
    btnTBarLeft.StyleLookup := 'arrowlefttoolbutton';
    mnuShowLeftPanel.IsChecked := False;
    btnTBarLeft.StyleLookup := 'arrowrighttoolbutton';



Here is the text version of the Form:

object Form1: TForm1
  Left = 0
  Top = 0
  Caption = 'Toggle Demo'
  ClientHeight = 480
  ClientWidth = 640
  FormFactor.Width = 320
  FormFactor.Height = 480
  FormFactor.Devices = [Desktop]
  DesignerMasterStyle = 0
  object StatusBar1: TStatusBar
    Position.Y = 458.000000000000000000
    ShowSizeGrip = True
    Size.Width = 640.000000000000000000
    Size.Height = 22.000000000000000000
    Size.PlatformDefault = False
    TabOrder = 1
  object pnlLeft: TPanel
    Align = Left
    Size.Width = 161.000000000000000000
    Size.Height = 458.000000000000000000
    Size.PlatformDefault = False
    TabOrder = 2
  object pnlMain: TPanel
    Align = Client
    Size.Width = 475.000000000000000000
    Size.Height = 458.000000000000000000
    Size.PlatformDefault = False
    TabOrder = 3
    object tbarMain: TToolBar
      Align = Bottom
      Position.Y = 418.000000000000000000
      Size.Width = 475.000000000000000000
      Size.Height = 40.000000000000000000
      Size.PlatformDefault = False
      TabOrder = 0
      object btnTBarLeft: TButton
        Align = Left
        Size.Width = 40.000000000000000000
        Size.Height = 40.000000000000000000
        Size.PlatformDefault = False
        StyleLookup = 'arrowlefttoolbutton'
        TabOrder = 0
        Text = 'btnTBarLeft'
        OnClick = btnTBarLeftClick
  object splLeft: TSplitter
    Align = Left
    Cursor = crHSplit
    MinSize = 20.000000000000000000
    Position.X = 161.000000000000000000
    Size.Width = 4.000000000000000000
    Size.Height = 458.000000000000000000
    Size.PlatformDefault = False
  object MainMenu1: TMainMenu
    Left = 304
    Top = 224
    object mnuFile: TMenuItem
      Text = 'File'
      object mnuClose: TMenuItem
        Locked = True
        Text = 'Close'
        OnClick = mnuCloseClick
    object menuOptions: TMenuItem
      Text = 'Options'
      object mnuShowLeftPanel: TMenuItem
        Locked = True
        IsChecked = True
        Text = 'Show Left Panel'
        OnClick = mnuShowLeftPanelClick

Gunny Mike

Thursday, April 8, 2021

Turbo Boost Your Delphi Knowledge - Become a Docwiki Ninja Warrior

I've made a commitment to learn FireMonkey. My flagship software product, Zilch Standard, turned 30 years old in 2021 and I still don't have a macOS version. I've got macOS consumers who buy my Windows® software and then email asking if there's a version that runs on their mac computer. This inevitably leads to me issuing a refund. So, I have a pretty strong incentive to learn FireMonkey.

"I feel like I'm sitting in the cockpit of an airplane."

I tried going down the FireMonkey learning path before but unfortunately I didn't get very far. Learning FireMonkey makes me feel like I'm sitting in the cockpit of an airplane. There's so many things that are unfamiliar. The scope of it all is overwhelming. There's so much to learn. I don't know where to look first. What about the help? It's just an [F1] key press away!

I don't know about you but I get frustrated at the built-in help that comes with Delphi? Does this sound familiar? You're frantically trying to figure something out... pressing [F1] all over the place, and hopelessly rummaging around through Delphi's built-in help. Sometimes it's great and gives you what you exactly what are looking for. Often times you are left feeling like you just read a bunch of cryptic tea leaves. 

Where do you turn at this point? The Facebook Delphi groups? Stackoverflow?  Your stash of Delphi books? Delphi's dockwiki?

In the past I've rarely thought to use Delphi's docwiki. In my mind I felt like it was the same rehashed [F1], cryptic leaves stuff. Well, that changed last night. 

It turns out, I wasn't using the dockwiki in a meaningful way. I figured out how to exploit the value of the docwiki. I'm going to show you how to become a docwiki ninja warrior.

"I'll show you how to become a Delphi Docwiki Ninja"

It all started last night when I wanted to learn more about FormFactor. I wrote a simple FMX application that displays the ClientHeight, ClientWidth, FormFactor.Width, and FormFactor.Height in the OnResize event handler. I was curious why the FormFactor values never changed as the form was resized, so I wanted to learn more. That's when I highlighted FormFactor in the Object Inspector and pushed [F1] .

This brought up the built-in help for FormFactor. This is one of those cryptic tea leaves help reference.

This wasn't very helpful. I may have done some googling to learn more but couldn't find anything that talked about FormFactor. What it is? How it's used? Why it's used? So I posted my question to StackOverflow

Someone commented and said "Please look at the documentation. It seems to concern iOS only, and changes according target device selection."

How did he find that docwiki page? That's not the docwiki page I found. In fact I couldn't find the dockwiki page referenced in StackOverflow comment. Turns out I didn't understand how to use the dockwiki. I was stuck in the API library and couldn't got out!

I was stuck in the API library and couldn't get out!

That's when I discovered how to become a Docwiki Ninja Warrior. This takes less than a minute to setup and I believe it will save you hours looking for information about Delphi that is relevant to what you are looking for. For illustrative purposes I'm sticking with my original pursuit of FormFactor.

Step 1: From inside the IDE click Help > RAD Studio Docwiki

Step 2: This opens the RAD Studio docwiki page in your default browser.
Step 3: Right-click on Library Reference > Open link in new tab 

Step 4: This opens the Library docwiki page in a new browser tab.
Step 5: Right-click on Code Example > Open link in a new tab.

At this point you should have three tabs in your browser each dedicated to separate docwiki sections. And now the fun begins.

Step 6: Enter FormFactor in the search box for tab 1 RAD Studio and press [Enter]. I'm horrible at spelling so I usually just copy and paste the value I need. I just highlighted FormFactor in the IDE code editor and pasted it in the search box. 

Step 7: Switch to tab 2 Library docwiki page and paste or enter FormFactor in the search box and press [Enter].

Step 8: Switch to tab 3 Code Examples docwiki and paste or enter FormFactor in the search box and press [Enter].

"So, what did I learn about FormFactor?"

FormFactor is only used used when you are creating an iOS application. This is awesome. I learned enough about FormFactor to satisfy my current need. Because I'm focused right now on learning how to use FireMonkey to create desktop applications for Windows and macOS, FormFactor is not relevant to my current situation. This lets me know I can skip a thorough investigation about FormFactor for the time being. It also lets me know that ignoring FormFactor at this time is okay since it does not apply to desktop applications for Windows or macOS. I don't need to be concearned about FOMO (fear of missing out).

However, if FormFactor was something I was interested in, the three different docwikis provide ample links to related, relevant, information in one convenient location. 

Oh yeah, make sure to play around with the "Advanced" link on the special search results pages.

There you have it. I am so glad I stumbled upon this. It will surely be very helpful in my quest to learn FireMonkey. 

Semper Fi,
Gunny Mike

Sunday, March 28, 2021

Video: What's New in 10.4.2 - With Timestamp Jumps

 I just watched the "What's New with 10.4.2" Embarcadero video. It sounds like there was a lot of quality code fixes put in place. One thing that surprised me is the ability to open the Form Designer and Code Editor in separate windows. Each fully functionable and editable.

The video is over 4 hours long. the first 43+ minutes are the new feature presentations. The remaining 3+ hours is a question and answer session. I have not listened to the Q&A. McKeeth did create a separate google docs of the Q&A.

Here are the topics with timestamp jumps.

Jim McKeeth

Overview of RAD Studio 10.4
Sarina DuPont

What's New  in 10.4.2
Sarina DuPont

Best-in-Class Windows Application Support
Marco Cantu

New TControlList VCL Component
Marco Cantu

New TNumberBox VCL Component
Marco Cantu

MSIX and Windows Store Support
Marco Cantu

More VCL Improvements
Upgraded Konopka Components (KSVC)
Enhanced TEdgeBrowser VCL Component
Marco Cantu

Demo TNumberBox
Jim McKeeth

Demo TControlList
Jim McKeeth

New Developer Productivity and UX Features
David Millington

Demo IDE & Code Insight (LSP)
David Millington

Form Designer & Code Editor in separate windows
David Millington

Expanded FireMonkey Platforms Support
Marco Cantu

New Delphi Compiler Enhancements
Marco Cantu

C++ Changes
David Millington

General Quality Enhancements
David Millington & Marco Cantu

RAD 10.4.2 SKUs
Marco Cantu

Gunny Mike
Semper Fi

Thursday, January 7, 2021

30 Year Old Delphi/Turbo Pascal App Still Relevant

Once upon a time there was an enthusiastic, ambitious, twenty-seven year old man who spent sixty dollars on a two-inch thick book with a funny looking floppy-disk measuring exactly five-and-a-quarter inches tucked in the back. To him, it was just another book he bought at the college book store. A book he needed as a requirement for a class on learning how to program a computer using a compiler. This was the next step. Beforehand, it was some introductory class on programing using BASIC. Yup 1986 was going to be a good year.

That young man was me. I was a Sergeant in the United States Marine Corps. I spent a year or so taking college classes at night working my way toward a degree. T'was was a pretty good deal. The Marine Corps was paying eighty percent of my tuition as long as I passed my classes. No problem.

Until, the admissions office said, "Mr. Riley, you have taken too many electives. You won't be able to enroll in any more classes until you complete English 101". No. Not  English 101. Not Again!

"Not English 101. Not Again"

I had taken the English Composition with Essay CLEP test six months ago and missed a passing grade by one point. One lousy, miserable, stinking point. It felt like Mr. Potter from It's a Wonderful Life had snatched my dream. It was at that moment my college career ended. Me and English 101, let's just say we don't get along.

I turned on my computer and said "let's see what this Turbo Pascal can do". I decided to create a flash card program for my young daughter. I didn't want her to read the screen, type an answer, and hit enter. Oh no, that would be too much work. I wanted her to use the arrow keys and move around and pick the right answer. No data entry for my little girl. 

With the help of two books by Ray Duncan I learned how to trap the keyboard using Interrupt 21 function calls. I also learned how to use Interrupt 10 to save and restore screen memory creating nice, fancy popup windows. Later I added true shadows to my popup windows by disabling the blinking bit which gave me a whopping 16 background colors. 

This was all fine and dandy. It kept me busy. Never really made a worthwhile "flash card" program. But I learned a lot. And it sure beat trying to master English 101.

Thus began my pursuit to create an exciting, functional working computer program. But where do I begin. I decided to modernize an old BASIC program I created back in 1986. After a year of nights and weekends that involved typing, cursing, compiling, retyping, more cursing, recompiling, printing, adjusting, readjusting, more typing and recompiling I had a program. I called it Zilch. The year was 1991. And there were two things I didn't know:

  1. Would anyone purchase this software?
  2. How long would it last?

Zilch v1.19 from 1995

Well it's been 30 years and tens of thousands of people have purchased this software. And it's still selling 30 years later.

Learn to tell a story

The past 30 years have been fraught with many hardships and many more wonderous moments. I would like to share a few insights I have gained over the years. Hopefully you'll find some of them useful.

  • Do not fall in love with your product. My software was "my baby". I spent a lot of time creating it  and I loved it. I nurtured it and most of all, told the world how lovely it was. When people tried to tell me what they thought about my software, I didn't listen. They would say "I'd buy your software if it did [ fill in the blank]".  I quickly jumped in, cut them off and said stuff like "No, you don't understand how my software works. It does this and you need to...". People were to kind to hang up mid sentence. They just didn't buy. 
  • 3,000 Views = 100 Downloads = 1 Sale. It's hard to get people to part with their money. Make sure you value every customer. 
  • Beware of copycats. From day one when you release your software competitors will find you. Better mousetraps are always being invented based off of similar designs. If you have a pioneering idea you will be copied. 
  •  Preserve screenshots and early drawings. At the start you never know how long your software will last or how many changes it will go through. Take pictures and preserve the memories from your early efforts. Someday you will want to look back at how it all started. Trust me.
  • Learn to tell a story. This is where I am at, right now after 30 years. It's taken me a long time. The story I have been telling for 30 years was a "transactional" story. It's been the story of what my software does, how it works, a litany of the features. Learn how to connect "emotionally" with your customers. People don't care about you or your software. They care about themselves, and how you can make their lives better.

I wish I played with my kids more

Do I have any regrets over the past 30 years. You betcha. Here's a few:
  • I wish I played with my kids more when they interrupted my keyboard time. Instead of saying "No, not now I'm busy". I should have spent 15-20 minutes playing catch or dolls. 
  • I failed to keep in touch with people who helped me along the way. I failed to keep in touch with Steve Payne from Craven Community College. He was my first in-person computer programming instructor. Hey Steve if you see this contact me..
  • Not listening to potential customers. (See Do not fall in love with product )
  • Having a Microsoft Windows only product.
Zilch v29.7 from 2020

Gunny Mike