Sherlock

Looks peculiar enough to say: I don't understand half of what is written there. Is the compiler not deterministic anymore?

No need to be sorry, we've all been there. Cheers

No screenshot in the docs, but no mention of the possibility (or need) to edit the path of an installed package either. So I guess you are just tired... grab a beer and get some shut eye.

I wonder where you might want those dots to show up? After a package is installed, editing its path seems rather pointless. And that dialog looks just the same on my system. So I thought maybe you have some strange dpi settings, that confuse the dialog. But there seems to be everything OK with it. I'm checking for the official docs to see if they have a screenshot.

Could you post a screenshot please? And what are your DPI settings?

There is a Wiki for DUnitX, which also explains installation: https://github.com/VSoftTechnologies/DUnitX/wiki/Wizard-Installation

Have you looked into iOSApi.CoreMotion? It does sound like a good place to start.

OT: BPL hell. I build monolithic applications. copy the exe anywhere and run it. Never even considered using dll or bpl "technology". All I ever see is drawbacks to this kind of software development.

True for more than one reason.

Oh! OK, sure, that'll work just fine. 👍 But the underlying point is if a manufacturer chooses to implement a feature, he should fix the bugs.

@Pat FoleySorry, I don't get it

While it is a nice thing to be able to use your own charset during development, it is something I would never encourage or do myself. You will never be able to have someone outside your language read and understand your code. That said, this is a bug and you should just report it in the Quality Portal: https://quality.embarcadero.com/secure/Dashboard.jspa

11.2 will now need a totally reworked Wuppdi Welcome page. Which is a good thing because "no more Internet Explorer"

Just call Invalidate for the entire form. Or (if you really have to) call InvalidateRect for the rectangle of your label. Note that InvalidateRect is still a method of your form, not of the label. But you will have to use some form of threading to get that application responsive anyway...

According to the installation notes Delphi 11.2 can only run on Windows 10....nicely done.

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.