Der schöne Günther

Works for me. Have you tried ticking on the boxes, and then unticking it? Or logging out/in again?

I don't know how to reproduce. This here runs fine: program Project1; {$APPTYPE CONSOLE} uses System.JSON; const the_resp = '{"msg": "you get ... 100 % satisfaction"}'; the_resp2 = '{"msg": "you get \"... 100 % satisfaction\""}'; DEF_INDENT = 2; var doc: TJSONObject; formatted: String; begin doc := TJsonObject.ParseJSONValue(the_resp) as TJSONObject; formatted := doc.Format(DEF_INDENT); WriteLn(formatted); doc := TJsonObject.ParseJSONValue(the_resp2) as TJSONObject; formatted := doc.Format(DEF_INDENT); WriteLn(formatted); end.

I remember it did work by using DocumentationInsight XML comments, you had something like <remarks> See the <see cref="App.Fizz.Buzz.pas|TFizzBuzz.init">init() method of TFizzBuzz</see> for more info </remarks> where you could then click on init() method of TFizzBuzz and the IDE would take you directly there. If I recall correctly, that was removed in either XE5 or XE7 and Documentation Insight has to be purchased separately. These days, the IDE still offers you to click on it, but clicking will do nothing except freeze the IDE for a few seconds 😪 A possible workaround is to specify the absolute path (including Unit & class name) so to make the references work. Of course, they stop working if you rename either unit or class: 2021-07-09-08-49-29.mp4

Not saying that this site is not reliable, but I would always refrain from 3rd party magazines in that case. The official CPU support list from Microsoft can be found at http://aka.ms/CPUlist

Stupid question: Is it running inside a VM or directly on real hardware? When I installed it inside a Hyper-V machine, it lacked 3D acceleration and a lot of effects (transparency, animations, rounded corners) were missing.

I can only speak from very positive experience, and the fact that I'm doing HMI software that runs 24/7, for months. So leaks (of all kind) are a big concern to me. For sure you can have memory, handle or GDI leaks in, for example, 3rd party GUI libraries from DLLs. But on the other side, that ReportMemoryLeaksOnShutdown also just registers things at ... shutdown. It's not going to help you either when you pile dead and unused objects on top of each other, just to tediously free them when the application ends.

I'm used to closing the debugging session with [Ctrl]+[F2] 😎 Memory leaks are taken care of in unit tests, DUnit can let a test fail when there's a memory leak.

I had the same use case a few months ago, and I was glad to find out that you can at least easily select, copy & paste the compiler output as text lines. Writing yourself a tool that filters the output (for example, by unit or severity) should be trivial. The extra step to select, copy & paste might be annoying, but better than nothing.

I remember taking a look at horse, but dropped the idea of using it because - back then - it looked like a lot of stuff bundled into one giant repo, i think it even had another library as a dependency. It seems they have changed that: At first sight, everything looks much more structured and clean up. I think I will take a look at it again.

You seem to be using FireDAC to access a Microsoft Access file. I don't understand the language you have on screen, but entering the terms "ace dsn jet" from your error message into an internet search engine reveals that the computer you're trying to run it on does not seem to have the necessary ODBC drivers for accessing the database file. Does installing the following help? Download Microsoft Access Database Engine 2016 Redistributable from Official Microsoft Download Center PS: The Windows "Sandbox" is a great feature to test if your program runs on other machines that do not have additional software installed (requires Windows Professional, I think).

Yes, it does. But it indicates it also works the other way around, but it doesn't. I think I'll file a bug report. -- https://quality.embarcadero.com/browse/RSP-34216

FireDAC sources do come with RAD Studio, what am I missing? 🤔 However, yes, the RAD Studio documentation in general is a pretty sad sight.

In the meantime, I have found out that the file needs to be saved to disk for auto-implementation to work. I was not aware of that. 🤦‍♂️ It's the first time I'm using Omni Pascal beyond for actual compiling/running unit tests. So far, I had only used it as a simple editor to write code, then copied it back into Delphi.

Of course, but I really wonder what this property is intended for. So far, it seems you cannot use it to achieve what it advertises and is therefore broken.

Perhaps I should, yes. But I am not sure if @Wosi is still maintaining OmniPascal and I don't knonw yet if I overlooked something or if it's a bug.