Uwe Raabe

Thanks! Will be fixed in the next version.

As long as you choose the same setup mode (for me only / for all users) as before there should be no problem. The setup will detect the previous installation and replace the files without manipulating your settings. If that isn't the case with your installation, please contact me so we can find the cause.

Sorry, I just realized that we are on FMX here.

A fixed version V15.0.27 is available.

I have uploaded a new version, which is identical to that I am working with in the moment. In addition I have attached a map file for the 10.4 instance of this MMX version. Place the map file next to the MMX_BDS21.dll. This will give some more verbose call stack for the MMX part. The problem about empty floating windows is reported from others, too. Currently I have no idea what could be the cause, so we have to investigate further. Fortunately I can somehow force this problem to appear, when I create a layout where the MMX windows are undocked. Starting a debug session with closing those windows and opening them again after debugging actually shows these empty windows. At least that is a point where I can start. Just checked, it works perfectly with 10.3.3 MMX_BDS21.map

Do you get call stacks with the crashes? If so, I would provide a map file to get more information from it.

Yeah, that's better. Thanks!

As there must be a reason why it doesn't happen here: Any other non-standard plugins installed?

TMS Components used to have their own copy of Spin.pas.

Weird - I have never seen this. A quick test didn't show this either. I will try on a clean Delphi installation later. Meanwhile, can you try with a clean Debug Layout by deleting the Debug Layout.dst from %APPDATA%\Embarcadero\BDS\21.0\ ?

The idea was to write all units in all uses clauses with their full names instead of relying on the value in Unit Scope Names.

Not from the IDEs point of view. When a unit is referenced by a package that is not contained in that package, it looks for other installed packages for this unit. In this case it found one in the getit package. That is standard behavior since ages. Try compiling a package that uses VCL.Controls without mentioning anything in the requires clause. Delphi will suggest to add vcl.

Just guessing: You are referencing a unit named "Utils" in your project, which you missed to add to the package project directly.

Are you able to check without Unit Scope Names?

Have you tried MyMemo.HideSelection := False; ?

Define Large

Indeed, that could be misinterpreted easily. Although it is not necessarily a thread, but could as well be collecting data for a report or consolidate data monthly or other areas where multiple DB actions can be grouped. Obviously it is data is processed or retrieved in the background, where multi-threading steps in. Due to the integrated connection pooling, opening and closing a TFDConnection doesn't cost as much as it did in the past (BDE era that is).

That is exactly how I do it. The TFDConnection has the proper ConnectionDefName set. Then, inside the same thread, I open the connection, do all the query stuff and close the connection. All the queries linked to that connection are only used inside that same thread.

This may as well be the case for the specific browser currently installed at the customers system. That is another point for the component solution, as you definitely know the capabilities.

I am with Dmitry here. Having a separate connection per query is definitely wrong. Interestingly I never made use of that TFDQuery.ConnectionName feature. Instead I have a single TFDConnection instance for a specific part of the program where all necessary queries are connected to. Thus all these queries use the same connection and it works perfectly even in multi-threaded situations. I admit that identifying those groups of queries sharing one connection may sometimes be a bit tricky.

I often use this double slash comments at the end of a line to force a line break. const cArr: TArray<string> = [ // 'SELECT *', // 'FROM EMPLOYEE', // 'WHERE EMP_NO > 2', // 'ORDER BY EMP_NO', // '']; (Align line end comments is active here) Without these comments the formatter will produce this: const cArr: TArray<string> = ['SELECT *', 'FROM EMPLOYEE', 'WHERE EMP_NO > 2', 'ORDER BY EMP_NO', ''];

I am pretty fine with Advanced Virtual Com Port

Can you explain a bit more, please?

Seems legit. If you have a horizontal scroll bar there is no need for wrapping anything.

You are not alone: Parented controls with free notifications aren't scaled Frame with Assigned PopupMenu is wrong Displayed on high DPI A scaled form gets resized to design time ClientWidth/ClientHeight when embeded in a parent form