David Heffernan

I need to do work before I can do that. It's really frustrating that I cannot have 11.2 and 11.3 installed on the same machine.

I'll bet that there is a clean solution to your problem, but not the one you are trying. Instead of asking about pre-processing DEF files, why not ask about the root problem, rather than the solution you imagine using, which you now know is not possible.

Doesn't EXPORTS CCfgClassNew work?

I'd been working with 11.2 to get my app looking good in high DPI settings. This was all fine. Now with 11.3, loads of things look terrible again. One step forward, two steps back. 'Twas ever thus.

No prizes for guessing what happened there. I did a complete uninstall, and then a re-install succeeded.

This aspect of installation isn't much fun

Pretty hard to make such recommendations. Really depends a lot on how your users want to use your software. Are they going to want to have floating licenses? Metred usage? Cloud hosting of license manager? We have a lot of customers that don't have a shared network and collaborate entirely in the cloud with 365 or similar. Solutions to allow such users to share licenses aren't trivial. Of course, you may know that you will never have customers with such needs, or at least not in the short term.

This statement is incorrect unless I am very mistaken. Please show your main form code and the project file.

Not in a def file, perhaps you aren't familiar with def files. They are used to specify exported functions, typically at the link phase in C and C++ tool chains. See: Module-Definition (.Def) Files | Microsoft Learn

No. No language or library support for anything like this.

Yes.

No. When OwnsObjects is true, as it is here, the list is the owner.

Likely because it has been properly designed by skilled practitioners in this field.

Works fine here on the latest Delphi. Are you still using Seattle?

Yeah, defo

I definitely hope that no Delphi code is running by 9999. I'd be amazed if there were any humans left on the planet when that year comes around.

No.

We don't need to read the files, and we don't need to write in all supported formats. I guess the only real complication I can see here is the PNG format for 256px images.

Sad to see two lookups rather than one when the key is not in the dictionary. But that's the sort of thing that happens when your collection choice is limited. Given those constraints, I doubt this can be bettered. Confused actually. Your previous posts have rejected writing new code because it needs to be tested.

You could search for a library with support for this. Otherwise the ico format is very simple and comprehensively documented.

I don't think there is any generic collection that meets your needs in the rtl. Perhaps you'll just have to give up.

Why let lack of knowledge get in the way of offering suggestions?

In a language without exceptions, how do you implement your proposed solution? Answer, you can't.

In a programming language that didn't have exceptions. Like C. It's then up to the programmer to check if the operation failed. Inspect the FPU status word to do that.

Floating point exceptions got masked by the library you used. We've covered this hundreds of times here and elsewhere. Some websearch will reveal more.