Uwe Raabe

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.

1 hour ago, PeterPanettone said:

But would a rainmaker dance also work?

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.

2 hours ago, PeterPanettone said:

When will Embarcadero do something about it?

Is there a report for that?

5 hours ago, PeterPanettone said:

I will file a quality Report.

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

39 minutes ago, Angus Robertson said:

I would have designed it with a tick box, so it is obvious.

So, file a feature request...

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

2 minutes ago, Anders Melander said:

If only there was a way to solve that problem...

I don't see how downloading a VS Preview would solve that problem.

6 minutes ago, mvanrijnen said:

by default they do not have a version in it

What makes you think so? At least in my standard installation these folders are located under c:\Users\Public\Documents\Embarcadero\Studio\xx.x and c:\Users\<user>\Documents\Embarcadero\Studio\xx.x

7 minutes ago, mvanrijnen said:

Maybe the problem is that the Beta testing is done on "clean" systems only ?

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.

17 minutes ago, gioma said:

But what seems normal to you?

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.