Uwe Raabe

MMX has a feature Find next/previous occurrence: Place the cursor somewhere into the specific identifier and press Shift+Alt+Right/Left. You can combine this with the IDE Search Enhancement feature, which adds all identifiers of the current unit to the Ctrl+F search box.

i get the same error message with GetIt, but that is not under my contol. The standalone installer should do, but leaves GetIt unaffected.

Yes, albeit not really straight forward. Also the Win32 platform has to be enabled for the project, which will always be the case when you create a new project even inside the 64-bit IDE. The trick is to create a Build Group and include Win32 as target platform in it.

Even a TMainMenu is drawn according to the current VCL style. A simple test confirms that. So, what class type has the form and is that class registered to the ThemingServices?

Same here.

Since the announcement in the See What's Coming in RAD Studio 13 Florence webinar last Wednesday, where MMX Code Explorer was promoted as a replacement for the removed refactoring in Delphi, there have been more than 1200 downloads. With this number it is no surprise when some people encounter problems installing or using it. This is a short list of things that happened and hints how to avoid these problems. I expect this list to be extended over the next couple of days. Some people get a virus warning when downloading the zip file. This is the MD5 hash of MMX_Setup_16_0_8_59.zip to verify that your copy is the original one: c24ef7eb0d073a97541bd8e11494cdad Always use the recommended Install for me only option! The admin mode Install for all users is heavily broken and can lead to problems when uninstalling. If multiple users are sharing the same Delphi installation each one has to install its own copy of MMX Code Explorer. Don't set your Startup Desktop to <none>. While this worked in previous versions, the new V16 doesn't like it. The issue will be investigated.

I was just about asking the same

As I am getting just the opposite, there must be some difference with our tests.

Indeed, 24 would have been expected, bat wasn't 24 some sort of secret Illuminati number? And 24 + 13 = 37 😲

I made some tests. In all cases Hints are enabled. Targets: Win32/Win64 DEBUG, Assertions on : no hint DEBUG, Assertions off : no hint RELEASE, Assertions on : hint RELEASE, Assertions off : No hint The behavior with RELEASE seems fine, but why is it different with DEBUG?

I am also a Ctrl+D guy, but usually only for the current selection - and, yes, I will have also have to find a replacement, at least temporarily. Currently I am inclined to use the GExperts Formatter, as it is based on the old DelForExp by Egbert van Nes, which I had been used to quite a long time in the past.

The DLLs are signed and MMX_Setup.exe is also signed. What else can I do? 😭

Can you say what refactoring you are actually using?

Yep, that sounds like a valid scenario for triggering the problem. I also cannot explain why the code is as it is - I just kept it as it was when I took over. Do you have a suggestion which window handle I could use as the owner window?

As part of the Modelling package it has been removed completely, too.