timfrost

I have used a Clever Components support ticket (I have never had any other way to contact them) to send Sergey a link to this thread and ask him to comment.

Clever Components is one of our software-library suppliers who used MyCommerce to process payments. We last paid for annual support/updates renewal in March this year, which may have just squeezed through to Clever before Digital River went quiet; or may not. Reading how other vendors have been affected makes me wonder if Clever have been starved of funding also.

When I try to run the pre-built executable linked from Github, on Windows 11, I get either a runtime error 217 or a crashdump, depending on the current directory of the exe.

I would try Process Monitor from SysInternals, filter on the bds.exe process name, and check what it's 'last words' were before dying. It may give you a clue.

I cannot believe how complex this discussion has become! All to avoid having a tiny unit with four boolean variables defined in the interface, along with a GetLogLevel function which can be called when needed, and then writing, for example: if LOGINFO then log(MyComplexStringExpression); if LOGALL then Log(AnotherExpression); This seems to meet all the criteria of readability, simplicity and efficiency.

I have used bits of their Internet Suite for over a decade. Looking back over the few tickets I have opened, the response time has varied between two and ten days. Not much more than it used to be when Sergei just responded to e-mails. I agree the help file is a bit primitive but they also have a large library of examples and tutorials for the Internet Suite on their site and on Github. I know nothing about their other products, but the ones I use are pretty solid. For this reason, and the fact that I have the source code, I have never really worried about where their offices are, or how many people are in the 'Clever Components Team' which appears under Sergei's e-mail signature.

Bravo! And please do not abandon a simple source download, for people like me who dislike having to struggle to work around an unnecessary version-control system to get what I need.

The ability to exclude areas from formatting is one of the many reasons why I have always used: {(*} GExperts Code Formatter {*)}

It's an IDE feature. Add or delete a file to the project, and conditions and includes in the units list in the DPR are changed in various ways. I opened a quality ticket a couple of years ago and was told it was by design, because 'Delphi manages the DPR file' and can override manual settings.

SysInternals Process Explorer can show the path and version resource of each loaded DLL in a process.

Sounds good, but raises some questions: Is this an alternative to ewriter files or an eventual replacement? Can you summarise the advantages/disadvantages of one over the other? How much change is needed in Delphi VCL applications, or in my help build procedures, to switch to using Ziphelp? And does a download of Ziphelp attract the usual Windows 'block' on zip files?

A delight to use, and very helpful to see project relationships. I also like your encouragement of exploration without needing documentation - I found that clicking on things was more than sufficient to reveal more secrets.

Could you not just have an option to leave things the way they are, and still support Yukon? For people like me, long time users of GExperts formatter, who find it an absolutely essential tool and who will have no problem in resolving never to use a triple quote for its new purpose.

In my experience the bugs in the project settings hierarchy have varied from version to version, but never gone away entirely.

I personally would use Mitec System Information Component Suite, because I already use it for many of its dozens of other information sets. It is probably overkill if you only need this one enumeration, but it's excellent value if you also need more. https://www.mitec.cz/msics.html