Uwe Raabe

AFAIK, the path to the database is configured in emsserver.ini

Sounds like this one: RSP-40290 - RAD Server Console DLL not working

Not according to the feature matrix:

The reason why FMX Linux is only available for Enterprise and Architect is, that those are the versions targeting Linux as a target platform. With a Professional version you can't compile code for Linux.

It has it when I connect from here: Perhaps it depends on the license and active subscription status. AFAIK, there is no other official way to download it than my.embarcadero.com.

I didn't say anything about X:

Make sure that the DLL can be found.

The CreateXX are class functions. Therefore they don't change LocalMatrix itself, but return a new matrix instead. I'm not sure if I understand you right, but it might be sufficient to set the RotationAngle of the StrokeCube according to the vector V between those two spheres. The Y value should get the angle (in degrees) in the X/Z plane, while the Z value should get the inclination angle to that plane (not tested).

When working with styles, the Color property of the form is ignored. Unless seClient is removed from its StyleElements property, the forms client space is controlled by the style.

A TCustomPanel is not filled with a color, but with part of the style bitmap (defined in the GroupBox.Frame object). In a lot of cases this may be similar to a solid color, but it can as well be some texture or even a transparent area for some styles like Amakrits. You might really get the best results with setting the labels Transparent property to True.

What type of control is the Parent of the label (TForm, TPanel,...)?

See here: Update: You can see what colors are returned here: function TUxThemeStyle.DoGetStyleColor(Color: TStyleColor): TColor; begin case Color of scBorder: Result := clWindowFrame; scButtonDisabled: Result := clBtnFace; scButtonFocused: Result := clBtnFace; scButtonHot: Result := clBtnFace; scButtonNormal: Result := clBtnFace; scButtonPressed: Result := clBtnFace; scCategoryButtons: Result := clBtnFace; scCategoryButtonsGradientBase: Result := $C0C0C0; scCategoryButtonsGradientEnd: Result := $F0F0F0; scCategoryPanelGroup: Result := clMedGray; scComboBox: Result := clWindow; scComboBoxDisabled: Result := clWindow; scEdit: Result := clWindow; scEditDisabled: Result := clWindow; scGrid: Result := clWindow; scGenericBackground: Result := clBtnFace; scGenericGradientEnd: Result := $C0C0C0; scGenericGradientBase: Result := $F0F0F0; scHintGradientBase: Result := clInfoBk; scHintGradientEnd: Result := clInfoBk; scListBox: Result := clWindow; scListBoxDisabled: Result := clWindow; scListView: Result := clWindow; scPanel: Result := clBtnFace; scPanelDisabled: Result := clBtnFace; scSplitter: Result := clWhite; scToolBarGradientBase: Result := $C0C0C0; scToolBarGradientEnd: Result := $F0F0F0; scTreeView: Result := clWindow; scWindow: Result := clBtnFace; else Result := clNone; end; end;

That depends on the definition of correct.

As I never use any dark theme myself I am thankfully not affected. Nevertheless, I would rather question the decision to make clBtnFace and clWindow looking quite similar in the dark theme, while they give a perfect contrast in the light theme.

I did some deeper investigation not concentrating on the colors itself and it turned out that HideSelection was True under some conditions. I fixed that in the latest beta. Can you please try and see if this helps a bit?