dummzeuch

Such a mechanism already exists: Everything between {(*} and {*)} does not get formatted.

One option would be to use a pre-build-script to set a compiler define depending on some external criteria. This could work via an include file that gets modified or maybe by changing the dproj file (not sure this is possible). Of course this only works for a given project.

I know of no such option. GExperts reads the version info of several files to get this info at runtime.

My blog post is not meant as a general security advice for WordPress. I'm not qualified to give that. It just highlights one particular problem which apparently many overlook. As for authentication: It is only as secure as the transport protocol, so if the installation uses plain http its not much. It does prevent automated data harvesting by simple bots though.

Guess what? The new GExperts release is here. There are lots of bug fixes and a few new features in the new version. https://blog.dummzeuch.de/2020/10/23/gexperts-1-3-17-experimental-twm-2020-10-23-released/

I thought I already had?! No, because that's a combobox, which means it automatically looks up from it's list. You can drop a directory on it though.

I'm also using ComPort from SourceForge. Never tried AsyncPro though.

I hope they were getting paid for that work.

Mine is longer than yours: XDOM_3_1: 27134 lines That's one of the files I use to test the GExperts code formatter with. One advantage of having only one huge unit is that everything is in one place. You simply add that unit to your project and that's it. No need to add any entries to the search path etc. But that's not my preferred coding style. But I am sure that somebody somewhere has already hit the maximum file size of the IDE or the compiler (if there is one apart from the obvious 4 GB limit of a 32 bit program, I don't know). I have definitely read of somebody who has hit the maximum number of lines in a method.

Yes, it is the culprit. And unfortunately I see no way to solve this.

If you are using relative paths and of course an SCM, you start out by creating a copy of the original project in SCM, check out that copy to a new directory and then simply do all the changes necessary: Rename the project, delete any files you don't need, optionally rename the files etc.

You are kind of right, but that was a totally different kind of inline:

GExperts also has an option to "Automatically close (the) message window after a successful compile". It's on the IDE tab of the configuration. Not quite a keyboard shortcut but maybe even better?

Yes, it's possible, but it needs to be done properly, for which I don't want to spend the time. In particular because I myself don't use the theming. If anybody else wants to put in the effort, I'll be accepting patches. By "properly" I mean that not only the standard controls must support theming - which kind of works, even though it's a bit clunky -, but also the owner drawn controls must match it. And of course that must be done without breaking compatibility with older versions of Delphi.

Is it possible to have UnitAlias empty? When I try that, it automatically gets reset with the ancient aliases for WinTypes etc. But I haven't tried that with recent IDEs.

Having a unit called "utils" in the GetIt package is not really a bright idea by Embarcadero. At least they could have prefixed it as getit.utils.

From what I can glance of the error message, there seems to be a problem with compiling the GXIcons.rc file.

You will never leave that phase, just the number of mistakes will shrink over time. At least that's how it has been with me. But on the bright side: Making mistakes - and recognising them - is a great way of learning.

Not sure about that. I have seen that kind of formatting with the additional indentation for the second and later field very often. Personally I prefer explicitly giving the type for each field: type TSomeRecord = record a: integer; b: integer; { bla } c: integer; d: integer; end; even if that means a bit more typing.

Famous last woAccess Violation at address $00000000 ...

Simple: I rarely make any calls at all. For those calls I still need to make, I prefer a SIP connection and a headset on my computer. My mobile phone contract even comes with an option to connect via SIP, but that is a remainder from old days, new contracts from that company do no longer offer this. And also, calls via SIP are not covered by the phone flat rate. So I have a different one paid for by my employer due to me working from home nowadays. I also have a land line, but that's for internet connection only, no phone was ever connected to it.

GExperts has no external dependencies (and as far as I know never had). It's just a matter of checking out the sources from svn and start the correct compile batch. All additional libraries (Synedit, Abbrevia and some more) are included in the repository. And since GExperts is a DLL (not a package) wizard, there is no conflict with other versions of theses libraries that may be installed.

I'm thinking about not bothering any more. Maybe have a generic installer for the additional files and registry entries required and letting the user compile his own DLL.. On the other hand there seem to be many Delphi developers who are adverse to compiling it on their own.

Some of this new fangled stuff is just not worth the effort. Now get off my lawn! 😉 OK, I'm getting old. More and more grey hair and receding hairline are obvious telltales. (My grandma was using the German expression "neumoderner Kram". Back then (in the 1960s) she was talking about the telephone with a dial. Having a private phone line was still something special in many areas of Germany in that time (so I heard). She never really learned the customary protocol for using it, that is, stating her name when calling. That was back then when phones didn't even display the caller's number, so you didn't know who was calling. Some kids nowadays are the same, they never learned it, because "nobody uses a phone for calls any more". And they are basically right: I rarely use my smart phone to make calls.)

No, didn't try yet. And with @Achim Kalwa's plugin, available (which I haven't tried yet either), I'm not sure I'll bother.