Leaderboard

??

I guess I finally found the cause: When you edit a property inside an interface the available visibility values are limited to default. Now edit a property in a class and the visibility is also default. The reason is that the current visibility is set before the allowed values are set. A fix will be available shortly. Can you check if you have Pick up any style comments as documentation checked in your MMX Documentation settings? That would take the commented method declaration as a comment belonging to the one below. Consequently the comment is moved together with the method declaration.

I find it a bit sad that none of these fixes get backported to earlier versions. They had something like this around 2016, but somehow stopped doing so. Or never really started, I don't know. I think this especially important when everything (editor, debugger, runtime, ...) is so tightly coupled together.

LOL. I knew some response was bound to come in from someone. Sorry, but that is pretty weak as every piece of software has bugs. If you mentioned, say, RSP-9678 Delphi IDE is not DPI aware (from 2014 with 93 votes) then it may have been stronger. Or maybe RSP-17724 Linux x64 compiler produce very bloated code. Or perhaps this thread: Again, that's not an overly strong argument. How many one liner changes have you had to chase for hours on end, that may have not have revealed themselves as a problem for months? The key point here is tests. So you can put bugs in your code, or hair on your burgers which you serve, but they aren't allowed? I believe the major issue here is lack of tests. The main way to gain more confidence in the Delphi platform is by trumpeting, marketing, glorifying their major gains in testing over the last few years (which assumedly has been the case.) Likely one of their most dominant product features is backwards compatibility - that very valuable feature can only be assured with a huge amount of manual effort, or a very large amount of tests. Likely one of their most harshest points of criticism lately is new code is not up to the quality of old code. That also can and should be braced with an adequate amount of tests. Finally, let's state the obvious here: Boian Mitov should not have changed his core library to inline variables until he was completely satisfied that it wouldn't cause problems for his customers. Changing your legacy source code in thousands of places to utilize a new feature of Delphi seems pretty reckless without adequate testing. Yes, we should be able to trust the compiler, but how about using Microsoft as an example... They have one of the largest R&D budgets in the world and they still ship very questionable software. If they came out with Visual Studio 2021 today, would you immediately migrate all your source code to it, after changing it in thousands of places to use one of the VS 2021's newest language features, and then quickly ship your product to all of your customers with a large amount of memory leaks? Would you be out there stating that Microsoft shouldn't be able to sleep at night, or would you be rolling back your changes and provide a stable product again to your customers? I certainly don't like providing an excuse for buggy code, or lack of tests. But this particular example is certainly not the hill to die on.

I used to work with Excel heavily, even with interactive, app-like documents, in the past. All that was very nice and efficient, but I still would say that I only touched 10% of Excels capabilities. Nowadays I still work with older Excel 2003, since this is the last mainly compatiblle Excel version, for all the features I loved to use. I try to move to LibreOffice instead, but only as spreadsheet and not with all VBA features, and all my interactive features are broken nowadays. Unfortunately either Excel, Office365 and LibreOffice were not able to give that light ease of use of the old Excel versions. And I'm talking about the ease of use for inserting lines, formats, printing formatting, etc. All that is gone now, or very much limited, where I see the old Excel still as perfect UI, which I even used as replacement for Word in some cases. I considered many times, to put my stuff into an Excel-replacement-app, but I think from the 10% I ever used, cut another 10%, so even that remaining 1% of the normal Excel would be a too tough project. Even is you use libraries from TMS or others, this is quite tough to re-implement the basic convenience features, and still a lot of manual coding is needed. I'm looking more towards solutions in HTML5, CSS, JavaScript right now, to make nice, interactive, print-friendly data presenstations, where HTML seems to be much more flexible than Delphi could every be. Always when I have to fill a PDF form, I think OMG, why on earth has Microsoft give away control over the spreadsheet market, which they once 100% ruled, so that this ugly peace of modern PDF could happen.

Just remembered capecod gunny (Michael Riley) who wrote some financial software in Delphi. Not sure whether it can apply here because it seem very specific to - in my view - typical American problems. https://www.zilchworks.com/zilch-standard.asp

I released quite a bit of interesting code to github over the years: YouTube DATA API v3 parsing: https://github.com/bLightZP/Delphi-YouTube-Channel-parsing-plugin-for-Zoom-Player Basic RSS feed parsing code: https://github.com/bLightZP/Delphi-RSS-feed-parsing-plugin-for-Zoom-Player TheAudioDB MetaData/Image scraping code: https://github.com/bLightZP/Delphi-theaudiodb.com-Zoom-Player-media-scraping-plug-in TheMovieDB MetaData/Image scraping code: https://github.com/bLightZP/Delphi-themoviedb.org-Zoom-Player-media-scraping-plug-in OpenSubtitles.org subtitle search & scrape code: https://github.com/bLightZP/Delphi-OpenSubtitles.org-API-support-for-Zoom-Player A basic cross-platform calculator https://github.com/bLightZP/ElegantCalculator https://play.google.com/store/apps/details?id=com.inmatrix.ElegantCalculator Adapted old code to work as cross-platform pure-pascal image scaling with filters (bicubic, bilinear, etc): https://github.com/bLightZP/ImageInterpolation Adapted old code to work as a cross-platform drawing of an anti-aliased circle (can be modified to draw rount-rect as well): https://github.com/bLightZP/AntiAliasedCircle I forked a QRCode generating source code and greatly optimized it (~ x50 faster): https://github.com/bLightZP/DelphiZXingQRCode The original Delphi scanline color-conversion implementation was very slow, so I optimized it: https://github.com/bLightZP/OptimizedDelphiFMXScanline