Uwe Raabe

Better remove the trailing dots in Frame and Form. Plain group names get that automatically appended when looking for a match. F.i. a simple entry like Form matches unit names Form, Form.Tools and Form.Test, but not FormTest. Assuming that the x stands for the obfuscated parts in your screenshot, I get the following results with this Groups: Winapi System.Win System Vcl Data FireDAC cx DM x x.Tools Frame Form uses System.Classes, System.SysUtils, System.Variants, System.Generics.Collections, System.Generics.Defaults, System.DateUtils, System.Math, System.StrUtils, Vcl.Imaging.pngimage, Data.DB, FireDAC.Stan.Param, FireDAC.Stan.Option, FireDAC.Comp.Client, FireDAC.Comp.Script, x.Classes.Common, x.Classes.Base, x.Classes.Data, x.Constants, x.Types, x.Database.Common, x.Preferences, x.Tools.Mapping, x.Tools.DateTime, x.Tools.TryFinally, x.Tools.Json, x.Tools.Regex, x.Tools.IO, x.Tools.BitMask, DataModuleTextConstants;

And for completeness: What are the defined groups?

That's default.

Not yet. It is. All units not matching a group are placed after the grouped units.

Brackets denote a list of unit names forming a group. I use it f.i. for keeping the ToolsApi units together: (ToolsApi,DesignIntf,DCCStrs,DockForm,TabDock) The example shows a glitch in the TMS unit naming: Adv* followed by (BaseGrid) keeps the TMS Grids unit together. The other example (ZipForge) is used when a group consists of a single unit name only. Omitting the brackets would take it as a unit scope name instead.

With Premium you get early beta access, while an active subscription entitles you to participate in the public beta. In most cases the latter should be sufficient.

Unfortunately not - and it would be quite difficult to implement that with reasonable effort. Wildcards are handled by TMask.Matches and that has a hardcoded Upcase in its implementation.

I didn't try it.

Now it is.

The Migration Tool has a special mode for migrating to a newer version, which requires to select the appropriate settings. Did you follow these when migrating? If yes and it didn't work, you should file a bug report.

This is fixed in Delphi 12.

Unfortunately that is by design as comments in uses clauses are considered not clean. Background: It is pretty hard to connect the comment to one of the used units - there is too much convention involved with this. Also, line end comments don't play well with grouping and line wrapping. There are non plans to change this any time soon.

Can you reproduce on a minimal project? I just copied that uses clause into a fresh VCL project and everything works as expected.

Can you show the Unit Scope Names entry in your project options, please?

Can you check the MMX properties Key bindings for Format Uses Clause, please? Also make sure that no other plugin steals that shortcut.

With Delphi 12 the Index type of TList as well as Count has changed from Integer to NativeInt. While this has no effect in 32 bit, with 64 bit it definitely has. Check all descendants of TList if there are any declarations of properties (f.i. Items) or methods with Index type Integer which act as overloads for the base declarations. Then change these Integer types to NativeInt.

I believe that not reporting an issue most likely lead to nothing.

Is there a report for that?

No need for that: Add a FILTER SEARCH BOX in the Install Packages dialog

The following code lists 355480 files in less than 15 seconds on my system. program TestGetFiles; {$APPTYPE CONSOLE} {$R *.res} uses System.SysUtils, System.IOUtils, System.Diagnostics; procedure Main; begin var sw := TStopwatch.StartNew; var arr := TDirectory.GetFiles('C:\Windows', '*', TSearchOption.soAllDirectories); Writeln(Format('%d Files, %d ms', [Length(arr), sw.ElapsedMilliseconds])); end; begin try Main; except on E: Exception do Writeln(E.ClassName, ': ', E.Message); end; Readln; end. The dir command needs a lot of time to display the files, while the Delphi code avoids that.

Indeed! It is working here, too.

It may depend on the uses list and its order. The different Stat units register different default values: {FireDAC.Phys.SQLiteWrapper.FDEStat} initialization TSQLiteLib.GLibClasses[slDefault] := TSQLiteLibFDEStat; TSQLiteLib.GLibClasses[slFDEStatic] := TSQLiteLibFDEStat; {FireDAC.Phys.SQLiteWrapper.SSEStat} initialization TSQLiteLib.GLibClasses[slDefault] := TSQLiteLibSEEStat; TSQLiteLib.GLibClasses[slSEEStatic] := TSQLiteLibSEEStat; {FireDAC.Phys.SQLiteWrapper.Stat} initialization TSQLiteLib.GLibClasses[slDefault] := TSQLiteLibStat; TSQLiteLib.GLibClasses[slStatic] := TSQLiteLibStat; Manually adding FireDAC.Phys.SQLiteWrapper.FDEStat to the uses may solve the problem. I'd rather set the mode to an explicit value instead relying on a volatile default.

That is mentioned in the What's New: FireDAC SQLite Version Update

So, file a feature request...

It has been quite a while, but I had a good experience with CANUSB.