timfrost

And I would be grateful for this fix also

It is very many years since I wrote anything in COBOL and I could not remember any of it, except the feeling of 'writing all those words'. And after googling for some sample source code the memory turned out to be correct. How did we do it? And what about getting the cards punched with the program before we could test anything.

I still like a Ternary Search Tree, which I have been using for at least 20 years. Fast to load, faster to search. My implementation uses string keys, and NativeInt, Object or String values. I posted about this in a similar thread here; let me know if you want a copy to try. https://en.delphipraxis.net/topic/4635-fast-lookup-tables-tarraybinarysearch-vs-dictionary-vs-binary-search/?do=findComment&comment=40466

I don't have an answer to your question, but I have one elderly program which still uses a component called CoolTrayIcon. I still use the version I downloaded in 2006, and it still works faultlessly in Delphi 11 and in Windows 11, though it looks as if I have hardcoded a $define for Delphi_6_UP and changed the BPL/DCP numbers to match the compiler. The same author, Troels Jakobsen, still publishes it on Github. I recall it was easy to work with, and you may just find that using it solves your problem.

Thanks, that was it. I had tried to recall anything new I had installed, but had forgotten a Snagit upgrade last weekend, and also that this probably caught me two years ago when I last upgraded. Getting too old!

Something seems to have stolen Shift-F9 in my 11.3 IDE. It's extremely annoying because I have a keyboard with function keys on the left, so it is a left-hand-only action which has become automatic. Does anyone have any ideas about who might be the culprit? I am aware of tools which claim to display the owner of all shortcuts, but they seem over-complex as well as limited to certain types of shortcut only, so the learning effort might be wasted. Alternatively does anyone know of an IDE plugin which can change the setting? Both my F9 and Shift keys (and I have two of each to choose from on this keyboard) appear normal in a test FormKeyDown event, and F9 on its own works as expected in the IDE.

In England, at least, I understand the word as "holding to one's own opinions and ideas too strongly"; "obstinate"; "unwilling to be corrected"; "inflexible". In other words, not the most desirable qualities I need in a tool which will be adjusting and improving whatever I have carefully written. But I accept that this may just be an accident of translation which is not intended for this context.

SysInternals Process Monitor may be more useful than Process Explorer, to get a log of every file and registry access in the system. Filter the log for your process only, to avoid being overwhelmed.

I am still using parts of Clever Components but for a simple HTTP Client I have long used the Delphi WinInet component and did not bother to change this when I started with Clever about ten years ago for some other protocols. Both WinInet HTTP Client, and the Clever protocols I use, work fine on Windows 11 for me.

Does Sysinternals PROCMON reveal what the IDE is waiting for or trying to do?

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.