Leaderboard

When I initially installed Delphi 11.0, I went through GetIt and installed several items, including the Parnassus Bookmark and Threaded Debugging plugins. For the next couple of months, the Delphi IDE was more unstable than any previous version. It was bad enough that I emailed my account rep and she arranged an online call. The short version is that once I uninstalled both Parnassus plugins, exceptions stopped occurring in the IDE. I occasionally see one today, but that is typically after having an instance of the IDE open for several hours using the debugger heavily.

No need to buy a book. Google for "principles of modern ui ux design" and there is a bunch of info. Additionally there are how-tos and guidelines from both Microsoft and Apple publically available.

UI design is not bound to the component set you are using or even the programming language. You should follow the OS guidelines.

That's what the word "amnesty" is supposed to mean in this instance - a waving of penalties. I'm very surprised to discover it was just another sale. They're out and out telling you something that's not so to get you to call up a sales representative. A former 20-year employee of Borland/Embarcadero's Delphi support once shared that they start having these sales whenever the sales team isn't making its target sales numbers for the quarter. It seems like that's a constant state now.

Probably this one as it's the only one (I know of) that is focused on FireMonkey: Delphi GUI Programming with FireMonkey.

I have a lot of plugins installed in my IDE, many of my own + other like GExperts and MMX. I found my IDE became more stable after disabling all the Parnassus plugins. Haven't had the time to spend a day tracking down the issues to report a bug.

We're excited to release version 1.1.0 of DelphiLint, a free and open-source static analyzer and linter for the Delphi IDE! DelphiLint is powered by SonarDelphi, our Delphi analyzer for the SonarQube code quality platform, and can be run in two modes: Standalone - run analyses entirely locally, no server required Connected - connect to a SonarQube server, allowing for synchronization with the server's quality profiles and configuration Release: https://github.com/integrated-application-development/delphilint/releases/latest Blog Post: https://github.com/integrated-application-development/delphilint/discussions/43 New Features in 1.1.0 Quick fixes - fix issues using suggested automatic changes Standalone rule configuration - configure the analysis rules that are applied in Standalone Mode Declutter files by hiding issues Many performance improvements and bug fixes For more details, see the blog post for release 1.1.0 and the repository README.

In my opinion all is said. @PeterPanettone Just submit a feature request. It has nothing to do with "lacking abilities" of the developers but priorities for development

It seems beyond your ability to not be obnoxious. I don't see a point in continuing to converse who you.

Oh My! Found it. I really do need to get my eyes rechecked. It wasn't DBWIni.ini, it was DBiWIni.ini. All good now. Thank you for your inputs and apologies for any inconvenience. Ian

Also until developers did not start to use multiple languages.

Since Delphi is kind of a legacy programming language nowadays, backwards compatibility is very important. You don't want to throw away millions lines of proven code because they don't work any more, or even worse, because they are now buggy. So trying to change strings to be zero based was a bad idea, even if it was "just for mobile platforms".

This is an interesting example. Off-by-one errors are extremely common, especially when you first start programming. Over time, you learn to prevent them. Considering Delphi: Given this declaration: var ary[10] : char; str[10] : string; One might be tempted to write: for var i := 0 to 10 do ary[ i ] := ''; and similarly for var i := 0 to 10 do str[ i ] := ''; The first loop would blow up when i = 10, and the second would blow up when i = 0. And the compiler would fail to flag either as a possible problem. A smarter programmer might write: for var i := Min(ary) to Max(ary) do ary[ i ] := ''; for var i := Min(str) to Max(str) do str[ i ] := ''; But the safest way is to use this syntax (when it makes sense): for var ch in ary do xyz(ch); for var ch in str do xyz(ch); There are other variations that can attract off-by-one errors (while ... do, repeat ... until, etc.) that the compiler is helpless to do anything about. What's needed is a syntactical way to totally AVOID such off-by-one errors in the first place. Well, the for ... in syntax is the safest, but it's not valid in some use cases -- like if you want to initialize the contents of the array, because it yields a value, not an index. Some languages have the ability to let you say "foreach ..." or "for ... each ...", but that's still a decade away from showing up in Delphi, if it ever will. So we're left to use far less efficient libraries to provide these common-sense solutions, or just go bare-knuckle and let the cards fall where they may. There are plenty of ways to make the language "safer" in many such respects, but if nobody is willing to actually make the compiler changes needed then it's a wasted discussion.

It all seems a bit tricky. I generate a blank form Delphi app and 22/72 on VirusTotal identify the file as malicious. Oddly enough, one of the ones in VirusTotal that clear it is Microsoft Defender. But, on my laptop, it was Microsoft Defender that called virus. All Delphi developers could face a similar problem. I can't give a program to a customer and say it's just a false positive. Especially if 22/72 other virus checkers call it a virus. In searching online. I'm surprised to not find Embarcadero all over this.