Uwe Raabe

Most likely, yes, but there are several beta testers having a mixed version setup or even using their productive environment. As @Angus Robertson mentioned, there are other factors involved here that made this slip through.

Embarcadero knows about it and is working on an official solution. And before someone claims that could have been found during the beta: Most of the GetIt stuff is not available during beta until almost the last day and the majority of beta testers install in a dedicated environment without any prior Delphi version present. Also, not everyone makes use of all what is available in GetIt.

To have the Parnassus plugins work in Delphi 12 as well as Delphi 11.3 on the same machine you need to do either of this depending on your situation: Before installing the Delphi 12 plugin: In folder c:\Program Files (x86)\Common Files\ParnassusShared rename ParnassusCoreEditor.dll into ParnassusCoreEditor_XAlexandria.dll After installing the Delphi 12 plugin: Copy the 11 version of ParnassusCoreEditor.dll from the appropriate CatalogRepository folder as ParnassusCoreEditor_XAlexandria.dll into the mentioned folder

I don't know, but I know that GoToWebinar sessions have a limit for the number of participants.

Actually it is running in the moment, but the available seats are all occupied.

The reason for these "Whole Word" problems was that there was only one setting in the registry for Search (Ctrl-F) and Search in Files (Ctrl-Shift-F). In D12 these are separate settings. So, if there are still problems they have another cause and steps to reproduce are mandatory to get this fixed.

A quick check doesn't show this here. Do you have detailed steps to reproduce?

As I cannot check with QP in the moment, can you please describe the bug you are referring to?

I'm afraid the user manual doesn't cover this feature.

The lack of implementing that feature request was the driving force behind writing that article. As long as everybody steps away from designing in High DPI the collected bug reports will only cover the obvious cases but miss the deeper ones. Thus I decided to use the form designer in High DPI for at least one of my projects and see how it goes. Obviously I had to develop a strategy and some workarounds to make it usable in the first place. Publishing it is based on the hope that others also step on that ship and share their findings, too.

You can have this for free: Open MMX properties and navigate to Pascal - Sorting Under Format unit uses clauses check Group and sort uses Now when you format the uses clause (with Ctrl-Alt-U while the cursor is inside a uses clause) MMX does the following: Resolve any unit aliases Resolve all unit scope names Group the units as configured (see below) Compress and wrap each group according to the settings The groups are configured per project in the MMX Project options setting. If the entry for Groups is cleared neither grouping nor sorting is done. Also these Project options have an Auto Format checkbox, which when checked forces the uses clause formatting whenever MMX manipulates a uses clause. My personal preference would be to format the uses clauses without any other changes done to keep version control happy. This can be achieved by a command line tool available on GitHub: UsesCleaner It provides almost the same functionality as MMX, but targets complete projects instead of single units.

Indeed, for me the biggest enhancement is the handling of font sizes regarding dpi changes. This eliminates a plethora of workarounds where fonts are adjusted in height, color or style and thus cannot rely on the ParentFont mechanism. Besides that, there are currently 15 issues I reported in Quality Portal marked fixed in this release. Not that bad.

Copy the ParnassusCoreEditor.dll from the 22-CatalogRepository as ParnassusCoreEditor_XAlexandria.dll into the c:\Program Files (x86)\Common Files\ParnassusShared\ folder.

I guess the problem that these parameters are in the URL query.

AFAIK it matches the commit from September, 11th 2023 (65ae6909208257e51450be7ec724fd54aedfeba4)

The Delphi 12 release falls in your subscription, thus you are entitled to download, install and use it without any time limit. Nevertheless I recommend to renew your subscription to stay eligible for further updates.

Delphi 12 already has a separate menu item for this unter Tools.

The current implementation of the code formatter is deprecated, probably because it relies on some dotnet code that is going to be thrown out. I expect a proper replacement for the formatter in the future.

AFAIK, the Modeling option is selected by default. So, as long as you don't deselect it...

It doesn't even get a name to search for: function TRESTRequestParameterList.AddItem: TRESTRequestParameter; begin Result := Add as TRESTRequestParameter; end;

Have you tried using the parameterless AddItem function overload and set the Name, Value and Kind in its result?

Regarding speed, the docwiki link states at the end: Depending on the requirements about the restrictions mentioned in the lines above that quote, assigning Data may be the better approach, while CopyDataSet covers a broader use case.

If the tables have the same structure it might be as simple as using two TFDTable components with their attached connections and call CopyDataSet on the target one.

You didn't mention the Delphi version, but since Delphi 11 you can use the appropriate Sort overload taking a comparer, start index and count. procedure Sort; overload; procedure Sort(const AComparer: IComparer<T>); overload; procedure Sort(const AComparer: IComparer<T>; Index, Count: Integer); overload;

Seems it already exists: RSP-42131