Der schöne Günther

He told Windows not to tell RAD Studio anything about the "true" DPI. Windows should "lie", pass 96 DPI and then handle the scaling on the operating system level, instead of the application level. Windows did so when using DPI scaling with 125% or 150%, but not with a "custom" 115%.

I should have mentioned we are using the good old GnuGetText / dxGetText for localization. It seems to do some magic to swap out the method for resolving resource strings from System.pas with something else. I can only say that "It just works".

We are using this. Passing a pointer to a ResourceString instead of the (already translated) ResourceStrings allows us to show localized error messages to the user while using English messages when logging the exceptions to disk.

That sounds like your VM lacks proper drivers for hardware accleration.

Possibly related? http://blog.marcocantu.com/blog/2017-june-delphi-packages-creators-update.html

Then he probably has initialised the variable with nil or something else before entering the loop. Because otherwise, you get a compiler warning.

If you're actively exiting the loop, then everything is fine. You're probably talking about compiler warning W1037.

I can't say how you define severe. Of course there is overhead for the 2nd process, but your 1000s of entries should be well possible. I suppose this is also how professional logging solutions like Gurock SmartInspect (also available for Delphi) do this (Link)

So you need to Be able to cope with 1000s of entries per second Do not lose a single entry when the process crashes fatally Since you say it "Debug logging" and you don't need to survive a powerloss: Use a second process. This can casually flush the log entries to disk when a certain threshold is reached and has no problem with your main process crashing.

By itself, TB does not really have much to do with TA. It's just a type definition, it's full type name is TA.TB. Since it's just a type definition and no instance, you could have multiple instances of TB inside your TA instance. You can have TA.TB instances outside of a TA instance. You can have a TA instance with no TA.TB inside at all.

While I agree and also miss something like "zoom in/zoom out", you will have to propose this at https://quality.embarcadero.com/

"It renders crap" is not a very accurate description of the problem you're having. Care to upload a screenshot? And maybe your application manifest?

See also: https://www.xkcd.com/713/

I haven't done any benchmarks and don't know how much memory usage is a concern in your case- But I would assume that Creating a new list (you already know the capacity) Adding only the needed items Let your variable/field point to the new list could be a valid option.

Personally, I like to store those things in a local variable as it makes it easier to debug, but that's probably just personal taste.