vcl | Visual Computing Library | GPU library

From the documentation for GetKeyNameText:

24 Extended-key flag. Distinguishes some keys on an enhanced keyboard.

This says that it uses bit 24 in the LPARAM-styled argument as the extended-key flag.

Then, in About Keyboard Input:

Extended-Key Flag

The extended-key flag indicates whether the keystroke message originated from one of the additional keys on the enhanced keyboard. The extended keys consist of the ALT and CTRL keys on the right-hand side of the keyboard; the INS, DEL, HOME, END, PAGE UP, PAGE DOWN, and arrow keys in the clusters to the left of the numeric keypad; the NUM LOCK key; the BREAK (CTRL+PAUSE) key; the PRINT SCRN key; and the divide (/) and ENTER keys in the numeric keypad. The extended-key flag is set if the key is an extended key.

(body text emphasis mine).

Therefore, I conclude, that you can use

Create your own style with the color you like.

You can't do this with objects directly as they are scoped by the VCL and can't "escape" it. As you've experienced, you need to load the labeled vcl first, so you also need to create the object in it.

But nothing prevents you from creating objects that reference a global variable so all objects have access to the same data.

Alternatively, you can use the Event function to use a PRIV_VCL (https://stackoverflow.com/a/60753085) also referencing a global pointer and avoid using objects completely. This is what is done here for example: https://github.com/varnish/varnish-modules/blob/master/src/vmod_vsthrottle.c#L345

The Internet Explorer control is not quite designed to be given content on the fly. Therefore, my standard approach is to save my content to a temporary file:

This is the VCL code you need for banning:

I can reproduce your problem. I found a workaround: use the display rectangle of the selected item:

This is easy.

Your code Memo1.OnContextPopup := nil; has no effect because the Memo1.OnContextPopup property already is nil, as you can see in the Object Inspector; that is, by default you have no custom handler.

What you need to do is to add such a custom handler and set the Handled var property to True. At design time, use the Object Inspector to create an OnContextPopup handler for your memo, with the following code:

Looking at TDosCommand source code, you have 3 ways to know if the started process is running: use property ExitCode, or property EndStatus, or event OnTerminated.

Using OnTerminated event would avoid building a wait loop, which is usually not a good idea.

The problem seems to be the DSiUnregisterUserFileAssoc function not obtaining the required access level to the registry.

One of my rules of thumb when programming is to never use third-party libraries unless absolutely necessary, partly because you don't know all the details about them. And in this case, I don't quite see the point in adding a fairly large library just to do a few simple registry changes!

Making an association manually is trivial: