Sherlock

Damned be those blogs... The target of this blog is obviously a more experienced clientele, and Marco failed to mention that. What you did in post #4 was half way right. You need to add the declaration of those methods in the interface of the class TForm1 as well - right after FormCreate should be fine.

OK, that is not enough. You need to expand the declaration of your TForm1 class to include the definition of those methods. I suggest you work through some form of Delphi primer first. Just to get to know the basics.

What do you mean "when I do this"? Do you enter those procedure stumps without interface declaration? Please check the documentation on this http://docwiki.embarcadero.com/RADStudio/Rio/en/Procedures_and_Functions_(Delphi)

Slightly OT: dhsPinger has an ominous ring to it. Pinging the DHS sounds like something you should not do lightheartedly.

Aye, there's the rub. I propose exchanging DotNet with <SomeLanguage>. But folks keep saying "I want <SomeLanguage> feature x, because that is so cool, and I simply can't write my application without it". And then we get some half cooked thing which resembles <SomeLanguage> feature x by intent, but is buggy and breaks other stuff...

Something tells me, it was not the team that took that bite...

Yeah, all the cool kids want to JavaScript, while banks and insurance companies are going out of their way to pay regal salaries to those old COBOL geezers. COBOL delivers, where JS just looks shiny.

I didn't read the book, but I'm guessing that only applies when you add those programmers to the same problem. Luckily Delphi has a ton of problems, that could each feed a programmer for at least a month

And in the end, what is the effort worth? Just to say: "In my product 1+1 is still 2 but it looks better than the others".

That will fail quickly for word wrapped captions.

I don't hate them, I just don't need them. 😉

I have gone through the code and replaced those pesky FreeAndNils with FreeMem or Dispose, whatever fit. It compiles fine now, but next step is to redesign the code to get rid of those ancient pointer thingies altogether. Quite annoying. Thanks everyone for your help and insight!

You could think that to be the reason, but I'm looking at code with tons of PArrayOfByte like what I posted. This seems like some very, very old code and an array of byte is rarely implemented as a class is it? Much less back in the olden days.

@Dalija Prasnikar Thank you! I thought that might be the reason. Which brings me to my earlier question: Why use FreeAndNil on Pointers in the first place? Do you have any idea?

German is OK as well I would always use indexed format specifiers though.

Sorry, didn't catch the subform. Can't help then.

We are not aware of the complete wording of said offer, that is something between Andreas and Embarcadero. What we do know from past statements however, is that some form of NDA or other contracts might be involved. But lets not speculate. IDEFixPAck will come once Andreas gets to install a 10.4 CE, which will come out with 10.4.1. So keep your fingers crossed, that this well be soon enough.

Do you mean named pipes?

Of course you might exclude existing users. Those with 32Bit iOS. How many are there, though? What do you know about your users? Do you have any information? However, that still wont lead to a new AppID.

I totally understand, but some eye candy just wont work. And sooner or later some other stuff will follow. This discussion is as old as Windows itself. It used to be "my customers only run DOS" then became "my customers only run 16Bit Windows" over to "my customers only run WinXP" to what we have today. Someone in that story has not learned, and should be beaten with a set of Windows installation floppies: Hardware manufacturers that create one version of their controlling software and never update it, or for an ungodly price. We could break our ears and keep our software running on DOS, or just inform the customers and let them wise up and do a pitchfork and torch run on their machine manufacturer. After all, it is your hide they'll be after if something wont work because their system is outdated - not that this is the case right now.

Thanks for the heads up. Did you report it at QP?

Some files are in use while Delphi is running, so they can't be deleted. I am not sure there is any mechanism that can bypass this. Another subject for Embarcadero to look into.

Now that is a swift and elegant recovery from the blunder earlier. Respect @Embarcadero.

It's called consistency and is considered to be a good thing...most of the time.