Uwe Raabe

Well, at least that is a specific requirement. It is just that I would never be in that state (i.e. MMX not open), thus I didn't even consider this case before. You can disable that feature in General - Delphi Editor - Options - Auto toggle Object Inspector and Code Explorer, but then it will never be shown with F12.

Indeed - and I am not very satisfied with it. I haven't had the time to create a proper replacement yet.

This is a known incompatibility between design packages and experts compiled with 10.3.2 when used with 10.3 or 10.3.1. Currently there is no workaround for that besides having two separate DLLs. I'd rather avoid that due to the build and setup nightmare that is causing. Nevertheless I am confident that Embarcadero will provide a hotfix addressing that problem pretty soon. In the mean time MMX 15 for Rio can only be used with 10.3.2, sorry about that.

@Cristian Peța That looks like a perfect candidate for the Visitor explained in this article: The Visitor Pattern – Part 4 avoiding all the is type calls and type casting. The above code would break down to implementing a TTranslator class like this: type TTranslator = class(TVisitor) protected procedure IterateComponents(Instance: TComponent); public procedure VisitAction(Instance: TAction); procedure VisitComponent(Instance: TComponent); procedure VisitControl(Instance: TControl); procedure VisitCustomForm(Instance: TCustomForm); procedure VisitCustomFrame(Instance: TCustomFrame); procedure VisitMenuItem(Instance: TMenuItem); end; procedure TTranslator.IterateComponents(Instance: TComponent); var I: Integer; begin for I := 0 to Instance.ComponentCount - 1 do Visit(Instance.Components[I]); end; procedure TTranslator.VisitAction(Instance: TAction); begin end; procedure TTranslator.VisitComponent(Instance: TComponent); begin IterateComponents(Instance); end; procedure TTranslator.VisitControl(Instance: TControl); begin if Instance.Action = nil then begin end; end; procedure TTranslator.VisitCustomForm(Instance: TCustomForm); begin { translate form parts ... } { translate components } IterateComponents(Instance); end; procedure TTranslator.VisitCustomFrame(Instance: TCustomFrame); begin { translate frame parts ... } { translate components } IterateComponents(Instance); end; procedure TTranslator.VisitMenuItem(Instance: TMenuItem); begin if Instance.Action = nil then begin end; end; Instead of calling TranslateForm(MyForm) you would call Translator.Visit(MyForm)

@Dokkie Thanks for reporting. I uploaded build 2345 with a fix for that.

Thanks, now I can reproduce.

That is not breaking cycles, but actually creating them. Cyclic dependencies in the interface simply don't even compile. Therefore cyclic dependencies are only possible in the implementation section.

There is a new beta drop (build 2344): https://www.mmx-delphi.de/downloads/download-info/mmx-beta-build/

As I cannot reproduce here there is probably more to that. I have the MMX Explorer pinned and the OI collapsed in a tab in the same dock host. Pressing F12 switches from Code to Design and pops out the OI, or from Design to Code while the OI collapses again making room for the Explorer. What is your scenario?

Could it be that those highlighted properties are those to be linked to other components?

They move the code away from the class constructor into the initialization section and revert that in 10.4 for instance.

Thanks! Seems to have worked then.

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?