PeterPanettone

I clearly said this is for Delphi 12 Athens. Using just a few compiler conditional directives, you can restrict any code to specific newer Delphi versions, for example: {$IF CompilerVersion >= 36.1} // Code for Delphi 12.1 or later {$MESSAGE WARN 'Only for modern Delphi versions'} {$ELSE} // code for older Delphi versions {$IFEND}

On my HighDPI monitor the CodeLibrarian Search dialog was still broken in r4431, so I fixed it: This should now work with all DPI settings on the end user side, as it now uses a Manifest in modern Delphi 12 Athens instead of a custom "InitDpiScaler": constructor TfmCodeSearch.Create(_Owner: TComponent); begin inherited; //InitDpiScaler; // now using Manifest in Delphi 12 end; fmCodeSearch.Scaled := True; // Set in Object Inspector I've also modernized the LAYOUT from StoneAge Layout (simply place components anywhere without layout considerations) to Modern Layout (use Align and AlignWithMargins properties). Here is the new source of the Search dialog: GX_CodeSrch.zip

In r4431, the Rename Expert is now finally fixed: However, it would be LOGICAL to place the Buttons (OK, Cancel, Settings) at the BOTTOM: Clicking the OK button affects not only the newName setting but also the Align/Anchors and Margin settings.

I have YOU to thank for such an ingenious product as GExperts! I could not take over the maintenance of GExperts. YOU are the leading expert for GExperts!

Dear Thomas, you are completely right! But all these DPI problems can be OVERRIDDEN by using an optimal LAYOUT. The logical error is to focus only on one issue (the DPI settings) while ignoring the broader context of responsive design and layout adaptability.

I use Delphi 12.2 in Windows 11 and have just now downloaded and compiled version r-4418: 1. you should not trust the GExperts users to use the same DPI settings as you when they compile the GExperts source code. 2. you should prioritize LAYOUT over blindly trusting that your DPI settings will work for the users when they compile the GExperts source code. Following rule #2, I have now moved the main dialog buttons down to the bottom into a separate panel, which creates a more logical layout: In the next step, I will adjust the layout logic for multiple properties.

Dear Thomas! Can you please post a screenshot with multiple properties? Thank you! And a happy new year! 🎈🙋‍♂️

Hello Thomas, Thanks for the information. The GExperts Rename Component expert is indeed useful when changing only the name. However, with multiple properties, the layout is broken and inconsistent:

I want to achieve this design time automation: Whenever a new object is created (either from the Palette or by pasting an object from the clipboard), the Quick Edit dialog for the new object is automatically shown. Is there a way to achieve this with GExperts?

Having flexible UI options is always a good thing. Thank you!

Better display of tabs in the SourceCode editor (OPTIONAL): 1. Marking of the MainForm unit in bold font 2. Marking files that do not belong to the current project in italics This would lead to more visual consistency and transparency in the presentation of the tabs in the SourceCode editor. What do you think? Thanks to everyone for taking part in this BRAIN TEST!

Another solution could be to subclass TRichEdit and then (temporarily) suppress the TAB character, but it's not worth the effort.

Thanks for the information.

Using KeyPreview, I have even tried the following trick: procedure TformTextEditor.FormKeyDown(Sender: TObject; var Key: Word; Shift: TShiftState); begin if (Key = Ord('I')) and (Shift = [ssCtrl]) then begin CodeSite.Send('TformTextEditor.FormKeyDown: '); Key := 255; end end; And then in RichEditKeyDown: if (Key = 255) and (Shift = [ssCtrl]) then begin CodeSite.Send('RichEditKeyDown: '); Key := 0; // does not prevent TAB output! end

Even when KeyPreview = True, setting Key := 0; in FormKeyDown does not prevent this strange effect: procedure TformTextEditor.FormKeyDown(Sender: TObject; var Key: Word; Shift: TShiftState); begin if (Key = Ord('I')) and (Shift = [ssCtrl]) then begin CodeSite.Send('TformTextEditor.FormKeyDown: '); Key := 0; end end;