Der schöne Günther

That's just a form with buttons on it, and occasionally half-transparent. That's really not rocket-science.

Excessively writing unit tests for new parts, but not using code coverage tools for the whole project. More than 50% of our code is 10-20 years old and simply cannot be tested. Yes, I have read Working Effectively with Legacy Code by Michael C. Feathers (goodreads.com), how to get out of this. But ain't nobody got time for that.

I'm not very good with words, but I honestly can't find that he claims VS is terrible. "He says Visual Studio is terrible" is a really delusive distortion of words. 👎 RAD Studio definitively has its issues (for example, I'd never call it responsive, as he does), but so does VS. I don't particularly enjoy working in VS either, it's far from perfect. But I do love Visual Studio Code, that's for sure.

Also known as Elvis operator - Wikipedia 😉

I have been shipping one of our Delphi applications with the WebView2 runtime for months now. It really does work fine. The easiest mistakes are Forgetting to ship the needed dll Forgetting to install (or ship) the runtime or needed beta browser version Putting the application in a write-protected folder without telling the runtime where it can write What exactly is your problem?

Saving to file has nothing to do with the string itself. What's next, myString.SendOverNetworkByUDP(..)? You have TFile.WriteAllText(filePath, fileContent) from System.IoUtils, that should be enough for everybody 😉

It makes no difference whether Delphi is installed on a virtual or real machine. One installation takes one activation. If you run out of activations, you have to contact Embarcadero and ask for a "bump". I don't use Delphi on real machines anymore, only virtual machines.

You can achieve this by ctrl+clicking, or middle-clicking, or whatever you usually do to "Open In New Tab" on the headings, when in fluid view. It should not be possible.

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

So I have something very simple: A TFDConnection, a TFDTable, TDataSource and TDBGrid. Both connection and table have a property ConnectedStoredUsage: As far as I understand, I should be able to Set both connection/table to "active"/"connected" And remove the auDesignTime flag from the ConnectedStoredUsage property so that the form designer will not connect to the database, but the running application will. The problem is: Because both connection and table are not active on the form designer, their properties Connected = True and Active = True will not get saved into the DFM file! Modifying the DFM file with notepad, adding "connected = true" and "active = true" yields exactly the result I'd expect: It will not connect on the form designer, but the running application will connect. As soon as I the form is modified within the IDE, it will once again remove the Connected = True and Active = True from the connection and table. What am I missing? I'm sure this is not working as intended.

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

OmniPascal appears to be having auto-completion since 2015: However, this option does not exist for me - There is no quick fix available: Any idea what I might be missing? Code completion is working fine, by the way. Update: Turns out the file must be saved to disk first, then it's working.

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.