DelphiDabbler's Blog

This blog post is based on a pre-release version of the RAD Studio software and it has been written with specific permission by Embarcadero. No feature is committed until the product GA release. It seems I'm getting very excited about multi-line strings of late. My previous post was about multi-line string literals for Delphi  and this time I'm talking about the new multi-line string property editor being slated for the RAD Studio 12 IDE. For more years than I care to remember, I've been frustrated by the inability to enter multi-line strings in the Delphi IDE object inspector. That meant having to resort to code to initialise some multi-line labels. So frustrated was I that I wrote a little property editor of my own ( stringpe ), way back in 2004. It's still around and on GitHub. Here's what it (sometimes) looks like: Yeah, I know this is Vista - I used an old screenshot Sometimes? Well it looked like that until it got installed on DPI aware Delphis, and then it sh...

This blog post is based on a pre-release version of the RAD Studio software and it has been written with specific permission by Embarcadero. No feature is committed until the product GA release. The upcoming new release of RAD Studio 12 Yukon is a major update that's got a new Delphi language features that I've been wanting for years, or perhaps even decades since I first discovered heredocs in PHP. Yep, we're going to get multi-line string literals. This excites me just as much as the earlier introduction of inline var statements, which was a lot! I write a lot of multiline string constants in my code like this: const   S0 = ' Lorem ipsum dolor sit amet, consectetur adipiscing elit.' +         sLineBreak  +        '   Vestibulum eleifend elit id dapibus pulvinar.' +        sLineBreak +        'Suspendisse tincidunt, diam vel dapibus aliquam.'; Miss out one of the closing quotes or ...

Just released  CodeSnip  v4.21.2, which is a minor bug fix release. Updating is strongly recommended but not essential. Full details of this release are discussed in detail over on the  CodeSnip blog . ⏬ Download the new release from the  v4.21.2 release page  on GitHub.

I was casting around looking for something new to write in Delphi 11 when it struck me that there hasn't been an easy way to view the SWAG archive since I took down the viewer from my website and, well, archived the archive! Now I can't imagine there's going to be much demand to view this rather ancient archive of Delphi & Turbo Pascal code, so I'm not spending too much time on this. So, here's v0.1.0 of SWAGView for your delight and delectation: SWAGView v0.1.0 running on Windows 11 👉 You can grab a copy from the program's  releases page . 👉 There's also some brief  online help  and a  web page . 👉 The source code is on GitHub in the  ddabapps/swagview  repo. ⚠️ Be aware that SWAGView doesn't come with a bundled copy of SWAG - you need to download that from the SWAG GitHub repo and then install it from within the program. Full instructions here .

It's the 1st of July, so it's time for another update to my System Information Unit. Once again TPJOSInfo has been updated to detect the various Windows 10 & 11 builds and revisions released during the previous month, June 2023. Grab this release from the project's GitHub  releases page .

Release 0.3.0 of the app formerly known as Unit2NS was released yesterday. Unit2NS is/was a little application that, given a unit name, finds all the unit scopes that contain a unit of that name. For example, on Delphi 11.3 Enterprise there's a unit named Json in the following unit scopes: Data.Bind FireDAC.Comp.BatchMove REST System The thing is, when I released v0.1.0, I'd referred to these unit scope names and " namespaces ". As a commenter pointed out, this was wrong. Said commenter was right that I was wrong. It was quite simple to change the text in the UI and docs, but  the trouble was that the "NS" in Unit2NS stood for "namespace", and it's been bugging me. So I decided to change the name, I could have turned round "NS" to "SN" (for scope name), but that seemed like a cop out, so I've gone the whole hog and changed the name to ... 🎺🎺🎺... DUSE: D elphi U nit S cope E xpander. Corny, maybe, but I tried lots of...

Yesterday I released gbg v0.2.0, followed a few hours later by v0.3.0. Busy day! v0.2.0 When I announced the first release of gbg  someone suggested an option to generate ASCII characters instead of random bytes. That's what I added in v0.2.0. There were two options that could be added to the command line: -a to generate printable ASCII characters with codes 32 to 126. -A  to generate all ASCII characters with codes 0 to 127. Here's the new commands being used with some sample output: v0.3.0 I like my command line programs to be able to display their version numbers, so I added the -V option to do just that. The Usage screen also got updated: Any More Suggestions? Any more requests? Either leave a comment on open an issue on GitHub. Downloads You can get the latest version from the GitHub releases page . I'd skip v0.2.0 and go straight to v0.3.0, but it's up to you.