dummzeuch

You're still miffed, apparently.

You might want to turn inlining on for debug builds if what you are trying to debug might be releated to inlining. But in most cases I would also turn it off because it is really annoying if you can't step into a function because it was inlined.

I just tried it in Delphi 10.2: I can only rename identifiers, it doesn't work for any other text or even special characters. But even with this limitation it is useful. And I know now, why I haven't used it: It's available since Delphi 2010 and until a while ago I was using Delphi 2007 for most projects.

I didn't even know it has a keyboard shortcut. I have never used it.

I'm sure I saw a similar functionality demonstrated in the Delphi IDE. Was it called SyncEdit? https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Sync_Edit_Mode_(Delphi,_C++) An older version of the documentation links to a video: But that's only for identifiers, not for generic text.

GExperts does not have this functionality.

Sorry, I couldn't resist letting ChatGPT write a reply to this: (I'll try to resist in the future though because I don't want this to escalate into a thread that consists of ChatGPT generated stuff only.)

And those command line compilers do not use the dccxxxx.dll files?

What they mean is "Don't use a patched IDE to produce anything (DLL, Exe, DCUs, BPLs whatever) that's going to be used in production".

For all I know about that patch it might replace a dll that the commandline compiler uses.

Does anybody know whether this patch also affects commandline builds? For me it would be a huge inconvenience to be forced to uninstall the patch every time I want to do a production build. But having a better working less broken IDE is definitely desirable.

Yes, that's exactly what I did. And then I asked the first question again and got the same wrong answer again. So it doesn't "learn" but simply adjusts the answer when you tell it it's wrong, but not for the actual question but only as a reply to you telling it that the answer is wrong. Question -> wrong answer -> "I's wrong, beause ..." -> correct answer (maybe, otherwise rinse an repeat) -> orignal question -> original wrong answer

Ask it that very same question again, it will then fall back the the same wrong answer as the first time or possibly modify it slightly but still be wrong. I tried that several times with different questions from different domains (and within the same session as it only "learns" within such a session).

No, that's not the case. But the Unit Tests don't use the DLL, so you can create test cases for the unit tests and then implement the code directly using that program.

No. It's something totally unrelated.

If you really want that kind of formatting: I am accepting patches.

There is no option (as far as I know, I might have missed it). And I remember seeing a comment in the original formatter sources from Egbert van Nes that he implemented this behaviour because he couldn't get the formatter handle these comments in any useful manner without breaking the source code. If anybody really wants to use that kind of comments: I am accepting patches.

Alternatively update to the current sources, compile a new DLL and try again. I just commented out these experts. They are more trouble than they are worth.

Check whether the two editor experts "Goto Previous Modification" and "Goto Next Modification" are enabled. If they are, disable them and see whether the problem goes away. And please report the result.

Are you using a mobile browser? If yes: I have exactly the same problem. The only way I found was to create a new post in a desktop browser and then delete the old stuff. I found no way to do that in the mobile browser (on Android).

I just noticed that in Delphi 11 hovering the mouse over the inherited keyword in a method while pressing the Ctrl key underlines that keyword just like it does with an identifier. But clicking on it does nothing while for an identifier it takes me to the declaration or implementation. Should this also work for inherited? Edit: It does work in other methods, I apparently tried it first on a method where it doesn't work for whatever reason. So, to answer the question: Yes, it should.

There are computers running old versions of Windows (or in our case even DOS) that cannot be upgraded easily, usually because of some special hardware requirements. As long as these commuters are not connected to the network, there is no problem with running old OSes. We still run 2 computers with Windows XP and 3 with DOS. The former will hopefully be replaced with Windows 10 this year, but the DOS machines will probably stay for some more years. At least one is required for the maintenance of some specialized equipment that is actually used with other computers that run Windows 10. Oddly enough, you can still buy hardware that is DOS compatible, but the supply for Windows XP compatible hardware is drying up.

Experience has taught me that I make mistakes (Yes, there was a time where I thought I was the Über-Programmer that does not make mistakes,. But that was about 30 years ago.). And there is still so much to program even if I don't re-write anything that already exists that I don't get bored. Of course if it turns out that the existing code is buggy, I will try to fix it or rewrite it. On top of that: One of the main reasons why I ended up as a programmer was that I was am lazy, so code reuse is a godsent.

We have been there before, haven't we? If I write something myself, I might introduce bugs (Yes, I'm not infallible and I know that). That's why we use library functions even though the functionality might not be that complex.

This large Open button does not look good either. I think a panel with an Open and a Cancel button of a standard size on the right hand side would look better. But this is just my personal taste.