If you’re a bleeding edge user of StrongED, Fred Graute has another updated test release for you to play with: Version 4.70a22 (zip). You can also grab the sources (zip) if you wish to look at them, and if you’re on version 4.70a19 or higher you can download a smaller update (zip).
Changes in this version include:
- A new ‘Diff’ button on the Refresh dialogue box. This performs a ‘diff’ analysis against the loaded file compared to the version saved on disc, provided SideDiff is present on your system.
- The Counter dialogue box has seen a lick of paint to make it look more like the Search and Replace one, as well as to reduce the amount of empty space – and when the Counter dialogue is closed, the Search and Replace one is now re-opened at its previous size, rather than how it’s configured.
- Functions could previously take a string or a named search expression as a parameter, but now a search expression can be given directly, rather than having to define them in a ModeFile first.
- There is a new ‘HighlightWord’ function that will highlight every occurrence of the word at the cursor – a potentially quick way to search for instances of something than having to enter it into a search dialogue. However, this is still experimental, and details of how it’s used are therefore subject to change.
- The existing MouseToBuffer function, which grabs titles from windows and text from icons and feeds it to the keyboard buffer, now waits until the Ctrl and Shift keys are released before it performs that action, as do other functions that feed text into the keyboard buffer. This prevents tools such as DeepKeys from also picking up the Ctrl and Shift keys and acting upon them as keyboard modifiers.
- Clicking on ‘Help’ in the Search and Replace dialogue has been reinstated.
- Filenames in Data Transfer messages were previously being canonicalised within the message block, which caused issues with applications that didn’t expect the filenames to change part way through an exchange. This has now been changed so that the canonicalisation is directed to a separate buffer.
There is still some active debug code present in this version, which Fred is using to try and catch an intermittent bug that has been present in version 4.70x for some time. When the code is triggered, it produces a dump file (StrongDumpX) in the root directory of the boot drive, and pops up an alert window to bring the user’s attention to it. Fred asks that if this happens, please send him the StrongDumpX file, and as much detail as possible about what you were doing when the error occurred.