Uwe Raabe

At least back then they had no interest. Current state: it is actively maintained it is available for a couple of recent Delphi versions it is free for all Delphi SKUs Would you bet on all that not going to change?

I always try to get my projects on the most recent versions as soon as they enter a state where I can benefit from the features while being able to tame the defects. The less active a project is, the larger gets the gap between the used version and the recent one. Nevertheless, also these projects are moved to newer versions, albeit on a slower rate. Some customer projects have to stay on older versions, either due to decisions out of my realm or lack of demand for maintenance and enhancements. Whenever either becomes necessary I also try to get this on a newer level. Usually the costs for that cancel out with the higher effort of maintaining it with the older version. Whenever I am forced to work with any of these older versions (mostly D2007 or XE2) I immediately realize why I always prefer to avoid doing so.

There is also time playing a role here. While Delphi 1 had most likely a pretty low number of bugs, it is not usable in these days at it produces code for 16-bit Windows. Also the often praised Delphi 7 runs pretty unstable in a modern environment. Let alone all those "feel-like-bugs" of none existent behavior.

You might have better luck with TPngImage.CreateBlank.

Probably related: https://quality.embarcadero.com/browse/RSP-43125

Of course it is possible to write the SVN revision number into the source, but when you commit that change to SVN it gets a new revision number. That's why SVN replaces a special keyword in the sources with the current revision number. Letting alone that the concept of a revision number is some SVN thing and has no counterpart in most of the other version control systems for several reasons. The more I think about it the more I like the no-downloads approach...

While "of all" can also mean "of all open". Given that Bookmarks stores its bookmarks per file it may not have any concept of "files of a project", while "open files" seems like a valid filter. Otherwise it would resurrect this question:

C'mon, that is just not true! The help is available here: https://docwiki.embarcadero.com/Libraries/Athens/en/Vcl.FileCtrl.SelectDirectory

If you just registered for the portal it needs some time to get you attached to the proper group. To speed that up you can file a new issue yourself.

This can happen when the Patch has been installed with another user or different registry branch.

The Bookmarks plugin already provides a list of bookmarks for all open files. There is also an option to give a name to each bookmark. Looks like the only missing feature is to show the bookmarks from all project files.

I wonder if that can be implemented based on the Parnassus Bookmarks plugin available in GetIt. The API description mentions:

As I am not familiar with this feature, I wonder what the difference is between a standard bookmark and a global bookmark.

Well, it is definitely not a bug, so in case you filed it as a bug the "Works as expected" is indeed a valid answer. A dimmed selection color is actually standard behavior for non-focused Windows controls. Better file it as a feature request, as it asks for a change of the current, technically correct behavior.

Before doing so, the developer needs to get assigned a task for it. This requires the product management to schedule such a task, which itself requires that there actually exists a request for it. If there isn't already one in the issue tracker I suggest to create one.

I am not sure if that actually is a native Windows control. Given the context aware, mixed font style and color node drawing it could as well be a TVirtualTreeView descendant.

To reduce the need to keep that file updated with every new Delphi version I just changed that phrase into a version agnostic alternative. Will be available with the next update.

Probably lack of time to update the less important parts.

These dialogs are not part of your application, but are provided by the operating system and thus follow the Windows settings. There is not much you can do about it. The app BDSSetLang.exe found in teh Delphi bin folder has an option to change the Library language apart from the IDE language. This will use another set of resources when compiling your application.

I wonder if 42 would do, too...

Showing the actual content of the DBW.ini file located in E:\DBiWorkflow. Best attach the complete file so we can scan for suspicious characters.

Usually, yes! Peganza Pascal Analyzer even has a report for that:

You can as well simply scroll the form as needed, but the need to scroll was exactly the complaint.

Indeed, but they still reside in the interface section and thus may need some units being used in the interface section instead of the implementation section.

Another option could be calling SetLocaleOverride with the desired value. It just has to be done quite early as long as no resources are being loaded.