Leaderboard

I'm quite sure that the people at TIOBE are driven night and day by their intense feelings of envy towards Delphi. I really can't imagine they think about anything else.

So you don't format your source code with line breaks? - Because the Delphi compiler will ignore them anyway. It's not something I often do, but once in a blue moon I need to have a largish block of text in the source and that's just the way it is. Let's assume that there are reasons for this and that I know what I'm doing.

I can't tell if this was an attempt at humor because that's exactly the syntax I want to avoid.

Sounds like a bug to me. Have you checked the application for resource leaks?

They appear to be auto released which his why releasing again manually causes the crash.

I immediately understood the new syntax at first glance. The syntax you proposed looked like broken code. Honestly I doubt there is any possible solution to this that would not cause someone to complain, but I am glad they didn't decide to override the function call syntax for this. Personally I am glad we are finally able to move beyond the 255 character limit and have a viable option for pasting in multiline content to be used as a string literal.

Could you not just have an option to leave things the way they are, and still support Yukon? For people like me, long time users of GExperts formatter, who find it an absolutely essential tool and who will have no problem in resolving never to use a triple quote for its new purpose.

A multiline string is multiline - simple as that.

August 2023. Delphi was about to enter Tiobe Top 10. But exactly before that, Delphi was thrown down to position 30 (or something like this) for a few days. Now I see it is back to the top 20. But instead of pos 11 it is 15 now. People from Tiobe must really really hate Delphi.

The project now has been moved to Sourceforge: Delphi Cross-Platform Application Help download | SourceForge.net

The Delay option was added in 10.4 Sydney, so it is a relatively recent addition (2020).

For the same reason they have ridiculous NDAs and don't have public betas; They are so stuck in the 90s that they think anyone still gives a damn.n They never understood how to build a community.

Please stop using VERxxx. It's been possible to do {$if CompilerVersion >= XX} since Delphi 6 or 7. It's so annoying having to edit the .inc files of various 3rd party libraries with each new version of Delphi because they're designed as if the latest version = the last version. Graphics.32 uses {$LIBSUFFIX AUTO} for the D11+ packages. The earlier packages are manually maintained by using a diff tool to keep them synchronized with a master. The master usually comes from the latest supported Delphi version. There's no way I'm wasting disk space on old versions of Delphi just to maintain the package files. I have the latest version, and the few versions required by my job, and that's it.

This package madness really bothers. Especially knowing most versions doesn't differ at all.

Although the real problem is the language design that makes this order affect the meaning of the program.

You don't wait. As I said, put the code to be executed after JavaScript finished execution in a function and call that function from the callback. A call back function in Delphi terminology is an event handler.. Your app doesn't wait that the user press the "play" button. You get an event when the button is pressed and from there, you start the task you have to do, that is execute JavaScript. Then, you don't wait for the JavaScript execution, you just return. The code to be executed (A position bar on the timeline) once JavaScript is done is called from the WebView2 callback (That is an event). From the "play" button click event, you disable the button and you re-enable it once you get the JavaScript done.

You should think "event driven" and no "synchronous". Put all your code after the ExecuteScript call into another function. Then call that function from the callback. Probably your application will need other changes to become fully event driven without using any "wait loop" hack.

There are some odd entries in the resources of BDS.EXE and BDS.fr: And some other executables do not have proper version info: So they do not display anything when read the usual way (like e.g. in the Properties dialog in Windows). Older Delphi versions still refer to Appmethod in the translations (this is XE8): (I definitely had too much time on my hands today. 😉