Leaderboard

Done, thanks for the reminder.

As you likely noticed, Delphi 11 officially does not support Windows XP anymore. You can make your application compatible with XP again by simple set. In Project Options|Building|Delphi Compiler|Linking set "Set OS Version fields in PE Headers" and "Set SubSystem Version fields in PE Headers" to "5.1". Unless your application uses System.Threading.pas (TTask etc) you should run it under Windows XP with no problems. But if so, then you have to tweak this unit. Threading objects actually use in their internals new TThread.GetTickCount64 method, which is hardwired to Windows API GetTickCount64 which is not available in Windows XP API. Take this unit from "source\rtl\common" folder in Delphi 11 installation. Declare new local function in the beginning of implementation section of this unit like this: function _GetTickCount64: UInt64; begin if TOSVersion.Major<6 then Result := TThread.GetTickCount else Result := TThread.GetTickCount64; end; and replace all occurrences of TThread.GetTickCount64 calls with _GetTickCount64. For Win32 applications then copy this modified unit to \lib\win32\debug and \lib\win32\release folders in Delphi 11 installation and rename original System.Threading.dcu to e.g. _System.Threading.dcu. Then build your project which uses System.Threading with Debug and Release configuration. New System.Threading.dcu should be created in mentioned folders. After this you should remove modified System.Threading.pas from these folders to prevent its recurrent compilation. Now your Delphi 11 Win32 applications should run under Windows XP with no External Exception crash.

Resource Hacker A resource editor for 32bit and 64bit Windows applications. It's both a resource compiler and a decompiler - enabling viewing and editing of resources in executables (*.exe; *.dll; *.scr; etc) and compiled resource libraries (*.res, *.mui). Resource Hacker also provides many options for compiling and decompiling resources from the command-line. http://www.angusj.com/resourcehacker/ Download: http://www.angusj.com/resourcehacker/reshacker_setup.exe

ICS V8.67 has packages for Delphi and C++ 11.0, currently only available from SVN and the overnight zip, with a final release due next week. http://wiki.overbyte.eu/wiki/index.php/ICS_Download There was a major new OpenSSL 3.0 release this week, just finishing testing and integration with V8.67. Currently, many older ICS icons appeared incorrectly with a magenta background in Delphi 11.0 due to transparency being ignored, these will be fixed for the final release. Angus

Hi there, I want to wave goodbye to Delphi 10.4.2. This was for me one of the most stable versions in the past, maybe only XE8 was similar stable and less critical for me. Yes, it had its hickups here and there, but nothing too annoying at all. It accompanied me in the last 12 months as true friend, so I wish you luck in the afterlife. Looking forward to see Rx11 as stable as its older brother, and to give me another 12 months cycle of convenient Life. The start looks very promising, lets see ...

This issue has already been reported in QC: https://quality.embarcadero.com/browse/RSP-34850

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

Did you install EdgeView2 SDK from GetIt?

A change in TThread breaks Windows XP compatibility

@Daniel 11 Alexandria 😉 (versions before have names)

procedure UpdateTheme(Obj: TFrame); var objAsIThen : ITheme; begin If Supports(Obj, ITheme, objAsIThen) then objAsITheme.UpdateTheme; end;

Use Supports function var LTheme: ITheme; begin if Supports(Obj, ITheme, LTheme) then LTheme.UpdateTheme; end;

OK, it is not official, but I will share some internals here. You can change the titles of the Welcome Page items to clickable links with a secret registry setting: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Embarcadero\BDS\22.0\WelcomePage] "ActivateLinkOnTitle"=dword:00000001

True, but digging through the sub-properties to get what I want is so much more work than simply grabbing the value from the memory table to which it's attached. There might be times when this is necessary but I'd much rather use LiveBindings get the original value from the table. By the way, the working project is on GitHub under the name, AppPaths.

The Uses Clause Manager is now high DPI aware (more or less). I had to increase the width quite a lot to make this work 😞 I'll be on vacation for a few days. Not sure whether I'll get much done during that time. On one hand, work won't interfere. On the other hand, my wife might. 😉

Created PR https://github.com/ahausladen/DDevExtensions/pull/9

https://xkcd.com/979/

Support for older versions of Windows doesn't come for free. Official support means that they need to test against those versions and that they can't use the APIs of newer versions. Given the minimal market share of XP it hardly seems worth using resources to support it. If support for XP is required then use a version of Delphi that supports XP instead. I myself am on Windows 7 and if (when) that breaks Delphi then I will only blame myself.