DelphiDabbler's Blog

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 . For more info please see the similar post on the CodeSnip Blog .

This is just a quick post to apologise to Oliver  for accidentally deleting his very useful comment on yesterday's post about fixing a long running bug in CodeSnip. I've reinstated as much of his comment as I could glean from an email notification as a reply to the deleted comment. Suffice to say, I'm now fixing the CodeSnip fix as a result of the info Oliver provided! So thanks for your help Oliver - I appreciate it.

This has been a  l o n g   time coming. 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! ⮞  Get the fix from GitHub   EDIT: no, don't get it - I'm releasing a fix for the fix soon. See comments below. For an explanation of what was causing this little horror of a bug, see the longer post on the CodeSnip Blog .

Here we go again. I've found another repo with some outstanding issues and part completed code. So once again things have been finished off and the result is the release of Version Information Editor (VIEd) v2.17.0. The release is pretty much a tidying up exercise. The code, like me, is old and not pretty. So too make it less embarrassing there's a lot of refactoring been done. Some dialogue boxes have been tarted up too. The only reason that this release gets a minor version bump instead being a patch of v2.16 is that a new -open command line option has been added to open the program with a specified file already loaded. For a list of changes see the change log . ➤ Download this release from GitHub . Here's an image showing the  -open  command being used to start VIEd with its own version information file loaded.

As part of my current manic programming streak, I've been poking around in some of my neglected repos (I really do have too many). I noticed that last year I'd been doing some work on PasHi  , my Pascal source code highlighter console app, but had never finished it. So I finished it, and the result is this v2.4.0 release. A few more command line options have been added and one bug has been fixed. A couple of command line parameters were deprecated. I won't list the changes here. Go look at the change log if you're interested. PasHi comes with an installer that gives the option to a install a GUI front end if you want it. That is PasHiGUI. It interfaces with PasHi to save you having to go anywhere near the command line. PasHiGUI is pictured below ⮞ Get the download from GitHub .

My busy streak of programming continues! v0.5.0 of GBG , my little utility that creates files filled with pseudo-random bytes of  G ar b a g e, is now available. Previous releases would fill up a 10MiB buffer of random stuff and then repeatedly output that until a file of the required size had been generated. So, for files smaller than 10MiB all the data was random but for larger files the data did eventually repeat. It struck me that having repeated data could be useful, but only if there was some control over the length of the repeated blocks. Conversely having a file of entirely random data may also be handy. So, I've added a new command line option with which a repeating block size can be specified. For e.g. to create 100 byte random block you would pass the -r:100 option to the program. To get a file that is full of entirely random bytes you can use -r:all . Now, when generating large files in can be tedious typing in long numbers of bytes and having to calculate (or remember...