Uwe Raabe

You need separate packages for runtime and design.

It works as expected when I place the following code in FormCreate: var displayIndex := Screen.DisplayCount - 1; var display := Screen.Displays[displayIndex]; SetBoundsF(display.Workarea.Left, display.Workarea.Top, Width, Height);

You cannot directly set a specific display. Instead you position the form so that it is shown on the desired display.

I would rather like to know which magic makes your system behave different than most others.

You know that there is a place for such wishes?

https://quality.embarcadero.com/browse/RSP-16511

The Client info mentions <sqlite3_x86.obj statically linked> That means the SQLite engine is part of the exe or bpl. You cannot change that for the IDE.

If such an API would wrap things like "provide LSP with all necessary code for the current project" and "notify this interface with the requested results" that would make things easier. Even not trivial, though.

The LSP protocol is documented, but one has to implement the complete client code from the ground up and that is a pretty complex task. Currently there is no ready to use API provided by the IDE.

That is a scenario known not to work. Especially it is the driver behind RSP-35301

Under Tools - Options - Language - Delphi - Library check if the Library path contains c:\program files (x86)\embarcadero\studio\22.0\lib\Win32\release (or wherever you installed Delphi to). If that holds true, then check that FMX.FontGlyphs.dcu is available there.

My advice is related to styles that have a TPanel with a solid color. This rules out scenarios where a form wide image or pattern is visible as a (semi-)transparent background. If a TPanel is drawn in a solid color anyway, there is no benefit from drawing its parent background first. Thus setting ParentBackground to false omits some of teh drawing completely. It also helps when the form gets a full client TPanel containing all other controls to omit drawing that form client area on each paint event. With these simple steps we reduced flicker from highly annoying to no more perceptible.

The new release V15.1.3 is available now.

The release is scheduled for later this day.

I know and that is already planned. For the moment MMX provides an action Insert Attributes... which allows to select an attribute from a configurable list. If you customize the MMX toolbar to contain this action, you get a simple way to add attributes to existing fields, properties and methods.

ResourceOptions.ParamCreate is True?

No, you probably misunderstood. The Edit Layout offers an Options button, which takes you to the Welcome Page options page. There you can select a background image for each theme. You only have to make sure that when you change the image for one theme, you need to save this change before you start the process again to change the background for another theme. This has been reported already and closed as Works as expected: https://quality.embarcadero.com/browse/RSP-37883

After you change the background image, you need to save the dialog before selecting another theme.

https://quality.embarcadero.com/browse/RSP-38757

Currently this is not possible, but it is already in the feature requests. You can add attributes to existing fields or properties, though.

That is not the case here. Negative numbers are allowed. In both cases the non-zero borders are ordered correctly. The check for IsEmpty on both rectangles is a logical flaw. A Union of two empty rectangles can result in a non-empty rectangle. @Gustav Schubert Please file a bug report in QP.

That doesn't hold for applications that have to conform to some external guide lines like Corporate Identity or security considerations. Imagine a control software for a machine or automat that looks different depending on the OS used for the current hardware. What if the software on the stationary PC looks different to that used on an iPad for remote access. There are plenty of use cases where the look and feel of a software has to be independent from the underlying operating system - and be it just independent of its current version.

Isn't that a highly subjective question? Any answer would probably depend on someone's personal opinion.

The IDE has always been non DPI aware before version 11, so such a setting didn't even exist for versions below 11.

I had a related issue just yesterday where the synchronization between Editor and MMX failed completely. Normally moving the cursor inside the editor selects the current item in MMX. There are several source files where this doesn't work with build 2527. Although I wasn't able to determine the parts leading to that, I was able to fix it. I will provide a new version shortly.