Lars Fosdal

IMO, minimizing or avoiding Synchronize is preferable.

But isn't everything moving towards 64-bit?

There are numerous Unicode white space chars of varying width, so adjusting the distance "by character" is possible.

@David Heffernan - At this point in time, would it make sense to ask EMBT to focus primarily on the 64-bit part of this?

Use a worker thread which stays active and take tasks through a queue.

Off-topic for this thread, isn't it?

Well, what do you know! I actually didn't know you could wordwrap a checkbox caption! Thanks, @Attila Kovacs!

Having these discussions on desired language features bear little effect unless a properly thought through and well written proposal is submitted through QP, and even then it is just a pipe dream until it gathers a large number of votes, and/or someone within EMBT agrees that it is a good idea. Keep the ideas coming, and do discuss them - but unless they are formally submitted, we are just having a chat by the watercooler, if you see the analogy?

COM objects will work in a sub-thread if they are created after calling WinAPI.ActiveX.CoInitialize(nil) and destroyed before calling WinAPI.ActiveX.CoUnintialize, in that thread.

@David Heffernan - I took the liberty of splitting this off into a new thread. I think @Marco Cantu and @David Millington should look closer at this.

What happened to that document? https://web.archive.org/web/20171221023547/http://qc.embarcadero.com/wc/qcmain.aspx?d=107411 Edit: I took the liberty of splitting David's answer into a new thread.

Different part - as in Outside the sand box - but it seems the file system is fully virtualized. A bit odd that you cannot specify %APPDATA% in the deployment system, since that actually is the appropriate path. Write under AppData Windows 10, version 1903 and later: New files and folders created under the following directories are redirected to a per-user, per-package private location: Local Local\Microsoft Roaming Roaming\Microsoft Roaming\Microsoft\Windows\Start Menu\Programs In response to a file open command, the OS will open the file from the per-user, per-package location first. If this location doesn't exist, the OS will attempt to open the file from the real AppData location. If the file is opened from the real AppData location, no virtualization for that file occurs. File deletes under AppData are allowed if user has permissions. Windows 10, version 1809 and earlier: Copy-on-written to a per-user, per-app location. AppData is typically C:\Users\user_name\AppData.

On the other hand, APPX apps are supposed to be sandboxed - hence moving a file to a different part of the system might not be a good idea? I could be wrong about this, though.

Which looks like a shared folder - unless that part on the end is a user specific key. If you install it with a different user - is a new folder C:\Program Files\WindowsApps\MYAPPNAME_1.0.0.0_x86__?????? created, or is the same folder used? Looking at http://docwiki.embarcadero.com/RADStudio/Sydney/en/Deployment_Manager, all the examples simply uses .\ - so perhaps that is sufficient.

If you name it .\YourAppFolder\ Where is that folder created in the current user's file system?