dummzeuch

There have definitely been some improvements in the Delphi 11 IDE, but also quite a few bugs, in particular in the support for HighDPI. Most of them have been fixed in 11.3, but it's far from flawless. But you might never encounter some of these bugs, depending on the hardware you are using. I can't really compare to Berlin because I have never used it. The version that currently works best for me is 10.2 (Tokyo). I'm looking forward to Delphi 12 though: New Features, hopefully some bugfixes and very likely new bugs. (I'm not in the Beta, so this is purely guesswork.)

I don't think that's possible with the currently available options.

The first is a command line tool. The second doesn't make much sense for the average Delphi user, only if you want to write a plugin for hacking the IDE. The third does not work within the IDE.

This is not the right place for feature requests. You should post it on Sourceforge, where the chances are higher that I see it when I have some time on my hands. Of course, feel free to implement it yourself and append a patch to the request. It's not rocket science, you know.

Actually I invested many hours to improve the performance of the formatter. But that was many years ago. I don't know how I found the time for that. Probably by not wasting so much time in front of the bloody TV...

No, there are other kinds of strings where this could be usefull, e.g. JSON or CSV data for e.g. unit tests.

Hm, looks like I actually finished that work I was talking about, and had forgotten 😉

That is not a menu of the IDE but one added by some plugin or possibly a property editor. (Or it is part of a higher SKU than I know, e.g. Delphi Enterprise or Delphi Architect)

There are only two options for now: Hide Window Menu Move the Component menu to Tools Both can be found on the IDE tab of the GExperts configuration dialog. I have no plans exending this functionality, but I am - as always - accepting patches.

@Attila Kovacs I had started some work in this direction (not just for TMenuBuilder but also some of the other tool windows that seem to open at random positions (Action Manager, Popup Menu Builder ...) but never finished it. If you have got some working code, I'd be willing to try including it into GExperts. Best way would be to open a feature request on Sourceforge, attaching the code.

You are missing the point. We are not talking about missing/incomplete/buggy IDE features here (or at least I am not) but the pain in the lower back any new language features poses for third party tools that parse the source code, in particular the GExperts sources formatter, where the code isn't really well structured.

It has been donated by its original author to the GExperts project, so it has the same license as GExperts itself. The source code is part of the GExperts sources, but lives in a subdirectory of its own with few dependencies to any outside code.

I wasn't talking about Yukon. I can live with the formatter not supporting multi line strings, if (!) it turns out the change is too complicated. But these not supported language features add up over time and once they reach a certain threshold it simply doesn't make much sense use the GExperts. In an ideal world I or somebody else would start implementing support for new language features during the beta phase. But I'm not participating in the Beta and of some other Beta tester has made those adaptions, I don't know about it (he wouldn't be allowed to tell me). Btw. you could still use that feature, simply enclose those constructs in {(*} and {*)} so the formatter will leave that code alone.

It definitely does.

Yes, I know. But I also know that rewriting something from scratch takes a lot more time than one initially thinks. And may projects that start out as "This legacy code is cr*p, let's rewrite it" get cancelled due to time and budget overrun. Since my time is severely limited, I'm not going to rewrite that parser as long as it kind of works. And if it terminally breaks, I'm going to remove the code formatter for newer Delphi versions instead. There is a built in code formatter in the IDE after all, even though I don't really like it. Btw: I hope the built in code formatter was tested with multi line strings ...

That "multiline(...)' example was just the first thing that came into my mind. I just wanted to show something easier to recognize than these three quotes. Unfortunately the parser is quite complicated as it is now (I wouldn't have written it that way, but I also don't want to take the time to rewrite from scratch), so I wouldn't bet on the tweak being not too complicated. We'll see.

Not quite the implementation I would have liked though. Triple quotes '''? Who came up with that? Is that copyied from another programming language? I mean, Pascal is said to be very verbous, so why not somehing more explicit like: blub := multiline(' line1 line2, indented line3 '); People who don't like verbosity would complain of course, but these would complain about Pascal syntax anyway. (Goes away, silently weeping and anticipating yet another long night trying to adapt the GExperts Source Formatter to yet another string syntax ...)

As with any website: Print it. On paper, if you want to add notes. To pdf and send it to your ebook reader, if you prefer that.

The only sure way I know to prevent windows from updating is to disconnect it from the internet. That can be easily done with a virtual machine. Alternatively it's probably possible to only block it from accessing Microsoft servers. Of course there is the option to pause updates, but that only works for up to one month and has to be extended regulator after that. And it won't prevent an update to the next Windows 10 release when support runs out.

The easiest solution would probably be to assign different shortcut keys. No idea which part of the IDE now uses them.

Did Embarcadero buy SmartInspect? When? Last time I looked, it belonged to Code Partners Pty. Ltd.

Why not just use IFEND for all? {$LEGACYIFEND ON} switches XE4+ back to the old behaviour. (Didn't know that, it never mattered to me, as I always had to support some older Delphi version anyway.)

The only problem I remember is that early versions required {$ifend} rather than {$endif}. Apart from that checking the compilerversion should work for all versions after Delphi 6 (I cannot speak for Delphi 8 though, I skipped it).

That would make it harder to detect breaches of the NDA and start arguments about where the limits are. It's much easier to forbid any mention.

It was introduced with Delphi 6.