Leaderboard

I have just uploaded the third beta version of GExperts 1.3.12 for Delphi 10.3 Rio. NOTE: This is still a BETA! Also note that this is for Delphi 10.3 Rio only. It won’t work with any other versions. This beta release contains a (ugly) work around for the redraw bug in the Goto-Dialog enhancement when theming is enabled. Also, a few other bugs have been fixed. I am not aware of any more bugs that are specific to this version of GExperts or Delphi 10.3 Rio. If you still find some, please report them on SourceForge. Also note, that I have still not tested the installer as I don’t have a fresh Delphi 10.3 installation for that test. https://blog.dummzeuch.de/2018/12/08/gexperts-1-3-12-beta-3-for-delphi-10-3-rio-available/

The DDevExtensions 2.85 and the DFMCheck 1.6 are now available for Delphi 10.3 Rio. DDevExtensions Changelog Added: Support for Delphi 10.3 Rio Added: Use Unit dialog option “Every unit on a single line” Improved: UnitSelector Dialog in Delphi 2009 opens much faster Fixed: Structure-View search dropdown had a max height of 2 items Downloads

A new version is available V1.3.8.94 Visit our Homepage and download the Trialversion: https://fbm.gksoft.ch

@Emil Mustea You could be that clever however the real runtime overhead of the spring smart pointer is so small that any such tricks are not necessary imo and rather lead to defects because of implicit variables as shown earlier. @pyscripter YMMV but when I compile with release config the results are within 2% difference. Depending on order and CPU caching in that micro-benchmark they are even equal.

Out of the three options, the first two are fine, the last one is a terrible idea. Don't do it. You just create loads of extra work for no benefit.

Pointless to ask ShellExecute to create a cmd process to in turn create another process. Create the other process directly. This is the source of all your problems.

I just found out what is wrong with my Delphi IDE Explorer in Delphi 10.3 Rio. The symptom is that the Follow Focus option and the Select Active button no longer work in some forms, in particular in the options dialog (Tools -> Options / Run -> Parameters / Project -> Options). The reason is that this dialog now uses the Screen.OnActiveControlChange event itself ... https://blog.dummzeuch.de/2018/12/09/delphi-ide-explorer-is-broken-in-delphi-10-3-rio/

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.

To summarize: Who wants maximum performance like "classic" use it like this var obj := Shared.Make(TTestObj.Create)(); "obj" is object and will be free it at the end of the procedure; otherwise, use it: var obj := Shared.Make(TTestObj.Create); "obj" is interface and will be free it at the end of the block and every access has a small penalty of an anonymous method call.

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.

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):

I believe this is the most common problem in our line of work: not realizing what really is the problem. 😄

Why not directly make it `using` and replace the `begin` `end` with `{ }` ? :)