FPiette

Could you be more specific about what doesn't work as you expect? Maybe add some screen shots showing the issues? Which component is not showing correctly? If you think Delphi 11 has a problem, please write a report at https://quality.embarcadero.com.

How much are you ready to pay for such a DLL? Would probably cost more than upgrading your Delphi version.

Did you reinstalled the same Delphi version that you had before and for which you have a license key? By the way, you should have a backup of your system and restore that backup. That way all your software would be still installed and registered. Now, once your system is up and running again with all important and costly software reinstalled, you'll start to backup it regularly. I suggest you use a tool like Macrium Reflect to create images and rescue disk. Of course you need [removable] disk with same capacity.

/* Don't be offended */ Many peoples are asking questions about how to implement a solution to a problem they have. You gave the reason why you are asking your question and I gave answers to help solve the update problem you have (I don't have that Windows 10 update so there should be no reason for you to have it). Probably you can achieve your goal by launching netsh utility from your Delphi code. Look at the doc: https://docs.microsoft.com/en-us/windows-server/networking/technologies/netsh/netsh-contexts

Which version do your have ? There are several DIFFERENT Windows 10 version. It has been largely enhanced since the first version! Major updates are in the optional updates so you probably are still running the first version. That would explain the different behavior between your WIN10 and mine. Currently the last major release is named "21H1". See attached image from my system.

You system must be badly configured. I never have a force reboot using Win10 PRO: the system tells me a reboot is required but don't reboot by itself (You can also set the working hours so that the system still reboot but only in the non-working hours). I suggest you have a better look at all the related setting. And also make sure you have the latest Windows 10. Currently this is version 21H1.

As I said, a variable having a type equal to a class use NO MEMORY until it is assigned a value coming from the constructor (A constructor use dynamic memory allocation to create space for the object instance and return the pointer). If you copy another variable value, then you have a second pointer pointing to the same object instance. beware of pointer becoming invalid as soon as the object pointed to is destroyed.

A class declaration doesn't allocate any memory unless there are class variables inside that class. Memory is allocated when - at run time - the constructor is called. A variable having a type equal to a class is actually a pointer to the memory allocated for the class instance by calling the constructor. Class are handled "by reference". By the way, you should by a good book about Delphi programming (the language, not the runtime libraries). Look there to make your choice: https://delphi-books.com/en/

You are in an ICS support forum, not a devexpress one. Please repost your question at the right place. Since devexpress is a commercial product, the best place is probably the support area at devexpress website (https://www.devexpress.com/).

May be this StackOverflow article would help?

Did you try compiling a sample code with that syntax?

There is not that I'm aware of. And I think it is not possible. Defragmenting memory would mean moving memory around and thus invalidate any pointer your application has. Also note that at the lowest level, there is virtual memory that the system use to build the virtual address space your application see. The virtual memory is managed by pages (Usually 4KB each). Those pages are mapped to the user address space to make a continuous block of virtual memory but the pages in physical memory can and are moved by the OS. The pages are even swapped to disk when physical memory comes low. Have a look at this wikipedia article about virtual memory.

I said that for that particular user, it is the same as double click.

What I said is perfectly correct. To open the PDF file, with ShellExecute (The question here), the open verb must be used. Using the nil verb would cause trouble in the 0.01% people having tweaked their system. The point is to open the PDF with ShellExecute, not what happens when anyone double click on a PDF in Windows Explorer. The only important thing - beside opening the PDF - is that when THAT PARTICULAR user, the OP, double click on a PDF it is opens the PDF. That's it. Anything else is out of topic and pointless. You are of course free to think otherwise but don't try to make me think like you do. Don't try to teach the whole operating system when someone has a simple problem, especially to a beginner, you'll just confuse him. At some point in the study, certain points of detail must be taken for granted. Later the student will understand all the details. Later is the most important word here. In any case, we have something in common with Remy: when we have an idea, we defend it fiercely. The other people must have a good laugh, admitting that they are following the conversation. Or it bothers them deeply.

@Remy Lebeau I perfectly know all that. I said the the OP to use the "open" verb to open his PDF with ShellExecute and I told him that would be the same as double clicking on the file with Explorer. I'm sure at 99.999% that THIS PARTICULAR user has the open verb as default for PDF file so I said that the open verb will do the same as the double-click. I never said that it is not possible to tweak the verb associated with PDF file so that open is no more the default and that for an incredibly small amount of peoples double-click on PDF would not open it. This has nothing to do with the question I am answering. You are just confusing the OP with all this pointless discussion and you are not alone. We could have had this discussion if the OP had said that double clicking on the PDF didn't worked for him.

This is true for that particular user as well as 99% percent of user.

That is what the explorer do for that particular user as well as 99% percent of user.

Sure, but the OP ask to open the file, not execute the default action. For PDF files, the default action is to open the file, that's why double clicking a file in Windows Explorer has opened the PDF file for the OP. I just told the OP that using open verb will open the file like Explorer did and which is not the same as the command he was using.

A list is a good solution for that. Either a list of strings, or a list or colors or a list of color index. The best depends on what you need to do with that data after having captured it. Example: var ColorList : TList<TColor>;

@JDS2018You should check return value for error. You said opening the file manually works. Do you mean you entered the exact same command line in the command prompt or you just double clicked on the PDF file to open it? They are different operations... By the way, you can use ShellExecuteEx (Or ShellExecute) with the "open" verb to do the exact same thing as double clicking on the file using Windows Explorer.

Please show a minimal reproducible example so that be better understand what you mean. The situation is not the same on 32 or 64 bits. You need an array of pointers pointing to arrays of the datatype (You didn't say anything about the data type you use/need). At first glance, you should probably use a kind of linked list of arrays of pointers. For performance, you should also think about how the data is accessed so that the processor's memory cache is used efficiently.

Are talking about a 64 bit process or a 32 bit process running on a 64 bit system?

Why don't you ask the user what configuration he is using?

First, look at this https://en.delphipraxis.net/search/?q=websocket&type=forums_topic&nodes=37

Which problem exactly are you trying to solve? Describe the scenario you are faced with. Solution given by @Darian Miller is good. One similar is: protected FClickRunning : Boolean; procedure TUButton.Click; begin if FClickRunning then Exit; try FClickRunning := TRUE; // Do the stuff, call inherited and more finally FClickRunning := FALSE; end; end;