PeterPanettone

Here is version 0.3: The changes since the last version: - 2022-01-06: - Added F12 shortcut to Preferences menu item - Improved the sorting: When clicking on a column header, when loading specific IDE Projects - Set the Header-Title of the sorted column RED - Set the Project list Header-Font BOLD - Added an option to Preferences to generally hide non-existing Project files (of course, all Preferences are persistent between sessions) - Added a ToolBar Button to hide/unhide non-existing Project files temporarily DelphiMRUManager 0.3 (2022-01-06).zip

Here is version 0.2.2: The changes since the last version: - 2022-01-05: - Implemented SORTING: Click a column header to sort the Project list by that column For this I need user feedback: - Is the sorting working on your machine? - Do you have any suggestions? DelphiMRUManager 0.2.2 (2022-01-05).zip

I will do that, after searching for a tutorial on how to do that.

Here is version 0.2.1: The changes since the last version: - 2022-01-04 - Added "Hot"-feature to IDE-Selector - Added Drag&Drop feature that allows you to: - Drag and drop any Project from DelphiMRUManager to any Delphi IDE (while double-clicking a Project item in DelphiMRUManager always opens the Project in the last installed IDE) - Drag and drop any Project with the left mouse button from DelphiMRUManager to your File-Manager to create a copy of the Project file - Drag and drop any Project with the right mouse button from DelphiMRUManager to your File-Manager to create a LINK to the Project file This feature needs the open-source Drag-and-Drop-Component-Suite-for-Delphi: https://github.com/landrix/The-Drag-and-Drop-Component-Suite-for-Delphi - Added a button to empty the search-box DelphiMRUManager 0.2.1 (2022-01-04).zip

I will do that, after searching for a tutorial on how to do that.

I have made it with Delphi 11 Alexandria. Didn't it work with another Delphi version? Should I provide a SIGNED exe installer?

Here is version 0.2: The changes since the last version: - 2022-01-02: - Added a button to copy the path of the selected Project file to the clipboard. - Added a column that shows the Modified date of every project. - 2022-01-03 - Automatically and optionally loading all MRU Projects at program start - Several code optimizations - Optimized the Hint handling - Added a header panel and moved the IDE selection menu to it - Added an Options menu and a Preferences item to it - Saving and restoring window placement and settings DelphiMRUManager 0.2 (2022-01-03).zip

That's a good idea. One of the following things I will implement is FAVORITES and other project groups.

This is the PROTOTYPE of a MULTI-EDITOR where the single editors are descended from a template FORM and created in the tabs of a PageControl. The advantage of this is the possibility of compartmentalizing each editor's code into its form class and separating it from the other editor instances. Moreover, the project shows different code methods to access every single editor. EmbeddedFormStack.zip

Is there an MMX feature to comfortably MOVE the current entity (e.g., method) to another/new unit IN ONE STEP (without having to manually cut+paste)?

MMX is a valuable tool and has already provided me with many helpful services. I have only tried to make a non-binding suggestion for improvement. This is a standard procedure when dealing with closed-source software.

That's a rational point. Thanks for the information.

This is a real object: object shpColorHover: TShape Left = 26 Top = 313 Width = 41 Height = 41 Hint = 'Previews the color under the mouse pointer.' Brush.Color = clBtnFace Pen.Color = clSilver Pen.Width = 0 Shape = stRoundSquare end

The benefits are clear, and I agree with them. But introducing additional complexity always increases the cost of a project in terms of handling and maintenance effort.

Interesting approach, nice code. But why introduce unnecessary complexity into something which is intrinsically simple?

Did you read and understand what I wrote?

Is MMX open source? I believe not. I would be happy to help. But I doubt Uwe would allow me. Is this a Kindergarten? I hope not.

"Code is clean if it can be understood easily – by everyone on the team." procedure ResetHoverColor; begin Form1.shpColorHover.Brush.Color := Form1.FHoverColor; end; I doubt that @Uwe (or anyone else) did not understand this code. I rather assume that Uwe called my code "unclean" for specific "emotional" reasons...

Using: Form1.shpColorHover.Brush.Color := Form1.FHoverColor; instead of: shpColorHover.Brush.Color := FHoverColor; is MANDATORY in this context! So this is not a question to "encourage" something which is SYNTACTICALLY NECESSARY! It is strange that you define my code as "UNCLEAN". Has this any religious connotations?

Why not? Are you in a bad mood? Don't you want to make MMX smarter and make doing things with MMX more comfortable?

An example: I have this method entity implemented in Unit1: procedure TForm1.ResetHoverColor; begin shpColorHover.Brush.Color := FHoverColor; end; I CUT this method entity and PASTE it into unit uTransparencyManager (which is part of the same project), and it becomes: uses Unit1; procedure ResetHoverColor; implementation procedure ResetHoverColor; begin shpColorHover.Brush.Color := FHoverColor; end; However, to make it work without errors, I had to MANUALLY add the "Form1." prefixes: procedure ResetHoverColor; begin Form1.shpColorHover.Brush.Color := Form1.FHoverColor; end; 1. Adding these prefixes should be done automatically by MMX! PLUS: The FHoverColor variable is declared in the private section of the Unit1.TForm1 class. To make it usable in the uTransparencyManager unit, I had to MANUALLY move the declaration into the public section of the Unit1.TForm1 class. 2. This too should be automatically done by MMX! Can you please implement this? Thank you!

I have added a Search Filter to the GExperts ToDoList: It is VERY FAST! It searches in all columns of the ToDoList! Usage: Type the search text into the Search Box and then press the Return/Enter key. To reset/cancel the search filter, just delete the search text in the Search Box and then press the Return/Enter key again. This Search Filter feature is very useful when you have many ToDo items in your project. Here is the source (based on r3686) : GX_ToDo.zip Changed the visibility of the FilterTodoList method from public to private: GX_ToDo v2.zip Slightly increased the height of the Search Box to show the whole search text instead of this: : GX_ToDo v3.zip Showing the number of unfiltered and filtered ToDo items: : GX_ToDo v4.zip Improved the height setting for the Search Box: GX_ToDo v5.zip I donate this source code (i.e. my changes to the existing source code) to the GExperts project maintained by Thomas. Added the issue to the source code website: https://sourceforge.net/p/gexperts/feature-requests/150/

It should be: "Use the current editor identifier or the current designer control name as the default search string". This text conforms to the current English grammar rules.

"The Grep search expert now takes the name of the currently selected control on the form designer if it is opened while the form designer is active." I am not sure what you mean by "if it is opened": The Grep search dialog is modal, so no control can be selected while it is opened. And when I choose a control from the IDE Designer and then call the Grep Search dialog, the name of the control is not being inserted in the Grep dialog.

I compiled it in the IDE without problems as RELEASE version. I assume that makes GExperts slightly faster than the DEBUG version?