FPiette

@PolywickStudio Backup is done, you can access the website again.

Please be patient. Sunday morning is backup time. Retry in 15 minutes.

Create a simple, reproducible example demonstrating the issue and publish it on https://quality.embarcadero.com because here, there is no chance to have it fixed if ever it is a bug.

Probably the debugger can't call a getter/setter function.

That is why I always STRONGLY recommend to buy the source code with any third party library/component you use and to ONLY use the source code and not a single pre-built item. Rebuild what you need for your application, add a project for that purpose to your application project group. When a new Delphi release comes, most of the time a simple recompile is enough. This include the component package projects. The most common change to the source code is to add a simple conditional compilation related to compiler or runtime version. When you have full source code, you don't depend on component vendor when a new Delphi is released.

We probably do not write the same kind of code, because it never took much time to me to move a project, even a big one, to the next Delphi version. The only case when it took significant time was when Unicode was introduced. Most of the time, it was just a matter of recompile. I must say that I always manage to have FULL source code for every component I use and have that source code included in all projects making use of the component. When a new Delphi release comes, most of the time a simple recompile is enough. This include the component package projects. The most common change to the source code is to add a simple conditional compilation related to compiler or runtime version. When you have full source code, you don't depend on component vendor when a new Delphi is released.

That is definitely NOT my experience. You have something wrong on your system. Maybe you loaded a bunch of extensions. I only use MMX Code Explorer. If you have the problem you mention, please create a reproducible, minimalist example of code and give detailed instructions to reproduce the issue. Publish it here but for sure on quality.embarcadero.com. Anything else if blablabla.

Is 10.0 the first Delphi version that you use ? The risk you are exposed to is that if you don't update your code with each new release, the more difficult it will be. Between two consecutive releases, porting is quite easy. If you skip many releases, it will become more and more complex. Not only for Delphi itself, but also for 3rd party components you use.

I moving all my project to Delphi 11. Up to now, I've nearly ONE MILLION lines moved without a single problem. I don't use high DPI. With D10.4, I had to restart IDE from time to time. With D11, it runs continuously, I don't even stop it when my day is done.

Maybe create a new message thread with a clear question?

One possibility I see is to open a modal form just after the call to ExecuteScript and have that form closed by the callback. The modal form could be empty or even so small that the user won't notice it or it can be a place for a progress bar, a cancel button or just a "please wait" message.

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.

Evaluating old versions is useless. Before deciding, do your evaluation with Delphi 11 trial (Free for 30 days. Trial <> community edition).

That is exactly what I said before in this conversation. You have an OLD Windows version. Current Win10 version is 21H1. This is a real new version, not a simple update. Look at Microsoft release information.

I suspect the OP (David Schwartz) has a very old Win10 that was doing many unwanted things by that time.

Please tell us what you found. Virus scan, defragmenter,... Look at task scheduler there are a huge number of tasks.

That's a good and a bad news 🙂 If you application grab a file from iCLS Client, then it is likely a system path issue. Remove the directory from the path and restore the file so that iCLS Client will work again (If you don't use that product, you could - probably - uninstall it as well). Now that you get the correct DLL from your application directory, you can start again all tests and checks Angus suggested to understand what is wrong with it. But before trying with your own application, try with one of the ICS samples that we are sure the code is correct.

Use ProcessExplorer to see exactly which (full path) DLL your application has loaded. Then given which one it is, find the reason why that one is picked by the system. You could also remove that old version (Keep it in a safe place in case one of your applications depends on it).

Do you mean that for a given application on a give computer, sometimes some buttons and checkboxes (but not all) are missing? Or do you mean that for some application it works and for other it doesn't - always? Is it VCL or FMX application? When you create a simple program, does it happens ?

You application is probably blocked by Windows firewall which blocks by application. Look into the firewall rules (Advanced settings).

Try ICS (Freeware) : http://wiki.overbyte.eu/wiki/index.php/Main_Page or using GetIT from Delphi IDE. If you need help with ICS, don't post here but in the a dedicated forum: https://en.delphipraxis.net/forum/37-ics-internet-component-suite/

You should buy only components delivered with full source code. And more: you should rebuild the components as part of your application project group to be sure you have all the bits and pieces of the components. Never use prebuild dcu nor dll! Then as @Uwe Raabe said above, you'll will probably never be annoyed to much with new Delphi compiler. Most of the time only minor adjustments are required and vendor is not needed. If you really need the vendor and you are an experienced Delphi developer then stop using those components. They are not well written or the vendor want to lock you with his product and force you to buy an upgrade.

Not many work hours into that price. Why don't you use Delphi community edition to build the DLL yourself? Later you can ask someone with a valid license recompile it for you.

Is the app VCL or FMX ? Which component set are you using ? You don't show much but it doesn't look standard Delphi components. Do the users have a HiDPI monitor ? What is your and their zoom factor for text size (In Windows display settings).