Uwe Raabe

I just had a quick look into the sources and it is indeed so that the help icons are located statically and don't move when the control to the left resizes (which they actually should). I have to go through all of these (which are a lot) and check for that link.

Of course I have. After all it should adapt to DPI changes when the dialog is moved to another monitor. I rather suspect the help buttons rely on a specific font size. Will have a look.

I wasn't able to reproduce it with these steps on a simple new project. Can you try it again with a new VCL Forms project with a plain Integer property added to the form? I just want to narrow it down to the installation/settings or the actual source file causing this error.

I can also vaguely remember that Andreas claimed that as the reason why there will be no IDE Fix Pack for Rio. Unfortunately I cannot find that statement anymore, so it should be taken with care.

Can you try the same using a different or no password? Besides an error regarding the wrong password, does it succeed then?

Might be worth to ping @Allen Bauer with that. I doubt there is anyone at Google with more knowledge about Delphi and the RTL.

It installed flawlessly here, but I have to admit that I used an old Raize serial number which the installer automatically suggested.

Radiant Shapes has been acquired by Embarcadero a while ago: Konopka VCL Controls & Radiant Shapes now part of the Berlin Bonus Pack

Who hasn't seen this before: A bunch of controls and actions are linked to an ImageList with an ImageIndex, but as soon as you sort this ImageList to give it a sensible order all controls immediately start to show the wrong images. Wouldn't it be cool if instead a cryptic number as ImageIndex you could specify a descriptive name at the control? Thus the order of images inside the ImageList wouldn't matter at all. Of course, the ImageList has to support names in the first place. TPngImageList from PngComponents does that right from the beginning. So what about implementing that feature based on TPngImageList? Can't be that hard, can it? Well, it turned out to be a bit more complex than I anticipated, but that's probably because I had set my goals pretty high. So I expected to have a selection from image names for the ImageIndex properties of the control and thus a display of the image name instead of just a number. Also this scheme should be extendable to other controls and especially to other ImageLists supporting names. From this the ImageIndexMapper was born. A non-visual component to be placed on a form or datamodule, that when activated takes care of the image names. You just have to call one method to resolve those names to the actual corresponding number values. The attached ZIP file contains all the sources and files for the component and design time support as well as a sample project (currently for Delphi 10.2 Tokyo only). As a prerequisite you have to use PngComponents from the above source. I suggest to use the recent version V1.5.0 with direct ImageIndexMapper support. Older versions require the contained PNG Support Package to be installed and add the corresponding unit to your uses clause somewhere in your project. Version 1.5.0 makes this obsolete, Presumably there is much room for improvement. Whoever finds some time to test this component - please forward any encountered bug to me. Here is a short GIF showing the switch from TPngImageList to TImageList (without name support) in the Object Inspector: https://www.screencast.com/t/4MbJkygjFR ImageIndexMapper.zip Cross Post: https://www.delphipraxis.net/198212-imagename-statt-imageindex.html#post1415709

No problem. I attach it here again. ImageIndexMapper.zip

Looks like the attachment got lost in this forum. Please try the cross post mentioned above. The attachment there still seems to work.

Probably not for myself

May I ask, why not?

Actually clients do think this way! A couple of years ago we made a poll about features our customers want to see implemented in our software. Nearly 2/3 of the answers were about visual appearance. Probably because that is what the customers see and work with. They usually don't understand the internals and simply assume they just work. Even now I get approval for changes much easier if they are heavily accompanied by visual enhancements.

How are they sorted?

The component is going to notify other components when it is destroyed. A component can register for FreeNotifications by calling AComponent.FreeNotification(Self) and unregister with AComponent.RemoveFreeNotification(Self). The notification is done by calling the Notification method of all those registered components. This is usually done to update a local field pointing to that component to prevent dangling pointers. Perhaps some component doesn't follow this pattern as closely as it should do.

Can you elaborate on this a bit: What is the sort used for (iterating and/or searching)? How do you sort duplicates from different files?

Static arrays are never freed. That's why they are called static. They live as long as their scope lives.

Good catch! This allows me to create a reproducible test case and send it to David Millington.

That empty popup menu also happened to the CnPack guys during beta. I could also see it while fiddling around with making MMX support themes. It happened with a standard toolbar button set to DropDown, while the currently used TB2k/Tbx popup menu works. As ever so often it could not reliably been reproduced with a simple test case.

Even that would be a bit tricky if the Live Viewer is running on a different machine.

I had seen the same error with the editor context menu of MMX. The first time after a fresh IDE start it works, but fails on subsequent right clicks. That is why I removed it for Rio. I also noticed that the menu entry was moved to the top on the first context popup, albeit it was definitely added at the last position. Something fundamentally changed with the context menu in Rio.

Unfortunately not. It uses some ToolsAPI interfaces only available in later versions.

You can automate this with Pascal Analyzer: Control Tab Order Report

BTW, rebuilding with C#/.NET will cost a multiple of time and money with no real benefit but plenty of problems.