dummzeuch

No, it doesn't.

When I see formatting like this (generated by the Delphi formatter, if "Keep user line breaks" is turned on): type TSomeRecord = record a, b, { bla } c, d: integer; end; I wonder whether the Delphi formatter is based on DelForExp like GExperts'. But in the latter this bug has been fixed: type TSomeRecord = record a, b, { bla } c, d: integer; end; On the other hand, this is an interesting formatting: type TSomeRecord = record a, b, // bla c, d: integer; end; This was generated by the Delphi formatter from this input, with the default setting "Keep user line breaks" turned off: type TSomeRecord = record a, b, // bla c, d: integer; end; It would never have occurred to me.

I'm not surprised that cnWizards is using the same character sequence. But that probably did not come from GExperts but from DelForEx which was the base of the GExperts code formatter.

Thanks a lot for volunteering. Ijust made a release, the code to be tested is included in that. So in order to test it, simply install the release, enable the "Filter Exceptions" expert and debug code that raises exceptions. If the fix worked, you will get the new filter dialog for non-Windows projects. If it didn't, strange things (most likely AVs in the IDE) will happen. In the latter case, disable the "Filter Exceptions" expert and try again. The normal IDE dialog should appear and no AVs or other strange things should happen.

The simplest way is a patch file, as @Fr0sT.Brutal already suggested. Another option is to simply send me the changed sources (I prefer patches). And if you want to be involved deeper, I could give you write access to the repository. But a good start would be to submit a bug report (or feature request) on SourceForge providing input and desired output examples as attachments. I could then easily add those to the unit tests which would increase the likelihood to get them fixed.

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 ...