Uwe Raabe

Another answer can be found on StackOverflow (although for alTop) Delphi: How to programmatically adjust visual ordering of components with align = alTop

In addition I would pre-calculate the timestamp (Now) inside the thread. Otherwise you'll get the time stamp when the main thread handles the call. Not sure if this is actually significant, though.

I am reluctant to write the trivial case, but it won't execute if just no exception bubbles up to that point, perhaps because it is caught (not necessary handled properly) at some deeper level. Just curious: What problem are you actually trying to solve?

Extend that to all dfm files.

It is indeed. That is also the reason why a couple of bugs are fixed and features implemented the way they are or not even at all.

🤣 you nailed it!

There is no copy&paste here. That are just the release notes for Delphi 11 Alexandria when it came out. The relevant info for the update releases are linked in the Notes at the top:

Those are for Delphi 11.0 and I have doubts that they are still valid for 11.3. See: RSP 37609: PAServer ships with Python 2.7 dependencies - which are no longer available in macOS 12.3

Given that it is even not intended to work I count that as a pro

In Tools - Options - User Interface - Editor Options - Search there is a percentage value to play with.

OK, let me reword it this way: I would rather switch my settings or find another workaround than going back to 11.2!

I would rather buy a new monitor instead. Was really a good investment.

Does it really matter?

It is probably another module (BPL or DLL) that is internally used by the mentioned package, but is either missing or fails to load.

TFDBatchMove provides the AnalyzeSample property to control that.

As ever so often, the pragmatic solution probably lies somewhere in between...

Is there a reason why you don't use the original InterBase installer and select Client Only in the Choose Install Set dialog? Where did you get the information, that the steps you describe are sufficient?

Have you tried the TOAuth2Authenticator component linked to a TRESTClient? It has a context menu that lets you specify play with some parameters.

I have encountered the same ac couple of times, but I was not able to reproduce it reliably and thus cannot actually debug it. It is my impression that it helps to have MMX visible in all desktops.

That's the basic idea: You implement the code in the Actions OnExecute event instead of the Buttons OnClick event. That allows to use the same code for multiple controls (f.i. Buttons) spread over different forms or frames.

Or a couple of other keys like the decimal point or the DIV key on the numeric keypad.

If it can be reduced to the LSPServer alone, that may be (although I still doubt that), but in many cases part of the problem also lies inside the IDE/Compiler and cannot be fixed with an LSP replacement alone.

In that case the problem seems to be outside of the code in question. My guess is that either RESTRequest is destroyed in between or some memory is overwritten, but I doubt that the component itself is responsible for that. That's why I asked for a reproducible test case. Usually when one cannot create a reproducible test case, the problematic code part lies outside of the tested one.

Can you make a minimal example to reproduce? Oh, and: In contrast to your statement you don't clear the params in the shown code. BTW, you should keep the BaseURL as is and put the endpoint in RESTRequest.Resource instead.

I am not aware of such a setting. Given that my attributes often are multiline itself, I wouldn't even think of such a behavior, but that is just MHO.