 | Mike Verhagen on geerlingguy/my-backup-plan: Ho… |
 | Attila Kovacs on docs.embarcadero.com unreachab… |
 | David Blue on MacOS: converting a man page t… |
 | jpluimers on How do I pretty-print JSON in… |
| jpluimers on Delphi 10.2 Tokyo Godzilla ISO… |
Posted by jpluimers on 2018/07/03
Boy, I love this so much: [WayBack] vscode-markdown/CHANGELOG.md at master · neilsustc/vscode-markdown · GitHub
Just a few of the screen videos:
–jeroen
Posted in Development, Lightweight markup language, MarkDown, Software Development | Leave a Comment »
Posted by jpluimers on 2018/07/03
ModelMaker Code Explorer does not allow you to edit the “most recently used” items in that you can use in various places, but luckily these history lists are all in the registry as keys under this base key:
HKEY_CURRENT_USER\Software\ModelMaker\MideX\#.0\Histories
There # is the major version number of ModelMaker Code Explorer (internally named MideX).
Under the base key, you can find these keys:
ExternalSpac not figured out yetInterfaceSupport not figured out yetObject PascalParameters list limited to 60 individual parameters (“Modifier Name: Type = Default”)Parameters list limited to 60 parameter lists in the “Edit Method” wizard.PascalTypeNames list limited to 60 variable typesPascalVarLookup list limited to 60 variables (each of form “Variable: Type”) used in the “Add Explaining Variable” wizard.PropArray array indexes used in the property editorPropDefaultSpec default values of properties in the property editorPropWriteParam write parameters in the property editorRenameLocal not figured out yetResStrExternalFile not figured out yetSurrounds not figured out yetUsedUnits list limited to 30 entries of the uses list editorIf you made a typo anywhere, then just edit or delete these entries.
–jeroen
Posted in Delphi, Development, ModelMaker Code Explorer, Software Development | Leave a Comment »
Posted by jpluimers on 2018/07/03
Directives are commands to the compiler such as
{$D+}or{$WARN xxxx OFF}. Compiler defined conditionals are not “directives”, rather they’re used for conditional directives{$IF Defined(xxxx)}or{$IFDEF xxxx}, where xxxx can beNEXTGEN– Allen Bauer
It’s important to describe features right so everyone understands what you mean.
And note that you should end all your IFDEF with IFEND to stay compatible with the broadest set of Delphi versions possible.
–jeroen
Source: [WayBack] delphi – What is the use of NEXTGEN compiler conditional? – Stack Overflow
PS: Note the comment below by Remy Lebeau:
Note, in Delphi XE3 and later, you might also need to use
{$LEGACYIFEND ON}(http://docwiki.embarcadero.com/RADStudio/en/Legacy_IFEND_(Delphi)) in order to use{$IFEND}correctly, particularly if you have nested{$IF}and{$IF(N)DEF}blocks in your code.
A quick search for “LEGACYIFEND” “Delphi” “XE3” revealed this directive was indeed introduced in Delphi XE3, but not documented until XE4:
--legacy-ifend command-line switchBrian Long documents how to get around the limitation that Remy commented about:
{$ifdef CONDITIONALEXPRESSIONS}
{$if CompilerVersion >= 24.0}
{$LEGACYIFEND ON}
{$ifend}
{$endif}
It is in fact at the top of [WayBack] indy/IdCompilerDefines.inc at master · graemeg/indy · GitHub, which reminds me that there is now a git mirror of Indy at GitHub:
[WayBack] GitHub – graemeg/indy: Indy (Internet Direct) framework. This is an unofficial mirror repository which gets synced every 15 minutes. It contains the full history from the official Indy 10 SVN repository.
–jeroen
Posted in Delphi, Development, Software Development | 2 Comments »
The Wiert Corner - irregular stream of stuff 