Uwe Raabe

Yeah, that's kind of a chicken and egg problem. The simplest approach would be to execute MMX_Setup again.

Yes. it should. It is the search field for IDE Insight and should find almost everything that the IDE is aware of.

You can open a second edit window and (since D11) put the form designer in that one. That will mimic the former floating designer pretty well.

Sometimes it helps to rename the datamodule to avoid a name clash with the internal one. Naming a datamodule dmImages may be OK for a standalone application, but for an IDE plugin that seems not to be wise. I made this experience myself.

This can also happen when the missing DataSource is not located at the same form/frame as the DB components and the IDE fails to open the datamodule (or wherever this datasource resides) for whatever reasons. I had similar experiences with actions located in a datamodule. If by any chance that datamodule shares its name with one of the IDE internal ones (including those in 3rd party modules) that can be the cause of breaking the linkage.

The settings are in the same dialog as the list of recent files and projects. The default is 10 projects and 15 files.

As long as it keeps doing what it was made for even in newer Delphi versions I would not rate that negative. There is plenty of software just refusing to work anymore where I would love to see it in some maintenance mode.

TDataSet offers a method CopyFields for that.

There is a function for that in System.IOUtils: MyByteArray := TFile.ReadAllBytes(filename);

Sure that: var bmp: TBitmap; png: TPngImage; begin bmp := TBitmap.Create; try png := TPngImage.Create; try png.LoadFromFile('c:\Program Files (x86)\Embarcadero\Studio\21.0\bin\Artwork\Windows\UWP\cppreg_UwpDefault_150.png'); bmp.SetSize(png.Width, png.Height); png.Draw(bmp.Canvas, TRect.Create(TPoint.Zero, png.Width, png.Height)); bmp.SaveToFile('c:\temp\test.bmp'); finally png.Free; end; finally bmp.Free; end; end; Depending on your Delphi version you might even succeed with a simple bmp.Assign(png);

What about just Draw the Png to the Bitmap Canvas?

OK, inline const and inline var are not fully covered by MMX in the moment. It is on the ToDo list, though.

RAD Studio includes Delphi and C++ Builder, but you can purchase each separately.

When you use it on an existing method to change its name.

Yes.

IIRC, there used to be a Delphi Driver Development Kit at least up to Delphi 2007, but I never had the need to make use of it.

Revenue is proportional to number of sales and price.

Not sure where you get this from. The price for the first year and the price for the renewal are clearly shown side by side: https://www.embarcadero.com/app-development-tools-store/delphi They also offer subscription for multiple years if you ask for it.

Not sure if I understand, but you can extend the life time by renewing your subscriptions for one or multiple years. Are you referring to the annual subscription cost being too expensive?

I will never run out of activations, because I use a Named Network License provided by a local ELC server. This allows me to install Delphi on as much targets I want as long as I keep the same user name on all of them.

That's why renewing the subscription is highly suggested. The commercial versions can be run indefinitely. As mentioned before, security patches are very rarely necessary in Delphi. There are plenty of people out there working with Delphi versions years old, if not decades.

Note, that the implementation of TIBase<I> can be in another unit, where neither IFooBroker is known, nor that TIFoo is a type instance for IFooBroker. Nevertheless that unit has to be compiled before the unit containing IFooBroker and TIFoo. The compiler should only allow anything of type I as a parameter for inherited Create. That will rule out to grab any interfaces via Supports or AS constructs. Please file a bug report.

No, MMX is not open source and I don't have control over that fact.

That is a decision made by Embarcadero based on the nature of the patch.

I cannot believe that this is real code. To me it just looks like made up. If for any reason there is a need for a global procedure ResetHoverColor acting on Form1, the straight forward implementation would rather be procedure ResetHoverColor; begin Form1.ResetHoverColor; end;