MMX 15.0.18 - font bug

[Jacek Laskowski 57]

I'm updating the MMX, setting the cursor on the method, press ctrl+E and...

 

 

The same thing happens when I try to enter the MMX options (menu MMX -> Properties...)

 

 

I've traced that MMX looks for FontName and FontSize in the registry, in the IDE settings in the Theme subnode, if there are no FontName and FontSize, this is an exception. I don't have these settings.

I've written it down and it works, but... something is wrong.

 

Delphi 10.3

Edited June 30, 2020 by Jacek Laskowski

[Uwe Raabe 2059]

Yes, that has already been reported by others and will be fixed with the next update. Meanwhile adding these entries to the registry is the suggested workaround.

[Uwe Raabe 2059]

Version 15.0.20 should fix this issue.

[Jacek Laskowski 57]

6 hours ago, Uwe Raabe said:

Version 15.0.20 should fix this issue.

Now is ok, MMX works, thanks!

 

Just a small remark, the labels do not fit in the frame 😉

 

[Jacek Laskowski 57]

MMX from several versions already works really well, does not slow down, does not suspend the IDE, works quite smoothly. Thanks!

I have only one more problem with it. Unfortunately I can't find the rule, although I've been looking for a month.
Sometimes, very rarely, after editing a method in a class by ctrl+E and after approving the editing window by enter, MMX flips the header of the edited method from the public section just below the name of the class, as shown in the picture below. This problem is from about 3 versions back.

 

[Uwe Raabe 2059]

Strange! Unfortunately without steps to recreate that will be hard to fix.

[Jacek Laskowski 57]

I know, but I can't reproduce.
When something like that happens to me, I'm undo the change and repeating the edit, but the second time is okay.

I'm really trying to understand that and... for now I'm too stupid 🙂

[Guest]

10 minutes ago, Uwe Raabe said:

Strange! Unfortunately without steps to recreate that will be hard to fix.

I don't think it worth your time, but out of thousands of time i double clicked a method to edit or sometime just to look at how beautiful the Edit Method window, once or two i noticed that the visibility been wrongly set to default, but one in thousands chance.

[Jacek Laskowski 57]

@Uwe Raabe

 

I got it! I managed to repeat the effect a few times, I recorded the screencast:

 

https://www.youtube.com/watch?v=PmsQHrr3muU&feature=youtu.be

[Jacek Laskowski 57]

I use the latest version of MMX and the problem described above still occurs sometimes. Today I noticed an additional symptom. I have two methods in class, located next to each other, the same names, but the first one is generic and inactive (marked as a comment). After editing the second one and approving both were moved to the beginning of the class:

 

[Uwe Raabe 2059]

Thanks! There are several issues regarding visibility and they are still being investigated. All reproducible steps are valuable.

[Jacek Laskowski 57]

Perhaps the line width is important for this problem. I had 140, now I set 80 and for now the situation has not repeated, I will test for some time, although I want 140 eventually.

 

[Jacek Laskowski 57]

Unfortunately, after editing many methods, the problem appeared again, so this value has no effect 😞

[Uwe Raabe 2059]

On 7/1/2020 at 11:15 AM, Jacek Laskowski said:

Sometimes, very rarely, after editing a method in a class by ctrl+E and after approving the editing window by enter, MMX flips the header of the edited method from the public section just below the name of the class, as shown in the picture below.

I guess I finally found the cause: When you edit a property inside an interface the available visibility values are limited to default. Now edit a property in a class and the visibility is also default. The reason is that the current visibility is set before the allowed values are set.

 

A fix will be available shortly.

 

On 10/16/2020 at 12:21 PM, Jacek Laskowski said:

I have two methods in class, located next to each other, the same names, but the first one is generic and inactive (marked as a comment). After editing the second one and approving both were moved to the beginning of the class:

Can you check if you have Pick up any style comments as documentation checked in your MMX Documentation settings? That would take the commented method declaration as a comment belonging to the one below. Consequently the comment is moved together with the method declaration.

[Jacek Laskowski 57]

21 hours ago, Uwe Raabe said:

I guess I finally found the cause: When you edit a property inside an interface the available visibility values are limited to default. Now edit a property in a class and the visibility is also default. The reason is that the current visibility is set before the allowed values are set.

 

I don't think I've written anywhere, but with me practically 99% of classes implement the interface, so there is always an interface behind the class and problems with moving methods to the beginning of the class were ALWAYS present in classes implementing the interface.

 

21 hours ago, Uwe Raabe said:

I guess I finally found the cause: When you edit a property inside an interface the available visibility values are limited to default. Now edit a property in a class and the visibility is also default. The reason is that the current visibility is set before the allowed values are set.

 

A fix will be available shortly.

 

Can you check if you have Pick up any style comments as documentation checked in your MMX Documentation settings? That would take the commented method declaration as a comment belonging to the one below. Consequently the comment is moved together with the method declaration. 

Yes:

 

 

I am very happy that I will enter 2021 without this frustrating affliction

 

Happy New Year!