timfrost

There was a 'b' version of the ISO a short while after it first became available. Perhaps this had only a few files changed, and these are now also in the alternate installer (which I have nerer used).

It sounds as if in your VT1mousedown event you should first call vt1.GetHitTestInfoAt to find out whether the mouse has been clicked on a node or not. Once you have the node, it is up to you to work out what you have put in it and whether it is a selected/focused node, and what to do with it if so. Presumably you always ensure that there is a node type or tag in the nodedata.

https://quality.embarcadero.com/browse/RSP-25564

We have used this for many years and found it very robust and comprehensive. For some periods in the past it has not always kept up with every IANA update, but currently it includes the latest one. You can always update the embedded data yourself using the provided compiler, if you subscribe to the TZDB mailing list to get notified of updates. Our software only needs to be aware of future zone and DST changes, not those in the past, so I modified the compiler to omit all the information about which day in 1928 the DST rules were changed in Alaska or Zanzibar, and other such fascinating facts. It's very simple to use if you have a need for the TZ information that IANA maintains.

@Stefan Glienke What version of MMX are you using? I have 14.0.4.2274. Could it be that the default MMX shortcut has recently changed?

The fact that the shortcut for Debug ... Entire CPU does not work for me has annoyed me for many years, but never quite enough to investigate it. But I am not sure that your analysis is correct. This shortcut is Control-Alt-C, and that in MMX for Copy Entity is Control-Alt-NumPlus. I have never customised any of the MMX shortcuts. The shortcut-owner display in GExperts shows Control-Alt-C as Debug CPU, so I still have no idea what has stolen it; but MMX does not seem to be the culprit here. Edit: I see that Control-Alt-C does work to switch focus to the full CPU window, but only if this window is already open. Another extraordinary EMB feature. If for example I click in the stack window, then this shortcut switches focus to the CPU tab. But it does nothing if I am in the editor window.

When it happens, on my 4k monitor, I find there is a tiny slice of the red X which still works to close the IDE, if you hover the mouse at the edge. Going out of full screen, then back, restores the missing strip.

To answer your question, yes, I have done exactly this. But in my case program 1 was guaranteed to be a singleton on the machine, so I could just create an empty registry key before invoking program 2 and have program 2 place the result there. If you have control over the number of instances of your program 1 you might be able to adapt this solution. It has the advantages of extreme simplicity and needing no extra tools or special functions.

The problem described here is the basic reason (of course there are others) why I have never considered downloading from Getit any tool or component we will use in a production environment. We have source for all the components we use and for every one the BPL/DCP is built by a Finalbuilder project under our control. And if you download and install something from Getit (when it comes back up) how do you check precisely what has changed since you last downloaded it? Where has your older version gone, for comparison?

1.3.13.77 doesn't crash on IDE 10.3.2 exit here. This is consistent with an incompatibility with some other package that I do not have, but David Hoyle does. I have Documentation Insight, MMX Code Explorer and IDE Fix Pack 6.4.2 installed.

@Ian Branch Please read it again. It says name without, value with; and in the picture both without. I referred to the value. But it is immaterial because neither had any effect for me.

@Achim Kalwa Your IDEFixPack.DisabledPatches suggestion did not work for me in 10.3.2. The error message still appears. Your post says the value should be entered with quotes, but the screen shot shows it without; however neither option was effective. I also tried putting the value in the system environment and this was also ineffective, with or without double quotes.

For only 200 values you would have to be running your algorithm many times a second in order to detect any differences. I would simply put all the values in an indexed array and every time you update a value, simply check it against the previous lowest value. Then save its index and update the lowest value if necessary. Whether this is practical or not depends on how many threads are simultaneously updating the values, how long the algorithm takes to run, and what the intervals are between iterations of the algorithm. I have no idea whether this is the fastest way to do it, but it is simple, and for 200 items, as I said, I would not care if it took a few microseconds longer. If microseconds are really important to you, then it is essential to test and measure, not guess; so you must ignore my advice.

I have seen "kilometrage" used in UK English, and kilométrage in French. I would vote for it if you organized a competition, although it is ugly and not in wide use. If you are using the word as a column heading, you need something short. But in a descriptive sentence I would prefer a phrase like, "lifetime rolling kilometres" or "total kilometric distance". Googling lifetime kilometres only turns up FitBit links.

If Rad Server is not visible, maybe your Delphi license does not include it.