Leaderboard

well ... I do not agree that this file is unsuitable. It actually works quite nice with any browser out there. We might find a smaller replacement, but a saving of a little less than 300 kbytes (the file is cached anyway) is actually not on top of my todo-list.

Another advantage of actions and action lists is that they can reside on a datamodule, which can be used in a VCL and a FMX application. Thus the same action logic can be used, which might have to be duplicated otherwise.

The value is that you have the images in a useful form, not trapped in some weirdo base16 dfm format. You have names for your images, and not just integer indices.

Is there a way to place the button above? I have to scroll down each time to make the button visible. Very annoying on a big screen.

Selective Debugging allows to select the debug DCUs on a per unit basis. This doesn't affect the content of the call stack. Honestly, I doubt that removing this information from the call stack is of any benefit at all. In fact it would camouflage the actual program flow rendering the call stack next to useless.

Please email Calvin Tang at Embarcadero. His email address is the usual pattern, i.e. firstname.lastname@embarcadero.com

Open the ico, remove all layers but 32x32, change the compression from bmp to png, save, done :) P.S. There you go favicon32.ico FWIW https://www.delphipraxis.net/favicon.ico has only 16x16

We don't use Delphi for other platforms.... but FPC... There is no plan yet, due to how incompatible cross-platform was in Delphi. And even with ARC disabled, I am not sure it would be worth it. There is a very small test framework in our Cross-Platform client units. See https://github.com/synopse/mORMot/blob/master/CrossPlatform/SynCrossPlatformTests.pas It is very lightweight, and should work on all platforms...

I think the question (and my answer) is specifically about what TForm.Action is for. Not what TControl.Action in general is for. The Action property is explicitly published by TForm so it's not by accident that it's visible in the property inspector.

http://docwiki.embarcadero.com/RADStudio/Rio/en/Creating_an_iOS_App Check "using custom fonts"

https://stackoverflow.com/a/9006662/587106 Nowadays I suggest using https://bitbucket.org/sglienke/spring4d/src/master/Tests/Source/Spring.Testing.pas which adds the functionality mentioned in the SO answer but better than at that time and implemented in DSharp back then. Two features that I personally never needed so far but that DUnitX can do which DUnit can't do out of the box are: standalone testcase classes (i.e. not inheriting from TTestCase) and per fixture setup - can also be plugged onto DUnit. There might be other subtle features of DUnitX that I am not aware of but I am very sure that they could be added to DUnit either by inheriting or by modifying TestFramework.pas (the latter was one of the reasons Vincent rather rolled his own iirc)

<humour ascerbic="true">This is due to the relationship between "theory" and "practice". In theory there's no difference between theory and practice. In practice, there is. </humour>

There are plenty of differences beyond basic code checks... File I/O, socket implementation, authentication, database drivers, etc. Also - many people test GUI interactions with DUnit which is VCL based. There needs to be a FMX based version. Then you have the whole interaction with running tests on a different system than what you are developing on and providing feedback to the developer. Then of course you'd want to run all the tests automatically with Jenkins or some other tooling so now the C/I system also needs to build/run/report/monitor tests on different platforms. You should also be running tests across different versions of each platform. I assumed that there was a solution for actual cross platform testing for Delphi. I did find this today: https://sourceforge.net/projects/dunitfmx/ Project description: "DUnit translation to FMX and Mac OS X" with an additional note: "When project finish, it shall work for run unit test in Windows and Mac OS X. And of course for Android and IOS too." But this repo hasn't been updated in 5 years. I started building my own custom tooling and the more I sketched it out, the bigger the project got so I thought I'd pause and post a simple question to see what sort of responses I'd get.

When my applications stop processing Windows messages it's always a very long processing in the VCL thread. Like reconnecting to a database, refreshing a huge dataset or I simply messed something up and my code got in an endless loop 🙂 This is when correct logging can save your life: I'm usually logging when an action starts and when it ends. When the application freezes just check which action started, which did not report back as finished.