Uwe Raabe

In case standard Paypal works, you can send money to my account (use may name or email address) with a quick note and I will add that to the MMX Icon pool.

Amen!

You are still using connection pooling with this approach. Connection pooling doesn't pool TFDConnection but TPhysConnections which can be accessed by TFDConnection.ConnectionIntf.

clear FDQuery1.ConnectionName add a TFDConnection set its ConnectionDefName to your need set FDQuery1.Connection to that connection

Isn't that what they call cyclic dependency?

Took me a while to notice that I must not close the window with the cross button in the title to force that error.

Can you give me detailed steps for that? A basic test just worked.

Oh, I hate it when the same thing is done at several places in different ways OK, will look into that. Well, that's strange. Can you send your debug layout file (usually Debug Layout.dst somewhere beneath %APPDATA%) to support@mmx-delphi.de, please? Perhaps there is something inside where MMX is stumbling upon.

I can see this here, too. As it is only a performance problem I moved it behind the functional problems in the priority list. When its running stable I can make it faster.

I can think of TFieldCache in System.Classes replacing several expensive calls to FieldAddress.

A new Beta V15.0.0.2343 is available. Make sure to remove a previous V15 beta before installing build 2343 or higher. The new installer is most likely incompatible with the old one

That's the point! It doesn't matter in which state the IDE is closed. The setting alone controls the visibility of the TOD on startup. Not sure about that one. This is a screenshot of MMX 13.1.1 on XE2: The Light theme on Tokyo is the standard Windows theme, so it uses the OS colors.

But you are on an active Update Subscription, aren't you?

That's interesting! I quoted right from the Rio DokWiki, but perhaps the offline help is a bit different. Although, my German offline help is a translation pretty close to the English DokWiki one. Nevertheless there are other places in the docs that support the wording you quoted, so I guess it is probably completely unclear which behavior is actually intended. So the least we can expect from reporting that issue is a documentation consistent with the compiler - however that turns out then.

Yes - and I don't believe it is a restriction of the CE.

Continue is supposed to jump to the end of the current loop (re-evaluating the condition) and not to the beginning. Thus the until statement is evaluated which in this case ends the loop. So, yes, it is the way it should be.

Rewriting the toolbars rendered all settings invalid, so what you see is the default setting. Customizing the toolbar (when it actually works - hopefully in the next beta) allows for more options. I will investigate the state problem.

Have you updated your license?

At least to my knowledge that is not quite correct. If you are on an active subscription you can contact support for that, if not you need to contact sales. The reactivation is done in both cases. Do you know of any non-subscription user not being able to get a license bump from sales when asking for it? Note: This is just to get the facts right and shall not imply that I am actually supporting this scenario.

Besides making C# people coming to Delphi feel a bit more familiar. The concept of Delphi strings tends to stay a mystery for non-Delphi developers.

To allow proper theme support V15 removed the dependency on Toolbar 2000 and TBX in favor of standard VCL Toolbars. This makes it a bit hard to achieve the same functionalities that were previously available. Currently the editor toolbars are only supported on the top and cannot be moved. I am still investigating how to make toolbar docking work (probably with TCoolbar controls) with proper theme support. Unfortunately we will have to live with this restriction for the time being. The access violation does not happen here in the development branch, so it might already be fixed in the next beta drop. Otherwise we will have to find the necessary steps to reproduce.

Thanks for reporting. I will look after it.

public const Empty = ''; From Delphi 10.3.2 Rio.

There is even a const named Empty in TStringHelper, right accompanied by the function IsEmpty. I agree that the value of both is questionable at least.

Yep