David Heffernan

Inject code into every process

C++ already has using

What you are trying to do is possible. I guess there is just a mistake somewhere, or some extra detail that we don't know of yet.

graphics32 is generally faster than gdi I believe

Or a pure Pascal library like graphics32

I would have imagined that you'd want some coordination, not everybody having their own copies, all different. Also, git in particular, and dvcs in general are very complex. You sure you want to throw that at your users. But hey, what do I know about your needs. Nothing. If you want to use git then go ahead. For instance with libgit2.

Doesn't sound very much like dvcs is what you need. Sounds more like a central database is what you need.

Probably you'll need to show an complete program, obviously cut down to minimal form, if you want somebody to dig deeper.

Why would you be drawn to Embarcadero C++ tools? If you are going to consider C++ then you have a much wider range of options.

Lars understands that, I think, and wonders why the compiler doesn't take the same view and issue a warning.

That's not right. In order to evaluate expressions the debugger needs to execute code in the target process. Which may lead to allocations. It's a defect that the IDE / debugger leak such objects, but they can't do their job if they can't execute code and perform allocations in the target process.

This is a known bug in the IDE / debugger. Nothing you can do about it. Evaluating certain expressions, often involving strings, seems to be what triggers it.

This is why you should make a repro. Worth bearing that in mind for the future.

Encryption is agnostic of framework. I don't see how you could have a VCL only encryption library. You don't need design time components.

Component vendor is wrong.

Timers are for GUIs. MsgWaitForMultipleObjects is one sound way to implement a message pump on a thread that needs to do tasks periodically.

No you won't. There are plenty of timer free solutions I would expect. Very hard to give advice without context. And very hard to explain why messages are missing with only a partial extract of code. Anyway, good luck.

A complete repro is probably necessary here. A timer seems needless. Just keep track of the time when you last flushed and do it again once a second has elapsed.

You reap what you sow. Don't create multiple variables with the same name.

Don't think that's true. That's the point of the broadcast message. The shell updates its environment and uses that when creating new processes.

Did you do any debugging? Did you check that the registry was modified as intended? Reference back to https://docs.microsoft.com/en-gb/windows/win32/procthread/environment-variables

You code runs the risk of hanging when it broadcasts. But the basic concept is correct albeit poorly implemented. Have you done any debugging?

The answer in that link appears factually misleading at best, probably downright incorrect.

Provide a minimal complete reproduction.

This approach is what you take when you hate your users. They can't tell whether or not your program is stuck in a non terminating loop, and the OS asks if you want to terminate the program. So only do this if you want to make your users suffer.