Uwe Raabe

The plethora of working Delphi programs are proof that there already exist concepts to eliminate dependencies between units. They may differ from those available in other programming languages, though.

IMHO, circular dependencies should be eliminated even if they appear in implementation sections and thus making the code compile. I wouldn't support any request to extend that in any way leading to more circular dependencies.

42 minutes ago, Patrick PREMARTIN said:

Your code will remain the same

Only if you don't make use of Change Views. AFAIK, it also lacks Column-level Encryption.

27 minutes ago, Al T said:

I'm just royalty pissed off at the "AMENSTY" pricing. 

I guess everyone has got that now.

AFAIK, the Delphi IDE Menu Designer did never support images.

17 minutes ago, Lajos Juhász said:

On the other hand, it does not work for the Bookmarks or the Parallel debugger

So they seem not to be able to manage it even when they hire the developer. 

21 minutes ago, Lajos Juhász said:

The only thing that could be better in theory is integration. They would see what could be improved to make it work better.

Obviously that is more wishful thinking than perception of reality. I simply cannot see anything like that going to happen in the foreseeable future.

BTW, I still even refuse to provide MMX via GetIt for several reasons.

5 hours ago, Berocoder said:

Have there ever been any talk with Embarcadero about use MMX Explorer instead?

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

On 5/26/2024 at 8:14 PM, PeterPanettone said:

Making the behavior of a compiled executable dependent on something that is not in the source is simply IRRATIONAL.

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:

4 hours ago, dummzeuch said:

Is that only within a project group or global over all projects that MSVS ever opened?

5 minutes ago, Gert Scholten said:

now we can't see the help files either

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.

24 minutes ago, Navid Madani said:

GetIt claims that the "12.1 Patch 1 1.0" previously applied is not installed

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:

Quote

Version 1.2 of Bookmarks allowed users to assign a name or description to a bookmark. This interface allows you to read that name.  Use IPnAPIBookmarkList2 to change the name of a bookmark.

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.

43 minutes ago, PeterPanettone said:

The developer only has to take 5 minutes and switch on his brain.

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.

15 minutes ago, UCT_24 said:

The "Vcl.Forms.TApplication.MessageBox" and the "FileChooser (not sure about the exact class name here)" are not affected by the registry key

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.

17 minutes ago, UCT_24 said:

I tried switching the language set for bds.exe, and this changes the display language of the bds.exe.

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...