David Heffernan

Just upload the image to some file sharing site. And show your code to process the EXIF.

Turn this into an opportunity!

What about work with a different language?

System.Default(), still not documented I think

Seems unlikely that your diagnosis is accurate. If you could provide an example file and your code I think it would be easy enough to find out what's up.

If lots of people tell you that they don't fully understand your question, I respectfully suggest that you clarify what you are asking. It's easy for us all to write things that we think are clear but find that others don't fully understand. My guess is that you want to stop your program putting anything onto the Windows clipboard. Exactly how to do that depends very heavily on what controls your program uses.

Then you'll have to debug this yourself.

If you want to solve a problem, the first step is to understand it fully. Guesswork is unlikely to be successful. If you want help from others, help them to be able to reproduce the issue.

That reproduction is still required

GetLastError is bad advice. COM doesn't report errors that way. If you would just show a complete, minimal example, it would be easy to help.

If you have 32 bit code that works then that same code will work in 64 bit. We can't see your code.

Automatic header convertors tend not to be very effective in my experience. Don't expect to be able to get a working import unit without human intervention.

You can't kill it reliably and robustly. You can kill it, but expect consequences in your process.

TerminateThread does the job. But do expect your process to fail as a result.

If you have a demo program written in C or C++ then it is easy enough to translate to Delphi. But you'll want to learn some basic C or C++ in order to do so.

You can't do what you ask. You need the isolation offered by processes in order to robustly kill something. You can't kill threads safely. All those other topics that you found that said the same are still a cue.

You don't have time not to read

Any data structure that encodes depth in a static name is surely the wrong solution. Have you read any books on data structures?

What you really want is to separate the iteration over the data structure from the action that you perform on each item. Otherwise you end up with massive duplication of code. Also, this data structure seems pretty unlikely to be the right way to represent any data structure I can imagine.

How do you know that?

https://devblogs.microsoft.com/oldnewthing/20150304-00/?p=44543 https://devblogs.microsoft.com/oldnewthing/20120326-00/?p=8003

Assign to the form's Icon.

As it stands, in your code it will only be inlined in the code in the same unit as the implementation, and only for calls in functions declared after the inline method implementation. You can check this yourself by inspecting the disassembly of calling code.

If you want to terminate the process, terminate the process. Ignore the threads. System will tidy up all the resources, including the threads. Let it do it though, don't you try. ExitProcess does the job.

Not so. You are just as likely to have subsequent errors as the shutdown code in the main thread runs.