Sherlock

@Ralf7 I am not sure how to reproduce it. I created a new VCL project in D12. Activated SKIA...and now what? OK, now that I understood what this was about. I deleted the unnecessary code.

I can see them now, brooding in their offices over a not so satisfactory IDE release, when suddenly one of them jumps up in excitement, shouting: "I got it!" Proceeding to invite everyone to a Teams meeting to spread the good news. When they all finally got together an extensive presentation with countless slides was skillfully delivered to the increasingly agitated peers culminating in roaring applause and a virtual high five by Mr. Popov himself, who had joined after hearing the good news. With his chest swollen with pride he then announced "So this is it then: Athens!"

Have you tried undoing the update via Powershell yet? Details here: https://support.atera.com/hc/en-us/articles/360020477680-Uninstall-Windows-10-Updates-#h_01F0WXRRDN6R5S7NSCTF9P8V41

I concur with @FPiette. Considering Windows 10 support and life will be over in two years, you would not want to upgrade then. Do it now, and be done with it. You just witnessed in the flesh what an "old" Windows can do...or rather what it can't. Just consider that a fair warning.

And equally a candidate for the Darwin Award...if there was a software category.

Just as a totally unqualified insertion: We are talking about the GOTO statement right? The one Dijkstra is rotating in his grave about? Ok, just checking. Carry on....

Could be that. I have no insight to the absolute inner workings of the forum software, but I have the impression the situation is sorted out anyhow. Or is there still some trouble @fastbike?

So that is a VCL application? Because enabling SKIA in an FMX application will cause all rendering to be done via SKIA, independent of the components. Another difference to remember.

More than ten years ago, right? Daily snapshots plus snapshots before an installation are the norm. And everyone who has ever whined about something broken in his "production environment" after installing this or that has gotten an earful about why they don't work on virtual machines. So one would think this particular issue should have become a no brainer...

Correct me if I'm wrong, but has this problem not happened before? Parnassus stuff not running with two different installed Delphi versions. At least for me it does not sound new.

Just to clarify: Have you not seen increases or other differences between Delphi 11.1 and 11.3? I mean, there was some work done there too. Why compare "some version along the way" to the newest, and not the last version before the new release?

That was always the trouble with that Parnassus stuff. BTW it is now Embarcadero stuff, and they should know better. -.-

You are absolutely right. Sorry about that.

Noice! And which breaking changes happened this time? Python is sweet when you need short scripts but a pain for large projects. I would like to see any one of our colleagues here with their million LOC projects using Python.

According to the feature matrix found in here https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Community_Edition, yes.

According to this https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Using_SQLite_with_FireDAC a download of SQLite DLLs is not necessary. You did provide a 64Bit DLL and your application failed. 32Bit without external DLL on the other hand ran smoothly. So....get rid of that new thing.

Please read my post carefully, I answered @JohnLM. Your frustration is valid. I have felt it more than once myself.

Now gee, what do you expect? How many of your clients demand to run your software on their outdated, unsupported and insecure operating systems (Windows 98 SE was sweet)? And what do you tell them? Even Microsoft has abandoned that product. Seriously, as long as you are using Windows 7 you will get nothing but sympathetic nods as every little issue could be blamed on the fact you are trying to run it on an OS that does not meet the requirements. Nevertheless 11.3 is the current version, so some of your issues may have gotten fixed.

Or if you use GExperts anyways, use the "Replace Components" expert.

I don't think signing is the issue. But consider the sometimes simple heuristics of a virus scanner: DLL = suspicious, file access = suspicious, compiled with Delphi = suspicious. That will generate a warning anywhere... not that its OK, but it is understandable.

Since FMX components have no hints altogether you'll need to program them on your own. Or look into our german site https://www.delphipraxis.net/169747-brennende-hinweise-fmx-hints-thintmanager-1-3-a.html. Alternatively you can go the way of the accepted answer from here: https://stackoverflow.com/questions/22417565/is-there-any-way-to-add-a-hint-or-tooltip-with-firemonkey Keep in mind however, that hints or tooltips are not something common on mobile devices!

It behaves strangely when resized: On a side note, the __Build_Project.cmd enters an infinite loop when run from a UNC-path like \\Mac\Home\Documents\Embarcadero\Studio\Projects.

Was it a problem with connectivity? We have a Mac Mini in our network, for signing the mobile apps. And we can use it to run the apps in the iOS simulator as well. Works pretty good. I have no Android experience on the other hand.

In that case I do hope you use that single out of the box method provided by Embarcadero to do that one line of calculating you need, otherwise someone might be inclined to call your solution a hack... just saying. The VCL framework like most other frameworks provide methods that should suffice for a very high number of use cases. But not all of them, this is to avoid feature creep, and other mishaps. Programming is not always straight forward. Sometimes you have to get creative. That is the reason I love it.

There is a "What's coming" webinar on November 9th so it is still roughly a month away.