Uwe Raabe

Why do you think this information is stored in two different places?

How are your settings about saving the project desktop? Is the MainForm auto-created in the dpr?

Less hugs, less bugs...

According to the docwiki, InternalCalc fields are only supported in TClientDataSets: On the other hand, FireDAC mentions an example of using fkInternalCalc.

Can you provide some code?

If it is declared as fkInternalCalc, its value can be set in the OnCalcField event when the dataset State is dsInternalCalc.

You can find a list here: Exposing DataSnap Server Methods

There is no Tortoise folk. That are two totally different tribes that just picked the same name.

I guess I finally found the cause: When you edit a property inside an interface the available visibility values are limited to default. Now edit a property in a class and the visibility is also default. The reason is that the current visibility is set before the allowed values are set. A fix will be available shortly. Can you check if you have Pick up any style comments as documentation checked in your MMX Documentation settings? That would take the commented method declaration as a comment belonging to the one below. Consequently the comment is moved together with the method declaration.

Yeah, I have seen that, too. My perception is, that it happens when you just ran the current project in the debugger.

That can't happen using this approach. Internally the Post executes a parametrized UPDATE statement, which is exactly what you suggest.

How would you know that? It might as well been noticed, but either too late or of lower priority to make it into the release.

Users of ModelMaker may appreciate the availability of a Modelmaker IDE Integration Expert for Delphi 10.3 Rio. Note: ModelMaker is a separate Native Delphi Visual modeling and Refactoring tool based on UML™ 2 technology. Not to be confused with MMX Code Explorer. More info here: ModelMaker IDE Integration Expert for Delphi 10.3 Rio released

Go to the download page for MMX: https://www.mmx-delphi.de/downloads/download-info/mmx-setup/ Next to the version field there is a link Previous versions. For XE5 you have to go for V13.

TStringHelper.Compare has an overload where you can give the option TCompareOption.coDigitAsNumbers for this purpose.

That is exactly what I tried to address with Package Magician. Unfortunately some poorly programmed packages just refuse to unload correctly, which sabotages the task of Package Magician.

Currently not at design time (but a good feature request). You can write a small program that does this: for I := 0 to PngImageList1.Count - 1 do PngImageList1.PngImages[I].PngImage.SaveToFile('Image' + I.ToString);

And that lead to the first picture? And this results in the second one? Sorry, but I just try to get the steps leading to the problem. Can you either list exactly what you are doing - or better make a short video?

Are these different desktop files or the same?

That is my impression, too. AFAIK, the CE is technically equivalent to the Professional with the same license limitations (apart from the CE ones of course). While it is even possible to target remote servers with FireDAC in the Professional Edition it is just not allowed license wise.

Indeed, that is currently a known limitation.

BTW, a probably more recent version of the the code is available at https://github.com/UweRaabe/DataSetEnumerator

Are your with that? The docs about csFreeNotification say: That said, csFreeNotification is set when another component wants to be notified when the current component is destroyed. There is no specific action ongoing while csFreeNotification is set. In addition, csFreeNotification is only set but never unset.

Perhaps a QP entry might be helpful?

... and makes that TEditWindow instance the owner of a to-be-scaled TCustomForm. What bothers me more ist the csFreeNotification condition at the end. I mean, how is that related to scaling?