timfrost

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.

Sysinternals tools may give you a clue as to what is happening. Process Monitor filtered on the Delphi process will show you if the active thread is busy accessing the file system or the registry, and Process Explorer will display the active threads of the process and can snapshot the stack of each one - it can show much more information about the process than Task Manager.

Can I please say that I find the MMX user interface entirely satisfactory in daily use. This thread has reminded my about some useful features which I had forgotten about, despite many years of using the product. I would not want them removed, and since the icons take little space I would not want them hidden. There are perhaps minor features that I would improve, but they do not cause me any trouble and I appreciate that supporting the product is done as Uwe finds time to allocate to it.

I have a copy of DIBControls.zip downloaded in November 2007, but I do not recall ever having used it. And an e-mail from Peter Morris in 2002 announcing the new Droopy Eyes website. Another Delphi component that has fallen by the wayside, perhaps. Though there are other disappeared items from even earlier that are still in use here.

Try a later VT version; I think 7.2.1 is the latest. I have noticed several speed enhancements mentioned in the changes/fixes.

The obvious one that you have missed is to use an earlier version of Delphi, that matches the DCU version.

In my case the problem of the inability to select CPU view is related to MMX, but I also now agree with you that GExperts is involved also. I have been experimenting with both the checkboxes in the Delphi IDE key mappings, and the key mappings display in GExperts, and there are inconsistencies. I also tried Ctrl-Alt-D which picks an MMX action, even though Gexperts shows it in yellow.

The Torry listing for this says 'source on request'; and I agree with you about source code. And not seeing a published source price is never a good sign.

Answered on SourceForge (with apologies for believing the original report without testing). It turns out that Ctrl-Alt-C is one of the shortcuts defined and documented by MMX Code Explorer, and is easy to change. And I was pleased to discover the very useful list of shortcut key owners in GExperts, which I had never enabled before!

I have added a bug report on SourceForge

I used to think that the long-time failure of the CPU-window short-cut was an inexplicable Delphi bug, but I have always used GExperts in many Delphi versions. Thanks for identifying the probable source and I second your request for a fix (and the thanks for maintaining GExperts)!

Don't forget to clear the Windows icon cache after you have made an icon change, to be sure that you are seeing what your users will see on first installing your application. Your search engine will find many ways to do this, some of them better than others...

Which version of Delphi are you using? Is this is Rio or an older version?