GitLab

Utilise Install_Log command (from Installer-0_18) to log the source directory
for a Merge. If the command does not exist, it does not give error.

During testing of the above change, a bug in the !Font merge process
was found that can cause it to put merged fonts in totally the wrong place.

The function static_ReadVariables() in Main.c, if APP=FONTMERGE, uses the
value of Font$Path to set Destination (the merge target) from the third path
element from the end, which assumes it is the system !Fonts.

However, if a
    *FontInstall mydirectory.
was done before the *FontInstall in BootResources:!Fonts, then Font$Path will
be set to 4 elements, eg:
    ADFS::SSD.$.!BOOT.Resources.!Fonts.,
    mydirectory.,
    <Font$Prefix>.,
    Resources:$.Fonts.
so any new fonts wrongly go into mydirectory.

The fix now finds the first directory seen which ends in ".!Fonts.", which is
the LAST one in the path string. This is better, though not totally foolproof.

Version 2.12. Tagged as 'Config2PluginxxxxMerge-2_12'

When Sys/Font/Boot merge are run in a mode < 1024 pixels tall, the act of creating the toolbox objects for the main window plus pane is subject to the Wimp clipping the windows to the top of the screen they were created in in the Res file.
So, if used in a less tall mode (say 800x600) the pane is wrongly offset in the agenda view.
Edit the Res files to be -512, -1024 OSU down in the bottom left corner to avoid this.

Version 2.09. Tagged as 'xxxxMerge-2_09'

Check with task manager if that _TaskName is already running and quit if so.
Messages files add new error
Comment title blocks no longer refer to FontSetup[D[D

Version 2.07. Tagged as 'xxxxMerge-2_07'

Bugfix: if the user clicked Agenda then Merge, the log directory wasn't being unset after the operation was complete. (Simple Merge operations were not affected.)

SysMerge version number increased to 2.00 to avoid clashes with old SysMerge applications. BootMerge and FontMerge versions also increased, to keep them in line with SysMerge.

Fixed event ordering problems that became apparent when click-type window tools were re-enabled in the Wimp. This involves a subtle alteration to the plug-in quit protocol.

Initial import of Configure plug-ins '!BootMerge', '!FontMerge' and '!SysMerge' to CVS, this time in the correct place.

Note that !BootMerge and !FontMerge plug in to !BootSetup and !FontSetup
respectively, and all three plug-ins share the same source code.