dummzeuch

Pointers have their uses, but they come with risks. Skilled programmers know how and when to use them, but most important, they don't use them when they are not necessary. They also know that pointers can make debugging hell. Unfortunately there are many programmers who use pointers where they are not necessary. Of course they still think they are skilled, because they use pointers.

Alternatively omit the Count entry and simply read all entries in the section [mru].

Are you talking about just the tabs for Code, Design and History? No, these cannot be hidden. But if you are talking about the docked windows below that, containg messages, refactoring etc, you can undock that window and dock it somewhere else (I dock most of these on the right hand side) or simply close it. Don't forget to save the desktop otherwise it will pop up again any time the desktop is loaded.

Is that just me or is Delphi adding itself to the main list of the Windows Start menu every time the IDE is started? Is there an option to disable this annoying behaviour? My start menu is full enough, I don't need additional entries that come back even when deleted.

I doubt that it is this "helpful" Windows functionality. I start Delphi 10.2 and 2007 a lot more often than Delphi 12 and they don't show up there.

And also, in the most recent source code (no release yet, maybe this weekend, but no promises), it supports multiline strings.

There are currently some unit tests for the GExperts code formatter that fail. It all depends on how spaces after comments {comment} or (*comment*) are handled. A How should the code formatter handle the following code: procedure bla; begin {some comment} SomeStatement; end; A1 Keep the space after the comment: procedure bla; begin {some comment} SomeStatement; end; A2 Remove the space after the comment: procedure bla; begin {some comment}SomeStatement; end; B what about this code: procedure bla; begin {some comment}SomeStatement; end; B1 should the formatter leave it as is? B2 should it insert a space, so it gets changed into: procedure bla; begin {some comment} SomeStatement; end; C what about this code with multiple spaces after the comment: procedure bla; begin {some comment} SomeStatement; end; C1 should the formatter remove the spaces: procedure bla; begin {some comment}SomeStatement; end; C2 or should it reduce them to one space: procedure bla; begin {some comment} SomeStatement; end; C3 or should it leave them as them as they are: procedure bla; begin {some comment} SomeStatement; end; The current code will always remove the spaces, so its A2, B1 and C1. I'm tending towards keeping the number of spaces as they are, that would be A1, B1 and C3. I'm definitely not going to make this configurable. I wouldn't even know how to describe this configuration option.

That's actually the same frame which is shown in these two dialogs. If a project is loaded, you are viewing and possibly changing the project's configuration. If no project is loaded, you are viewing and changing the default packages loaded by the IDE without a project and for new projects. As far as I remember that has always been the case. (Or I might have misunderstood you.)

They do. As long as you haven't got an alternative development environment for the work you rely on, you will have to pay for Delphi or stay with an older version.

On the first page of the wizard, there is a button for doing that, somewhere on the bottom left. I can't look up how it is called now because the installer wants to uninstall everything first when I start it now.

That's for historical reasons. And with the "new" strict keyword even this can be prevented. If you only want to access the Canvas property you can change your TGetCanvas class to this: type TGetCanvas = Class(TCustomControl) published property Canvas end; This is used by all the classes that derive from TCustomControl to publish protected Canvas property, so it will always work.

That's not really an editor feature, is it?

I wrote my own IDE "integration" using the tools menu a few years ago. Scooter Software actually contacted me about it when they ware approached by Embarcadero to license BC for the IDE integration. I like to think that my simple work was what sparked the idea. Having said that I don't like the IDE integration either. Its complicated to use.

I expected this but just confirmed it: The GExperts code formatter does not handle multi line strings correctly (bug #337) For now the workaround is using the comment to prevent formatting ... read on in the blog post

That was easier than I thougth: As of revision #4112 the formatter now actually does support multi line string literals. And only those unit tests that already failed still fail. Of course that does not mean that I have not broken anything else. You are welcome to build your own dll and test it.

Inline variable declarations in begin end blocks already worked fine.

fixed: https://sourceforge.net/p/gexperts/bugs/336/ Thanks for the report and the patch.

Did you know that the limited Beyond Compare that comes with Delphi, can be used to show the differences of two arbitrary files? Just start it with parameters or even just start it and use drag and drop to diff the files. I have even configured it in TortoiseSVN as the diff viewer.

Hm, I have just read through that page and another one but I'm not quite sure whether I would find inline hints useful or annoying. I'd probably have to try it.

OK, so what are examples for editors that are not "stuck in the Stone Age"?

Just to confirm: Your first example is how you think it should be formatted?

HKLM\Software\Microsoft\Windows NT\CurrentVersion ProductName: REG_SZ On my Windows 10 pro it says "Windows 10 pro". There are several other entries that might be of interest, e.g. DisplayVersion="22H2". Of course this can easily be manipulated by an administratorl

Remove matching lines

Which plugin provided multiline strings? Or are you talking about the property editor for multipline strings?

No, I wrote an expert which removes those totally useless comments.