Sherlock

Out of curiosity: How would binaries created with this fare on a Ryzen processor? Are Intel and AMD still 100% compatible? AFAIK Ryzen had problems on Win11 well into this summer, but that was because of TPM.

No, not at all. There are plenty of FMX Android Apps. Keep in mind however, you will need to update your Delphi as soon as a new version is released to keep up with requirements from new Android versions.

Firstly, that information is roughly four years old (which is ancient history in our line of work) and secondly no Delphi developer would have an Android App, which seems not to be the case. Sherlock

Sorry, but @Lainkes clearly stated, the data is not entered by the user. So no focus on fixing user errors needed here. Remains the unanswered question, about the origin of the date. How did this possibly erroneous value get into the Edit in the first place? Is it from a database? Or maybe some text file? Retrieved from a web site? All of which have appropriate methods to ensure correct data types and values. Fixing the issue on the GUI is way to late.

I wonder why you think you can't use a TDateTimePicker? Have you tried? Whence is the date if not from the user? Because anything else should already be under your total control.

Just so it wont be forgotten, OLEDs may suffer from the same issue. But modern TVs and maybe displays as well have nifty workarounds installed (spoiler alert: they do what Ian plans to implement themselves). Read here for more infos: https://www.displayninja.com/oled-screen-burn-in/

Have you tried TFormatSettings.LongDateformat?

It is back online...FYI

For the complete device or only for your application?

@Uwe Raabe Thanks! Sounds like a tough task then. But if an API existed, would it make this task easier? I'm still trying to figure out, where one could benefit from the LSP other than finally getting correctly marked errors in the source.

So, from your description I gather you are not using the LSP? Is something missing from it to make it unsuitable for this task, or is it not accessible altogether for plugins other than Embarcaderos own? Or am I misunderstanding the purpose of the LSP completely...never actively used it.

@Uwe Raabe You are right, and that is why I sort of constrained my claim to "most of the time". It is very important, that users not have a hard time recognizing their security relevant and time sensitive application. Not many applications however are just that, security relevant or time sensitive. They are simple boring data entry UIs and it is understandable, that a developer is tempted to "pep things up" but that has to be done very carefully and I doubt Themes are the way to go. At least last time I looked at them (three years ago) they where inconsistent and hard to edit/adapt to own wishes. But I believe this is leaving the path the OP had in mind.

Any style that differs from the current OSes UI style and style guide, will cause an application to look and feel strangely out of place. You might want or like that, but most of the time users will feel uneasy about it as soon as the initial "wow how pretty" effect has faded to "why is the quit button green?". So in essence styles to me are just another toy where Embarcadero has wasted precious time and money, both of which are direly needed in other areas of the product.

Perhaps GExperts can do that trick... I'm not sure though.

Strange. What happens when you press F12 (standard key to switch between form and unit)?

I'm guessing you write about structural highlighting. The link to the manual should clarify. On second thought, you might have 3rd party tools like CnPack installed. That has such an option as well.

The really fine manual states this behavior as being as expected.

Check what is entered in the field labeled "né". This can not be converted to a date. I'm guessing that is a TMaskEdit. You should only try to convert its contents, when it is filled with data. By the way, this applies to all other date fields...and perhaps even more.

OK you'll need: uses FMX.Types, FMX.BehaviourManager, FMX.Platform; And even if you only develop for yourself, you should consider different DPI and scaling in your application because you might treat yourself to a monitor with higher resolution at some point.

Have you tried your code on Windows set to 150% or any other scale? You need to find out, what the DisplayMetrics are and react accordingly. I use something like this if TBehaviorServices.Current.SupportsBehaviorService(IDeviceBehavior, DeviceBehavior, Context) then begin DisplayMetrics := DeviceBehavior.GetDisplayMetrics(Context); Scale := DisplayMetrics.ScreenScale; ppi := DisplayMetrics.PixelsPerInch; end else ShowMessage('Help?!');

I'm afraid that is a waste of time. It's not just the SDK that is needed here. Code signing by a specific XCode release is checked by Apple as well.

If you only need the mac sporadically or for barely more than XCode code signing consider a service like macincloud.com

Strange. You probably should contact Apple about that.

Microsoft used to offer outdated OSes such as XP in virtual machines to test websites on different IE versions. Seems these VMs are gone though...you could try archive.org however.

So, to wrap it up: Be a genius and have your decades old application rely on an object being available at all times. Or just double check to make sure. The penalty for that is being frowned upon by the real geniuses...or not.