General guidelines to debugging a child process in the Delphi IDE.
Written for Dave Nottage and other forgetful people :-)
[10:50] Dave: ..and I want to debug the app that gets launched by the other one[10:50] Dave: both are Delphi 5 apps[10:50] Chee Wee: you have both the app's sources?[10:50] Dave: yes[10:51] Chee Wee: ok, so, what's the issue? you dunno the procedure how to do it?[10:51] Dave: yeah.. I thought I did.. but doesnt appear to be working[10:52] Dave: no blue dots, for one[10:53] Chee Wee: Load both apps in the Delphi 5 IDE.[10:53] Chee Wee: Activate the parent proj.[10:53] Chee Wee: In project options/settings, enable debug child process.[10:53] Chee Wee: place breakpoint in child project.[10:54] Chee Wee: ensure both projects are compiled with debug mode.[10:54] Chee Wee: start parent proj.[10:54] Dave: thanks :)[10:54] Chee Wee: that's the rough steps... you need to figure out the specific settings. I can't remember the exact names
In 2017, with the release of Delphi 10.2 Tokyo, Embarcadero introduced a specialized implementation of the Observer pattern into the System.Classes unit. While it has been in the wild for 9 years, it remains a "hidden" architecture for many, primarily because it serves as the invisible engine behind LiveBindings. Other than live bindings, you can also use the Observer pattern as a way to update component settings to the Windows registry, an .ini file, or persist it elsewhere.
System.Classes