Uwe Raabe

In that (probably unrealistic) case I prefer a method taking the record as the first var parameter (which is pretty much what the record method does internally, but I like the elegance of record methods and helpers).

Please report that bug to QP and add your example program.

That would work for classes, but fails for records. Introducing a record variable will give you a copy of the array element for your changes. The original array element will stay unchanged. A valid alternative would be a record method like SetBlaBlub(5, 10) which directly manipulates the underlying record. This might even benefit the readability.

Of course: File bugs and feature requests.

As I said: it works on my system, so I assume it is heavily dependent on the current system configuration. If someone would collect a couple of cases where it works and where not and compare the configurations that may lead to the source code parts that are still buggy.

Then you can surely tell us the QP entry for this, can't you? In that case please make sure to describe in detail the system setup you are using, so they are able to reproduce that bug. As for me, I simply can't on my system.

So then you probably have to live with the scaling bugs until 10.4, where High-DPI support for the IDE is on the roadmap. We can only give hints and tips here - we cannot fix the IDE for you. On the other hand does 10.3 work perfectly here on a 4k monitor set to 200%. The difference to your setup may be that I have three monitors where monitor 1 and 2 are set to 100% and only monitor 3 to 200%. As the default DPI for Windows is taken from monitor 1 and thus 100%, this may lead to the correct display even for 200% I can see on my system. Following this logic, I repeat my suggestion to set your DPI setting to 100% - for your system DPI - on an additional monitor. Then you can have your HiRes monitor set to a higher DPI and hopefully don't see that scaling bugs anymore. Perhaps you can try it.

Agreed! Problem is that reality sucks.

Set your display to 100%

The QuickEdit thing is a know bug: QuickEdit still use 10.2 registry path I can also see the RegQueryValue calls and more: even for every Delphi version installed. Not sure what purpose that has, but the same behavior is also seen with 10.2.3 Tokyo (including the Studio\20.0 entries).

That may give the background for this decision: the names for both forums should match, so people can be recognized.

Interestingly, that is quite similar to one of the reasons why "with" was invented in the first place: when accessing the record memory is costly. From Pascal User Manual and Report (emphasizes by me):

Drag-Select all the text you want to quote and click on the little "Quote" hint appearing when your selection is finished. That is also a good way to quote only part of a post and I miss that feature already in the German forum.

I am quite confident that Stephanes problem is caused by installing Tokyo after Rio messing up some parts of the registry.

No problem. See attached file. BorlandIDE.reg

Fine! There should be several subkeys for each Delphi version. Here is how it looks on my system: Please make sure that the entries in InprocServer32 match the corresponding values found in the 26.0.0.0 subkey.

So can you find that CLSID {FDAED0FF-DD92-42C8-BB2C-F1759632FDB8} anywhere else if not under HKEY_CLASSES_ROOT\Wow6432Node\CLSID?

Well, that is strange! The {FDAED0FF-DD92-42C8-BB2C-F1759632FDB8} is the CLSID value found under HKEY_CLASSES_ROOT\Borland.Studio.ToolsAPI.BorlandIDE. Do you have a different value there? Please check the RootDir entry in HKEY_CURRENT_USER\Software\Embarcadero\BDS\20.0, too. I get the feeling that your installation is completely borked.

Can you please check the registry entries under HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{FDAED0FF-DD92-42C8-BB2C-F1759632FDB8}\InprocServer32? Especially the version values for Assembly and RuntimeVersion?

First I would like to use the same settings as in your system. Can you export the MMX registry key for me? The key base is HKEY_CURRENT_USER\Software\Raabe Software\MMX\13.0 (I know about the 13.0 as an open issue in the beta). Then, if I still cannot reproduce it here, I will try to compile a special version with some logging. Unfortunately, as long as I have no clue about what is happening here, that can only be some shots in the dark. I am also a bit baffled that no one else reports a similar behavior. Can you rule out any other non-standard addin or a non-standard Delphi installation?

I am sorry, but even with your source unit I am not able to reproduce it here.

I hope that is also not the case when background compilation is enabled.

This should give you some hints: Checking the SQL Command Text The rest of that article might be helpful, too.

I was wrong. It is a problem with 10.3 Rio only. The IDE doesn't work well with these settings and MMX seems to be the victim here. Not sure what I can do about that.

You can edit the registry entry of your Delphi version to specify another version of MMX. Look for MidexExpert in the Experts subkey.