Der schöne Günther

There is an (outdated) copy of Spring4D on Github, just for Delphinius: https://github.com/Spring4D/Spring4D I also asked myself that. Not going to complain - Just double-clicky and you're done. But I also wondered if there was another reason beside comfort.

But wouldn't that require the "CallerThread" to support something like this? As far as I know, only the Delphi main thread has something like this, queueing/synchronizing something to a regular TThread has absolutely no effect.

Only who supplies the callback (your TForm1) knows if it's important to have it synced to the main thread or not. So it should take care of synchronizing/queueing it to the main thread, not your TCompressor.

Wasn't ModelMakerTools for Delphi able to do that?

I find it difficult to keep track of all the different products and technologies. VirtualBox is easy, I got that. Hyper-V appears to be more or less the same, it's a virtual computer running on some host (like my local machine). Then, there is the new Windows Sandbox. And there is "Application Guard" which allows some applications (like a browser) to run in a shielded environment, but display regular windows on my desktop. And then there is "App-V", which has been around since Windows 7, I think. Are they related?

A TWinControl has a method RecreateWnd(): http://docwiki.embarcadero.com/Libraries/en/Vcl.Controls.TWinControl.RecreateWnd Maybe you can have a look at the VCL sources where this gets called...

Wouldn't that be the easiest? I don't see much of a "problem" of how to know when everything is ready. By default, it should be after the first time OnShow (or maybe even OnActivate) has been called. This can be done in your base class. If you need more elaborate logic in one form class, then you can override that behaviour.

Thanks, I will try that. I didn't notice the file was supposed to be locked, I think it could still be moved around in explorer while compression was taking place but I might be wrong.

Sorry, I didn't know. That really paints a different picture of the whole situation.

No Embarcadero "This repo is a copy of our GetIt stuff"-type of thing, I meant the repo of the thing I wanted to use. Clone it, store it offline, never worry again. GetIt is great for quickly trying things out. If you rely on a component, get it from somewhere you can rely on (your own disk).

A year back or so, GetIt stopped working for 10 Seattle. I opened a support ticket with Embarcadero. I'm glad they were honest and told me they weren't going to fix it and I should download stuff from Github instead. That really showed it's nice for quickly trying something out, but no one knows when it will stop working.

But doesn't that defeat the purpose of using a thread in the first place if there can only be one canvas operation at a time?

Querying a random internet search engine with "Delphi TBitmap Thread", it appears to me as TCanvas is not meant to be used in threads. There are countless threads on this subject.

With proper source control you would have seen this immediately 🙃

I was talking about a "version control" system that helps you keeping track of what files were changed, when, and why. Notable examples include Git, Mercurial or the good old Subversion.