Uwe Raabe

The Plus and Minus signs are taken from the UML specification for public and private. The colors are just a visual enhancement. These icons are used all over the place, especially for the Delphi class visibility: They are not related to expanding or collapsing the tree structure (spot the down arrow in front of the Module node in the content tree screenshot above).

What about showing symbols as used in the contents tree? They can be placed somewhere between the Match, Line or Source column. The Yellow Plus symbol signals interface while the Blue Minus stands for implementation. That would waste only a little bit of real estate. Not sure what you refer to with "other scopes". Can you name some?

How is this supposed to work when the number of visible lines is less than the number of lines in the interface/implementation section? A simple marker line (I would suggest something like a plain horizontal line to avoid wasting a full text line) will scroll out of view. I was thinking of different text and/or background colors for interface and implementation, but the styling system doesn't really like custom coloring. It often looks pretty poor in at least one of the standard themes. Perhaps we can adopt some of the syntax highlighter settings? This would honor the fact that the editor can have a different color scheme than the IDE itself.

Your original request has been At the moment you are ranting about button colors, images and image sizes. I am out now.

At least I for myself would not. The report is not bound to the list and takes the complete scan result as output. Its position in the main toolbar instead of the list toolbar even suggests that it is not bound to the list. (I am just realizing that this may not be true for the official version, so I'll add a screenshot of the development version). The list can be filtered with a handful of buttons or with the Show item of its context menu, as well as sorted in two different ways and displayed as List or Report view (in the sense of TListView.ViewStyle). The printed report is unaffected of all of these three settings. If we assume you were right, then the Cycles Report button would not make sense anymore, as it could be achieved with the standard report when the list is filtered for cycles. So, yes, that is logical.

Not a bug - simply as designed!

Have you tried clicking the print button?

Have you filed a QP report?

Yes, that is intended. It lists all modules in the compiled exe (i.e. listed in the map file). The Unit Dependency Analyzer lists only units in the uses clauses. Unless there is a search path to scan those units, you should get the list you are asking for. Well, it does! The ListView to the left contains all used units found in the search paths and all units not found, but mentioned in the uses clauses. You have to enable Show not found units to see that. Can you provide a sample project with the desired result list?

The MMX Module Analyzer actually uses this approach. In the other hand there is the Unit Dependency Analyzer that actually parses the uses clauses to build the dependency tree.

That's why I restrict those paths to the Delphi ones. For any library used in a project there will be a search path entry in the project file. Unfortunately some library vendors or maintainers sacrifice the minimalism of these global search paths for the simplicity of their setup experience.

On the other hand MMX immediately synchronizes the editor view when you select a match with a mouse click.

This looks pretty similar to the MMX Source Indexer function "Search Identifier" available with <Shift>-<Ctrl>-<Alt>-S (assuming appropriate settings).

Did you know that you can edit binary files inside the IDE? Just open a binary file in the IDE and you get a simple HEX editor.

Seems that this is not possible in the moment. Please file a feature request at support@mmx-delphi.de to make this happen in a future release.

As the hint mentions: <Shift>-<Alt>-<Left/Right> Oh, I see. You mean without moving the cursor?

These switches are mentioned in the documentation for the Debug Information setting in the projects Debugging Options http://docwiki.embarcadero.com/RADStudio/Rio/en/Compiling#Debugging_Options and in the documentation to the Delphi compiler options http://docwiki.embarcadero.com/RADStudio/Rio/en/DCC32.EXE,_the_Delphi_Command_Line_Compiler#Generating_Debug_Info

https://andy.jgknet.de/blog/2019/03/ide-fix-pack-6-4-released/

Don't know about GExperts, but theme support is by far the most often requested feature for MMX Code Explorer. I for myself am not a fan of the dark theme and I even could do without themes at all. On the other hand there are obviously a decent number of developers eagerly waiting for it.

I have made the observation that the IDE behaves better when the primary monitor is the one with 100%. You might consider switching your monitor setup.

The option is called Tooltip expression evaluation.

I tried to reproduce it here, but unfortunately without success. BTW, how did you manage to create the mainform twice in the DPR?

You attached the screenshots, but I was referring to the small project.

Can you attach that here?

Is the unit in question explicitly mentioned in the project or is it a unit that is only used indirectly?