DelphiDabbler's Blog

The second thing I did after the release of Delphi 13,  after updating my website , was to enable the unit-scope look-up program, DUSE , to create a new mapping of all the units used by Delphi 13 to their unit scopes. This is easy to do: Having clicked  OK  then Save And Close  DUSE will read the names of all library units installed with Delphi 13. A new "mapping" named Delphi 13 Florence is created and you can select it whenever you're using Delphi 13: You can switch to any other mappings you may have created at any time: you can see the ones I've made in the above image. ➣ Download DUSE v0.3.2 from GitHub For help using DUSE, see the mini-help section of the program's read-me file. By the way, the code in DUSE that finds a given Delphi installation is very similar to that discussed in my article  How to programatically detect installed versions of Delphi . And finally, I used Delphi 13 to compile this new version of DUSE.

Now that Delphi 13 Florence is out, I've updated delphidabbler.com to bring relevant pages up to date. The changes are: The Delphi Version Numbers page has been updated with relevant information about Delphi 13. The most notable change is that the product version has now been brought into line with the compiler version, internal version and defined symbol. This means the product version has jumped from Delphi 12's version 29 to 37. The Delphi Version Features page has had numerous additions relating to features introduced in Delphi 13. If you know of any more please tell me by raising a new issue on GitHub (no C++ stuff though!). Article #27 (How to programatically detect installed versions of Delphi)  has been updated to include Delphi 13 in the list Delphi versions than can be detected. The notable change is that, due to the change in version numbering noted above, the registry key for Delphi 13 has changed similarly. For e.g. Delphi 12's key is  \Software\Embarcader...