CodeSnip

CodeSnip v4.27.0 released with support for Delphi 13

noreply@blogger.com (Delphidabbler) — Fri, 12 Sep 2025 14:53:00 +0000

➣ For info see this post on the DelphiDabbler blog.

CodeSnip v4.26.0 released

noreply@blogger.com (Delphidabbler) — Fri, 02 May 2025 19:55:00 +0000

➣ For info see this post on the DelphiDabbler blog.

Freezing this blog

noreply@blogger.com (Delphidabbler) — Sun, 20 Apr 2025 07:07:00 +0000

It's becoming a bit of a pain maintaining this blog just for CodeSnip and the Code Snippets Collection while also running the more general DelphiDabbler blog.

Given this blog has a much smaller readership than the DelphiDabbler blog I've been cross posting CodeSnip news on that blog for quite some time now.

So, in future, I'm going to post CodeSnip related news to the other blog and will cease using this one. For a time I will probably do a stub post here linking to any relevant new posts on the main blog. Eventually I'll freeze this blog completely.

This blog will remain up, partly because CodeSnip has a help menu item that links to it. That may change in future CodeSnip releases.

Should anyone have just cause or impediment as to why I really shouldn't do this, please tell me in the comments.

CodeSnip v4.25.0 released (including a fix for a fix of a fix)

noreply@blogger.com (Delphidabbler) — Sat, 19 Apr 2025 10:51:00 +0000

It's nice to be able to release a version of CodeSnip containing new features instead of bug fixes. Except that this release also includes bug fixes, including episode 3 of the hibernation bug fix saga.

So what's new? Not a lot except for some new snippet export options:

For the longest time you've been able to get a copy on the clipboard all the information about a snippet that gets displayed in the detail pane. Now you can finally save the information directly to a file. The only option is Rich Text Format just now, but more formats may make an appearance later.
When exporting Pascal units and annotated snippet source code various formats can be chosen. HTML 5 format export files has now joined the list or plain text, Pascal, RTF and XHTML

Some annoying, but relatively trivial bugs have also been fixed. Go see the change log if you're curious.

But I can't close this post without mentioning the hibernation bug fix saga.

A third fix of the bug where CodeSnip sometimes crashes after hibernation has been rolled into this release. Now this doesn't mean that the previous fixes didn't work - they did. But, as I mentioned in my posts about releases v4.24.1 and v4.24.2, those fixes relied on dirty hacks of which I was ashamed.

So, along comes Oliver (@SirRufo on GitHub) with a patch that fixes the bug without all the hacks. I've gratefully included this patch in this release. No more shame for me! Thanks Oliver.

⮞ Get release v4.25.0 from GitHub

Here's CodeSnip displaying the new Save Snippet Information dialogue box:

And here it is again, showing the new HTML 5 option when saving annotated source code, and showing a preview of a weirdly named, but valid, function that I use to test the rendering of Unicode identifiers:

Persistent bug in CodeSnip re-squashed, properly this time?

noreply@blogger.com (Delphidabbler) — Mon, 14 Apr 2025 20:04:00 +0000

It had to happen didn't it? Not long after my post about yesterday's bug fix release of CodeSnip, Oliver reached out to point out a potential problem with the way I'd implemented it. See the linked post and comments if you're interested in the details.

Suffice to say that the problem was sufficient for me to hunt for an alternative solution. Having found one I've rushed out hotfix v4.24.2 to patch yesterday's release (v4.24.1) and make it more robust.

Whether or not you downloaded yesterday's you really should update CodeSnip to the hotfix release.

⮞ Get hotfix release v4.24.2 from GitHub.

The fix involves a dirty hack of which I'm deeply ashamed, but it works. To be up-front about how horrible this hack is I've liberally sprinkled comments that include the text "!! HACK" in the code. Also, any new methods and fields that implement the hack have names prefixed with _HACK_.

I need to get this patch out, so don't have time to explain the solution here. See yesterday's post for a statement of the problem and an overview of the fix in v4.24.1. If you're interested in today's fix the following two diffs should help:

Diff between v4.24.0 and v4.24.2 - shows the fix relative to the last release containing the bug, without any of the reverted changes from v4.24.1 cluttering things up. Ignore all the documentation, version and help file changes.
Diff between yesterdays fix, v4.24.1 and today's fix, v4.21.2 - shows what changed between the two fixes. Ignore the documentation and version file changes.

Should you want an explanation of the changes, please leave a comment and I'll do my best to describe the problem and solution.

Persistent bug in CodeSnip squashed at long last [I hope]

noreply@blogger.com (Delphidabbler) — Sun, 13 Apr 2025 19:16:00 +0000

What a red letter day. 🎆🎇🌠

For several years a nasty access violation bug has been lurking inside CodeSnip. It crashed the program when the computer was resumed from hibernation, but only sometimes. Because the bug was intermittent and required numerous hibernation / resume cycles to be run before it finally cropped up it defied diagnosis for a long, long time.

Until now. Or up until someone finds my fix doesn't work for them!

The bug fix release is v4.24.1 - get it from GitHub.

Read on if you're interested what the problem turned out to be.

CodeSnip uses a custom drawn tree view control to display the available snippets, grouped under headings. A custom TTreeNode class is used that has an extra property that references an object instance that provides extra information about the item been displayed. This information is used by the custom drawing code.

The problem is that, occasionally, when waking from hibernation, Windows destroys and recreates the window handle of the tree view. The Delphi VCL detects this and stores the TTreeNode properties in a memory stream when the tree view window is destroyed and then re-reads the node properties when the window is recreated. This means that the standard TTreeNode properties are persisted, but not the additional property I added to the the custom TTreeNode class. Consequently where CodeSnip expects to find the object reference it left there it actually finds nil. And the first time the object is read is when things go all pear shaped. Hello access violation!

The window creation and destruction code is not easily available get into. I didn't (and won't) hack TTreeView in the VCL code. However I did try to hack TTreeView by other means. I don't like such hacks and, worse, my hack didn't work reliably!

So, in the end I intercepted the WM_POWERBROADCAST message that Windows sends when there's a change of power state. The message gets sent numerous times: it has a parameter that says what exactly is happening. When hibernation is detected the tree view state is saved. When resume is detected we let Windows do its worst and then jump in and rebuild the tree view properly and finally restore its state. Actually, the message that I needed gets sent twice, once before and once after the tree view gets recreated, so the rebuilding also gets done twice. There's no great overhead of doing this, so that's not worth working around.

This is still a bit of a kludge, and I'm not 100% sure it will work on all versions of Windows: the WM_POWERBROADCAST docs aren't clear.

A better solution would be to re-implement all the tree view handling code to avoid using a custom TTreeNode descendant, but the code is deeply entwined and it's a big job. Maybe one day.

Anyhow, please do try this update. I'm sure you'll report it if the fix doesn't work for you!

View diff of the fix here.

Code Snippets Collection v2.2.3 released

noreply@blogger.com (Delphidabbler) — Thu, 03 Apr 2025 19:05:00 +0000

Version 2.2.3 of my Pascal code snippets collection has just been released.

Unlike the previous bumper release, this one adds compilation results with Delphi 12 for all snippets that hadn't been tested with that compiler, which was most of them.

It also fixes a couple of bugs, so I recommend updating to this release.

For details of the bug fixes, see the change log.

If you are using CodeSnip v4.16 or later then you can update your snippets collection by using the Database | Install or Update DelphiDabbler Snippets Database menu option and following the instructions in the resulting wizard.

➤ You can find the new release on GitHub.

Code Snippets Collection v2.2.2 released

noreply@blogger.com (Delphidabbler) — Sun, 19 Jan 2025 10:39:00 +0000

Version 2.2.2 of my Pascal code snippets collection has just been released.

Don't let the patch version number bump fool you. There are a lot of new snippets in this release. In fact, it's the first time in years that so many new snippets have been added.

Nearly all the new snippets are mathematical. A few snippets were added to the Arrays category, but most got grouped into the Mathematics category. Some snippets relate to number theory while others work with numbers in different bases. However the majority relate to statistics, including functions to calculate Arithmetic, Geometric, Harmonic, Logarithmic and Power means.

I'm not going to list them all here, that would be tedious. See the change log for a full list of the new functions & other changes.

A couple of existing snippets have been modified, in one case to fix a bug.

Unit tests have been added for every new snippet and for one existing snippet.

All the new snippets compile without problem with Delphi XE and 12.2. I expect there will be no problems with Delphi release between those two. Several snippets use generics, so won't compile with the ever-popular Delphi 7.

➤ You can find the new release on GitHub.

CodeSnip 4 displaying LSE, one of the may new snippets in v2.2.2

ASIDE: The reason that this big update only gets a patch release is down to semantic versioning: the release adds nothing to the collection that can't be read by any program that can read v2.2.0 of the collection.

CodeSnip v4.24.0 released

noreply@blogger.com (Delphidabbler) — Wed, 23 Oct 2024 21:07:00 +0000

CodeSnip v4.24.0 has just been released.

There's no main feature in this release. It's a bit of a mish-mash of numerous minor bug fixes and tweaks that have been implemented since the previous release.

I'm not going into detail about the numerous small changes here: check out the change log if you're interested.

Do you need this release? Well, its not going to knock your socks off, but there are a couple of bug fixes, so installing it wouldn't do any harm.

✅ Get v4.24.0 from its GitHub releases page.

Released v2.2.0 of the Code Snippets Collection

noreply@blogger.com (Delphidabbler) — Tue, 15 Oct 2024 17:00:00 +0000

Finally, months after I meant to, I've released v2.2.0 of the DelphiDabbler Code Snippets Collection.

This is a collection of snippets that can be loaded into CodeSnip program. To do so, download csdb-v2.2.0-data.zip from the GitHub release page. Unzip it somewhere on your system then run CodeSnip. Select the Install or Update DelphiDabbler Snippets Database menu option and follow the wizard.

If you would like to run tests on some of the snippets then download csdb-v2.2.0-tests.zip from the same place. Read the included read-me file for info about how to run the tests.

Finally there's comprehensive documentation in csdb-v2.2.0-docs.zip.

In this release the main feature is the addition of a few routines to the Mathematics category. Specifically there are three IEEE conformant Pown routines and a couple of heavily overloaded summing functions. For details of these and other changes see the change log.

CodeSnip and Delphi 12.1

noreply@blogger.com (Delphidabbler) — Thu, 04 Apr 2024 15:24:00 +0000

Now that Delphi 12.1 has been released the question of whether a new release of CodeSnip is needed to work with it.

The answer is no, it's not. That's because Delphi 12.1 can't be installed alongside Delphi 12.0 - it's either/or. Furthermore, Delphi 12.1 appears to CodeSnip just like Delphi 12.0, so CodeSnip will happily use it to test compile snippets if it is installed.

CodeSnip v4.23.0 Released

noreply@blogger.com (Delphidabbler) — Tue, 02 Apr 2024 15:43:00 +0000

Today I released an update to CodeSnip that makes two little changes:

The marketing names have been removed from later Delphi versions (e.g. Athens & Rio) to save space in the UI if you have several versions of Delphi registered. So now instead of seeing Delphi 12 Athens you will see Delphi 12.x, for example.
The built in REML markup language that can be used to format snippet descriptions and "Extra" text, now supports the ' character entity that gets replaced by a single quote when rendered.

For the complete change log see here.

Compiler name changes in v4.23.0

New REML character entity in v4.23.0

CodeSnip v4.22.0 released

noreply@blogger.com (Delphidabbler) — Wed, 08 Nov 2023 09:35:00 +0000

Yesterday, Delphi 12 was released as part of RAD Studio 12 "Athens".

Today there's an update to CodeSnip that gives the option of using the new Delphi 12 to test compile your code snippets.

It's really simple to configure CodeSnip to use Delphi 12. The first time you start CodeSnip after installing Delphi 12 a dialogue box will pop up and ask if you want to use the compiler alongside any other versions you may have:

That will happen only if you haven't turned off the auto-register compiler option. If that's the case you'll need to use the Tools | Configure Compilers menu option to set it up yourself. The Detect Delphi Compilers button in the Configure Compilers dialogue box will do the trick:

The only other user-facing change is that the list of compilers in the Configure Compilers and Find Compilers dialogue boxes is now sorted with the newest Delphi versions first instead of them being hidden down the bottom an increasingly long list.

There's one source code change for the purists: you'll no longer find a single with statement in the CodeSnip source. 👏👏👏

As usual, there are separate standard and portable builds available. Both editions, along with the source code, can found on the CodeSnip project's releases page on GitHub.

For more info about CodeSnip see its web page and GitHub read-me file.

Released CodeSnip v4.21.2 (minor bug fixes)

noreply@blogger.com (Delphidabbler) — Fri, 14 Jul 2023 07:50:00 +0000

CodeSnip v4.21.2 has been released today, 14th July 2023.

This is a patch release that fixes a few minor bugs:

Fixed some broken and "unsafe" (http) links in the about box.
Fixed error in version information.
Fixed potential XSS vulnerability in JQuery code used in the program's easter egg .
Updated and clarified license & some other docs.

Do you need this release? Depends on how much you're bothered about the above errors. Up to you.

⏬Get the new release from the v4.21.2 release page on GitHub.

Released CodeSnip v4.21.1 (bug fix)

noreply@blogger.com (Delphidabbler) — Sun, 09 Apr 2023 15:35:00 +0000

Back in December 2022 I was quite pleased with myself for releasing the v4.21.0 update to CodeSnip.

The main feature that was added in v4.21.0 work fine - automatically detecting un-registered Delphi compilers at start up - worked fine. But, oh dear, the more obscure new feature that lets you use lists in snippet descriptions was a bit of a disaster.

The main implementation of lists was a bit flaky, but the main problem is that I forgot to add the implementation of lists in snippets reports and in source code comments in generated units. This pretty much trashed the reports and comments.

It's taken a lot of coding to fix these bugs, hence the 4 month delay before this bug fix materialised. But I think I've managed it, although whether the new feature was worth the effort is debatable.

⏬Get the new release from the v4.21.1 release page on GitHub.

Here's what a snippet looks like in the UI when it's description contains an unordered list:

Here's how the same snippet appears in a generated unit or in annotated source code:

And in RTF (top) and plain text (bottom) reports look like this:

These reports were generated by doing Edit | Copy Information and pasting first into WordPad and then into Notepad++.

There was another bug that affected reports that got fixed. This one went back before v4.21.0 and it related to the table of compiler results having misaligned comments. Anyhow, they're now aligned once again in both text and RTF reports, as can be seen below:

There were several other bugs squashed. For details see the change log.

Released CodeSnip v4.21.0

noreply@blogger.com (Delphidabbler) — Fri, 16 Dec 2022 17:50:00 +0000

To close off the year, here's a new release of CodeSnip that adds a couple of new features that have been in the pipeline for quite a while.

The first is one I've been working on ever since a user missed out on getting Delphi 11.x Alexandria support when I added it. He expected CodeSnip to just use it when test compiling snippets. It didn't do that. I think his expectation was valid, so I decided to make CodeSnip a bit cleverer!

Until now, when support for a new Delphi version was added to CodeSnip you would have to remember to tell it you wanted to use the new compiler, if you had it installed.

Now, when CodeSnip starts it checks if there are any versions of Delphi on your system that are not registered with CodeSnip for use when test compiling snippets. If it finds any it offers to register them for you.

This feature only works for any version of Delphi that CodeSnip knows about, which for the moment is all of them from Delphi 2 to Delphi 11.x Alexandria. This doesn't work for Free Pascal.

Here's what you'll see when CodeSnip starts if it discovers compilers that it hasn't got access to:

If you tick the check box next to one or more compilers and click OK CodeSnip will register them and you'll get a confirmation like this:

And if you really don't want CodeSnip to do this? Well, if it displays the top dialogue box above, tick Don't show this again to shut it up forever. If you change your mind you can turn the feature on or off again globally, or on a per compiler basis using the Configure Compilers dialogue box:

BTW, if you're curious how to go about detecting which Delphis are installed take a look at this article.

The second new feature will only really impact users who like to fancy-up their snippet descriptions with a bit of markup. CodeSnip uses a very small HTML like language called REML to format desciptions. Its been about 12 years since REML got any love, so I've finally extended it a little. At long last you can now use lists. The tags are the same as HTML: <ol>, <ul> and <li>. REML is a bit stricter than HTML - it will complain if you get the syntax wrong!

A whole bunch of new character entities were added (too many to list here). For full details of what's available read the REML documentation.

In the following some REML code is being entered on the Extra Information tab of the snippets editor. You can also use REML in the description field on the Code tab.

Here's what the markup looks like when rendered:

What else? Not much. There are a couple of minor changes to the open source EULA and the docs & help file have been updated re the above changes. See the change log for the gory details.

As usual the CodeSnip comes in standard and portable editions.

You can get both editions, along with the source code, from the CodeSnip project's releases page on GitHub.

This release is available from SourceForge, but I'm probably going to stop publishing releases there soon because hardly anyone downloads the program from SourceForge any more.

Never make new year's resolutions - dumping CodeSnip Belvedere

noreply@blogger.com (Delphidabbler) — Sat, 03 Dec 2022 13:33:00 +0000

Over 9 years I've had three attempts at creating CodeSnip 5. All have been very ambitious.

The latest was CodeSnip Belvedere, rashly announced on new year's day this year. Now I never normally make new year's resolutions, and I should have stuck with that tradition! Of course Belvedere foundered - it was way too ambitious. Again. I was overwhelmed right from the start. Just look at the repo where there have been bugger all commits.

So here's a new announcement I can stick by: Belvedere is dead, abandoned, gone.

The idea to rebuild CodeSnip from the ground up was an attractive proposition, but it was way too much work. Right from the start I seemed to have an inkling I might have bitten off more than I could chew, because I even queried the wisdom of the new year's resolution in the announcement itself!

And that's what all the failed attempts to create the next release have in common: the plans for the new version were always too ambitious.

Maybe I've learned my lesson! Watch out for plan B (or C, or D, or ...). I have another cunning plan. But this time I'm going to think it through a bit more before announcing it. Maybe not on new year's day 2023 though, eh?

Released CodeSnip v4.20.2

noreply@blogger.com (Delphidabbler) — Fri, 04 Nov 2022 17:54:00 +0000

Just released CodeSnip 4.20.2 which is a bug fix update to CodeSnip 4.20.1.

It fixes a bug in the main menu of the UI. To replicate the bug:

Drop down a main menu item.
Select an item on the dropped down menu using the cursor keys. Do not press enter.
Press F1. This raises an exception in CodeSnip prior to v4.20.2

This release also update Windows OS Version detection to correctly detect Version 22H2 of both Windows 10 & 11.

Because of the bug fix, I do suggest updating.

As usual you can download the program from GitHub or from SourceForge:

Source is available to download from both SourceForge or GitHub. Alternatively you can fork away in the GitHub repo - the master branch always contains the source of the latest release, while the develop branch has the latest development source and may not be stable.

Released CodeSnip v4.20.1

noreply@blogger.com (Delphidabbler) — Fri, 01 Jul 2022 16:10:00 +0000

Just released CodeSnip 4.20.1 which is a bug fix update to CodeSnip 4.20.0.

It fixes a problem in the library that detects operating system version information and makes a few minor documentation changes. There are no changes to functionality.

Because of the bug fix, I do suggest updating.

As usual you can download the program from GitHub or from SourceForge:

Source is available to download from both SourceForge or GitHub. Alternatively you can fork away in the GitHub repo - the master branch always contains the source of the latest release, while the develop branch has the latest development source and may not be stable.

CodeSnip 4.20.0 executables now available on GitHub

noreply@blogger.com (Delphidabbler) — Mon, 16 May 2022 07:10:00 +0000

I've managed to work around the problem I had yesterday when my antivirus program prevented me from uploading files to CodeSnip's releases page on GitHub.

So, the executable files are now available to download from the Assets section. And how don't need to toddle over to SourceForge to get them!

Here's the revised release page.

I've updated yesterday's blog post too.

Released CodeSnip v4.20.0

noreply@blogger.com (Delphidabbler) — Sun, 15 May 2022 10:36:00 +0000

Here's the first CodeSnip update of 2022!

First, there's an option to delete your user database if you really want to. Why would you do this? Well there's one possible reason and that's explained in this FAQ.

The second main change is that now the size of font in the detail pane can be customised from the Display section of the Preferences dialogue box. This setting applies to all text in the pane with the exception of the source code. The size of the source code can be changed from the Syntax Highlighter section of the same dialogue box.

While we're taking about the user database, I also fixed a bug that let you try to backup or move a non-existent user database, which wasn't pretty.

There are a few other minor tweaks that you can read about in the change log.

As usual you can download the program from GitHub or from SourceForge:

No update to CodeSnip needed for Delphi 11.1

noreply@blogger.com (Delphidabbler) — Sun, 27 Mar 2022 13:32:00 +0000

As I've blogged about elsewhere the latest version of Delphi, 11.1 Alexandria has been released.

Normally a new Delphi release is followed by a new release of CodeSnip that adds support for test compiling code with the new Delphi.

But not this time. Delphi 11.1 is actually an update to Delphi 11.0. You have to update from one to the other - they can't be installed side by side. Also the registry information CodeSnip uses to differentiate Delphi versions has not changed from Delphi 11.0 to 11.1. So there's no way to distinguish between the two. Indeed the RAD Studio's IDE still declares RAD Studio 11:

RAD Studio 11.1 IDE

What I am thinking of doing is to alter the way I describe Delphi 11 Alexandria inside to CodeSnip to read Delphi 11.x. Should be straightforward. (Really wish I'd no said that!!)

Back to the VCL for CodeSnip 5 Belvedere

noreply@blogger.com (Delphidabbler) — Mon, 17 Jan 2022 06:26:00 +0000

Well, my cunning plan to make CodeSnip 5 cross platform by using the FMX framework didn't survive contact with reality for long!

About as long as it took me to realise that SynEdit is a VCL component, in fact. And I really want to use SynEdit.

Another factor was my discovery that Delphi doesn't support GUI applications on Linux out of the box. And, yes, I know there's add on support in Delphi 11 Enterprise for GUI Linux, but that's complicating things slightly.

So that further scuppered my cross platform plans.

So CodeSnip is to remain Windows only. Ho hum.

I'm telling myself it doesn't matter that much because CodeSnip is mainly targeted at managing Delphi code, and the Delphi IDE is Windows only too!

New year's resolution: Have a 3rd attempt at CodeSnip v5

noreply@blogger.com (Delphidabbler) — Sat, 01 Jan 2022 14:18:00 +0000

Where have we heard this before?

OK, it was way back in 2013 when I first decided to try to develop CodeSnip 5 - a quite radically different version of CodeSnip than version 4. It was code named parsnip, as in pa[r]scal codesnip - really! Along the way that morphed into CodeSnip pagoda (I can't remember why) and then floundered.

In 2020 there was a partial reboot: pavilion. This was based on parsnip and was used to investigate one of two possible ways to strip the web service code out of CodeSnip before the services closed in June. It turned out it was quicker to revise CodeSnip 4, so pavilion got abandoned too.

Introducing CodeSnip Belvedere

And now, on 1st January 2022, I've just created a new belvedere branch off the CodeSnip 4.19.0 code tree to have yet another attempt at CodeSnip 5.

What makes me think I might succeed this time?

Well, I think the main reason the other attempts failed is that I tried to grow v5 from the a code base that goes all the way back to CodeSnip 1 in 2005. At 16 years old the code has been bludgeoned and battered into supporting four very different versions, so it's not exactly the tidiest and most coherent code you've ever seen. And that's probably where I stumbled - that mangled code is not easy change as radically as I need to for v5.

And then there's the fact that CodeSnip 4 really doesn't like compilers after Delphi XE - see CodeSnip Compiling & Source Code FAQ 11 if you want to know why.

So for belvedere I've decided to try to start from scratch. I'm using Delphi 11 Alexandria and ~~FireMonkey~~ [EDIT: VCL see this post]. Although belvedere has all the v4.19.0 code in it, I'm not going to use it by default. I'm starting development afresh in a new belvedere sub-directory and will only copy in the old code where it is suitable. The default position is that code will be new.

Will this approach succeed? I dunno. Progress will depend on my available time and enthusiasm.

New Year's Resolution - is that wise?

Hmm. Probably not. I don't usually make them.

But this year I have made two essentially contradictory resolutions. The first is this whole CodeSnip belvedere thing and the other is to play more guitar. Let's see if I can manage both.

More info & have your say

For details of what I'm planning see the new README attached to the belvedere branch on GitHub.

If you want to suggest anything then I've set up a CodeSnip 5 Belvedere discussion on GitHub where you can do just that.

Progress so far

Want to see how far I've got? About as not far as it's possible to be without actually doing nothing is how far. But, give me a chance, I only decided to do it today.

All there is so far in the belvedere branch is a .gitgnore file and README.md. There's also a blank Delphi 11 project - CodeSnip5.dpr - in the belvedere/src directory.

No forms? Nope - CodeSnip 4 uses a hierarchy of forms, which has proved to be one of the better design decisions, so I'm taking my time considering and how best to (re)design this for belvedere before adding any forms to the project.

Watch, as they say, this space. And now, I'm off to practise guitar.

If you celebrate it today, have a happy new year.

Released CodeSnip 4.19.0

noreply@blogger.com (Delphidabbler) — Fri, 31 Dec 2021 21:04:00 +0000

Just in time for the new year, CodeSnip v4.19.0 has been released.

This contains the promised re-organisation of the Preferences dialogue box to get rid of the confusing multi-line tabs. The dialogue box now has a list of pages in a pane on the left, with the relevant options appearing on the right.

I've finally worked out how to make the size of the font in the overview pane's tree view customisable - it's only taken me a year to respond to this request.

Finally, there's a fix to an obscure bug in the legacy Code Snippets Database loader code that I doubt has ever bothered anyone - but probably would if it wasn't fixed!

As usual you can download the program from the delphidabbler/codesnip GitHub repo's Releases page or from SourceForge:

Source is available to download from both the above repos or you can fork away in the GitHub repo.

For a complete list of changes see the change log.