PeterPanettone

May I ask where I can see the INSTALLED MMX version number? On my MMX About page I cannot see a version number:

Dear Thomas, I understand you perfectly and I agree with you. I greatly appreciate your valuable work and as soon as my financial situation allows it I will make a substantial donation to your project. I also had a look at the source code. It is very complex and I fear that I would make things worse if I change something.

Dear Thomas, I have not requested that you write these feature request entries. I just wanted to contribute to the general discussion. I didn't know that I have a duty. Thanks anyway.

Another very useful option in the GExperts Grep Search dialog would be an option to extend the search scope to all unit file contents contained in the uses clause(s) of the current file/project. But that would involve solving the problem of retrieving the paths of the used units.

Even better: Save and recall complete searches including ALL settings in the Grep Search dialog.

To efficiently work with Regular Expressions in the GExperts Grep Search dialog I suggest: • Implement customizable RegularExpression TEMPLATES in the GExperts Grep Search dialog (because inserting a regular expression like \['\{[0-9A-F]{8}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{12}\}'\] with a single mouse-click would definitely be an advantage) • Make the GExperts Grep Search dialog resizable

Thanks for the information, but the linked article doesn't contain anything I didn't already know. On the other side, it is obvious what Embarcaderro could do to fix the above issue in the GetIt Package Manager which IMO is simply simple programming negligence. I mean, for me there is no font size problem in the Delphi 10.3 IDE except the title bar controls. But cutting off interface elements like buttons isn't something which has been well thought-out and tested. Does Embarcadero test its IDE in different environments before releasing it? I would be happy to help as a beta tester.

I have Windows 7 x64, not Windows 10.

In the Delphi 10.3 Rio IDE, where is the Save Desktop... menu item? I have not found it in the View -> Desktops submenu:

You are right, the Mercedes CLA has the (electrically operated) handbrake on a "left down under" position. Very impractical!

I have no "moon icon" in the IDE titlebar. Only after moving the IDE window with the mouse the titlebar controls become visible: Why does Embarcadero HIDE important commands in spooky places? That would be the same as a car manufacturer hiding the hand brake in the car trunk.

This is my configuration: Main Monitor: Monitor 1: LG ULTRAWIDE(38UC99)(Display Port) (3840 x 1600 pixel) (87 x 37 cm) Second monitor: Monitor 2: PHL BDM3270 (1440 x 2560 pixel) (71 x 40 cm)

Hello, when I edit the property of TForm.Caption... in the Object Inspector: ...then this dialog appears: I assume that this is the JEDI StringList property Editor (because of the "J" icon)? Is there an easy way to disable just the Jedi property editors? BTW: A property editors Manager for Object Inspector would be very nice!

It seems that maybe the list of items is being rebuilt each time a search is performed...?

I just wanted to say a public BIG THANKS to Mr. Fierens from TMS for his amazing and outstanding support: Today (which is a SUNDAY) I mailed him the description of a small bug. ONE HOUR LATER I got the bug fix attached as source code file in the mail. I never had a product (TMS ALL ACCESS) with such outstanding support quality!

When trying to install ...\Delphi-Shortcut-Finder\Packages\XE8\nick.toolsapi.shortcut.DelphiShortcutFinder.dpk in Delphi 10.1 Berlin I got these compiler errors: [dcc32 Error] nick.shortcut.frame.KnownShortcuts.pas(143): E2003 Undeclared identifier: 'HintAnimation' [dcc32 Error] nick.shortcut.frame.KnownShortcuts.pas(143): E2003 Undeclared identifier: 'hatFade' [dcc32 Fatal Error] nick.shortcut.core.KnownShortcutsRegistration.pas(20): F2063 Could not compile used unit 'nick.shortcut.frame.KnownShortcuts.pas' This is the list of the package folders: XE XE2 XE3 XE4 XE5 XE6 XE7 XE8

Thanks for the information! @Pascal Expert wrote: You should prefix the reference, like “B.TheValue”, to avoid any uncertainty. Good advice!

Actually, to check for namespace ambiguity, it would be also useful to NOT stop at any match. For example, an addon which checks for namespace ambiguity would traverse all type-identifiers in the source code and check whether any type identifier (at least those with no fully qualified namespace prefix) is implemented in more than one used unit. That would be very useful, as type-ambiguity bugs can be very nasty.

Exactly. There should be an option "Add scope prefixes", that when inserting an object instance in the IDE Designer, for example when dragging a button object from the Tool Palette to the form, then the IDE should automatically insert this code: type TformMain = class(TForm) btnGenerateCertificate: Vcl.StdCtrls.TButton; //etc. The scope prefix is very important because it removes ambiguity and it adds clarity.

Logically, it would have to stop when it finds the first match. But I don't see the need to start from the last unit. How would you define the order of the units?

Obviously, it would be very naive using a simple text search in the implementation of *Contains*. That proposed pseudo-code would need an intelligent implementation. Maybe I should have written: if Unit.Implements(AIdentifier.Name) then ... to make it more clear.

Would such an approach be too simplistic?: for each Unit in UsedUnits do begin if Unit.Contains(AIdentifier.Name) then Result := Unit.Name; end;

Thanks for the explanation! Unfortunately, "Find Declaration" in such cases: ...mostly does not work.

So would you please consider adding this very useful functionality? I have made the experience that "Find declaration" for some identifiers works better if the identifier has this kind of specification.

Thanks for "Format Uses Clause" command! Is there a similar command to achieve the following: Turn this: type TformMain = class(TForm) btnGenerateCertificate: TButton; //etc. Into this: type TformMain = class(TForm) btnGenerateCertificate: Vcl.StdCtrls.TButton; //etc.