Der schöne Günther

Use a profiler to find out what takes time and fix those parts 😎

It is what happens when the application that called ShellExecute did not provide a HWND of a foreground window. What is the value of your hndCaller ? Maybe you passed something like Application.Handle? Compare to GetForegroundWindow - Is your value the same?

About backporting: They did some of it around the time of XE8 / 10.0 Seattle, but not much after that, as far as I recall. https://community.embarcadero.com/article/technical-articles/16439-fall-2016-xe8-and-10-seattle-updates Here is an example of a pretty serious bug in System.Generics.Collections that never got backported. Thread includes comments from Marco Cantu why it didn't get backported. [RSP-13196] TQueue<TBytes> doesn't add elements - Embarcadero Technologies But I honestly cannot see anywhere that something like that was ever promised or sold. Of course it would be nice, but I can't really blame them, we also don't do backports in our software 😏

Is it just "your machine" or also others (virtual machines / Windows Sandbox)?

Be sure to supply your foreground window's handle to ShellExecuteEx. Source: Sertac Akyuz, StackOverflow.com

I'd have expected your method to return a Boolean for indication whether something has been found, and the out parameter can be used (your "IsValid"). An unsuccessful search isn't that out of the ordinary, so an exception is not appropriate. I also don't see that the first is an anti-pattern. Loop control with break and continue is perfectly fine. Did I miss something?

Evaluation versions do not come with source code, and the Community Edition with "limited" RTL source code (whatever that means). Your understanding of "borrowing" however even seems even weirder.

Fixed that for you

Different VMs 😎

All Windows 11 menus look like this. I have no idea what they were thinking.

Just a side note: For classic setups, I always untick "Start application" because those installers usually run with elevated permissions and will then also start the application elevated.

I don't have installers, but I think there's nothing wrong with that. It's not like you have to introduce your program, the user has already decided to install. The welcome page they use for their example makes no sense, because it provides absolutely no information. Same like "Setup has now finished" you sometimes see. By the way: Compare with this totally stripped down MSIX install experience on Windows:

Although the multi-platform approach never appealed to me, it still sounds terribly interesting. Do you have a reading recommendation (a presentation video is fine too) that explains their general approach?

I would absolutely agree unless @Mike Torrettinni also used a new feature as a motivation to drastically refactor parts that now needed bugfixing.

You can make a fancy looking TListView and fill it yourself.

Sure. You can also click it to quickly check out some other branch/tag. I haven't tried the VS Code integration in Delphi 11 yet, maybe that makes it even more appealing.

VS Code and two plug-ins (Git Graph & Gitlens) lead to a fantastic git experience, in my view. The branch name is always visible at the bottom

I never had the use case for the fixed version - Can you get it working in the VCL?

The way of deployment you have selected (local, non-updating files) is not the most common. I'd recommend to spend the five minutes to read about the different deployment options here: Distribute a WebView2 app and the WebView2 Runtime - Microsoft Edge Development | Microsoft Docs (Strongly recommended to read the full page) For setting the path you have placed the files in, you can use CreateCoreebView2EnvironmentWithOptions(..), but you may also use simple environment variables (see link). As as third way, there already appear to be handy wrappers like the one you have found, but unfortunately, they haven't even written documentation for the VCL version that already exists since 10.4 https://docwiki.embarcadero.com/Libraries/en/Vcl.Edge.TEdgeBrowserHelper.BrowserExecutableFolder

There's too many "should run" in there. Neither the IDE, nor the produced Win32 binaries are intended to be run on Windows XP, MS-DOS or Enigma. Is there a guarantee it will run on those platforms, just by not importing GetTickCount64? That just doesn't sound safe enough to promise my customers the same.

You're welcome.

Really looking forward to this one 😊 Not sure why they're so hyped about those TreeView checkboxes, I care much more for Remote Desktop improvements and High DPI 👍

Many thanks for your analysis. These extremely narrow highlights were often thought to be a bug, but Microsoft has confirmed it is intentional. Really puzzling decision to me.

How is your screen performing this? There are basically two options It's using "true" touch functionality, like on a regular Tablet (like Surface) It is emulating a regular mouse. Which means a mouse pointer will always be stuck on screen. Right-clicking is usually done by long-pressing It sounds like your screen is using option 2. If possible, see if it can be configured to use option one. If not, you have to have to disable the "long-press to right-click" functionality, if you don't need it. If that's not an option, it can be adjusted in the VCL itself, every TControl has a TabletOption where the long-press behaviour can be adjusted. That's how I remember it, I could be wrong.

Suggestion: Throw the ENoConstructException from System.SysUtils, not a regular Exception 😉