Uwe Raabe

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?

To be fair, you actually posted two questions. Where the first one has that simple answer, the second one is somewhat difficult to target for us.

Probably it is not so simple: So depending on whether the optimization is part of the Compiler Speed Pack it might as well be incorporated into a Delphi compiled EXE.

ditto

There still is CodeSite Studio: https://raize.com/codesite/ Definitely worth it!

Perhaps I am a bit too optimistic, but I do have hope that some library providers will adhere to a reasonable standard whenever it will be established. If this Package Manager forces some requirements on any package/library to be supported, that might help to canalize the chaos diversity currently out there.

Only virtually 🚯