History ~~~~~~~ v1.1.6 (build 18 Alpha) (17th April 2005) -Message changes in various areas to better describe status. -[Display Warnings] tickbox is now enabled by default for new users. Otherwise important messages when first starting MapBorder could be missed. -If Oziexplorer was not installed in "C:\Oziexplorer" or "C:\Program Files\Oziexplorer" and the ozi path was not already known, then autostarting would malfunction. Fixed. -Improved error checking for lat/long manual edits. -When enabling Corner Marker dots, the text and the dots are now be turned off to prevent obscuring text on the map image. v1.1.6 (build 17 Alpha) (25th January 2005) Changes: -Removed [Smarter Inserts] tickbox from 'Settings' tab. This option is now permanently enabled. Added: -Added an "Edit" function. Behaves effectively same as a "move", but user specifies the target location by co-ordinates (and datum), rather than by clicking on the map. The [Edit Point] tab is used for this, and will only become active where required. Fixes: -Improved initial auto-detection of Oziexplorer path, if it is not already known or has changed. -Added several missed configuration options to "Restore Defaults" function. -Several fixes/additions to help file to update for new features. -Log file correctly reports "unknown" Oziexplorer version if not running when MapBorder was started. -Log file now states version of Oziexplorer if/when auto-started. -Where applicable, log file specifies invalid map datum. -Log file inserts a space between entries whenever MapBorder is started, to improve readability. -Improved logging instances of Oziexplorer version. v1.1.6 (build 15 Alpha) (12th December 2004) Added: -The "restore factory defaults" box now has an icon. -Added a logfile function. If enabled, will log user activity and errors to "Mapborder.log" in the same folder as the executable. Fixes: -If backup files were enabled, and user selected "yes" to delete backed up files at program exit, they would not be deleted. Fixed. -Improved error reporting when an invalid datum is found in a map file. v1.1.6 (Build 14 Alpha) (4th December 2004) Features: -Added a confirmation enable option. If enabled, will ask yes/no for "are you sure" type messages. If disabled, will assume Yes for all answers. -Added [Default Border] function. Will automatically create four corner markers, one at each corner of the image, the same as what Oziexplorer does by default when first calibrating a map. This presently requires the user to acknowledge an Oziexplorer error message. There is presently no neat way to work around this, but it still beats doing it manually... -Updated help file with changes. Fixes: -Fixed stayontop when file selection dialog comes up. (dialog box would appear underneath the main application). -Actually removed the now redundant "Force To Top" option in the Functions menu (forgot do it in the last release). -During a Load Folder operation, if a map had an invalid datum, it would abort without continuing with the remaining files. A message is displayed to advise the user to check the datum before trying that map again. To help with this, I've changed the error message text slightly, and also included the MAP file name that is affected. -A few more spelling corrections. -Changed the way dialog box text is drawn. Many of the messages now have associated icons. -The hint for the [Undo] button was disabled for some reason. Fixed v1.1.6 (Build 11 Alpha) (21st October 2004) Features: -Changed the [Position to first point] function. Now has been renamed to [Auto Reposition], and repositions to following points as well. Bugfixes: -Frees memory occupied during configuration file access. (oops!) -Added hints to buttons I had forgotten to put in earlier, and also correct a few spelling errorrs. :-) -The "Force to top" option within the Function menu has been removed, Implemented several enhanced StayOnTop fixes: - MapBorder will be automatically forced to top if the application has been redrawn by Windows: Such as if it were minimised then re-maximised, or another application were attempted to be placed on top. -All messages boxes from MapBorder will now appear on top of any other windows, and also stay on top. This will ensure you see any messages from mapborder. -The MapBorder About box will also stay on top of any other window. -While a file or folder is being selected for edit, MapBorder will not be forced to top. This was done because the folder selection dialog would appear behind mapborder (which would be rather annoying). After the file or folder has been selected, MapBorder will regain StayOnTop status. -The "[Load Folder] only finds" options under the Settings tab are now greyed out when not applicable (in the middle of a Load File/Folder operation). -Would not save the last used folder name after a [Load Folder] operation. Fixed. -The 'Find only unmodified maps' option would crash if it found a map file with more than four corner markers. Fixed. -Changed status bar text from "Loading selected MAP file..." to "Loading MAP file..." to better cater for the [Load Folder] function. Changes: -Cleaned up the help file a litte, added new features and configuration options, added some error messages, added some hints on making mapborder run faster, v1.1.6 (Build 10 Alpha) (4th October 2004) -Expanded Settings for [Load Folder] options. Can now also restrict read MAP files based on file age. -Changed layout of INI file. Added a 'DefaultSettings' group which contains all options in Settings tab. MapBorder v1.1.6.10 or greater should be backward compatible with older (existing) INI files, old settings will be read, and saved under the new header. -Updated help file to reflect new features & changes. Corrected more headers and layout errors in help file. -Some minor cleaning up of code. v1.1.6 (Build 9 Alpha) (4th October 2004) -Renamed the "File" menu to "Functions", as it is more descriptive to what it really does. -Added a "Force to top" option within the Functions menu. This is actually a workaround till I find a better way to handle it. If minimising Oziexplorer and MapBorder, then bringing them back, it is possible for MapBorder to no longer stay on top. This function forces MapBorder to the top again. I don't think this is a bug as such, but rather an interaction between how Oziexplorer and MapBorder handle their on-top status. If anyone finds a reliable way of making Mapborder fail in this manner, tell me, as I can't get it to fail anymore... -When loading a map for edit, MapBorder can now (optionally) position the window on the first existing point. -Changed default oziexplorer start path to c:\program files\oziexplorer. It can still be changed if required. -Added some missing defaults to 'Restore factory defaults' function. -Corrected some cosmetic errors in help file, also added new functions to help file. v1.1.6 (Build 8 Alpha) (30th September 2004) -Revised Legal and Licencing information in help file. -Added provision to access the help file via MENU Help > Help -Added provision to search for and subsequently load the Oziexplorer executable, whatever the executable name. v1.1.6 (Build 7 Alpha) (29th September 2004) Note: -There have been many internal changes made to how lines are handled and drawn. Lots of testing will need to be done. Additions: -Added a [Skip 10] button. Similar in operation to the existing [Skip] button, but skips 10 maps instead of just one. The back skip (right-click Skip button) does not operate for this. -Added a "Draw Curved Borders" tickbox to the Settings tab. If ticked, will draw curved border lines instead of the straight lines it used to. (where applicable) This function may be quite processor intensive, so can be disabled if you find it too slow. Also, a message on the status bar has been added while redrawing, to indicate a redaw is in progress. -The help file has been updated with the new features/changes. Fixes: -During a "Load Folder" operation, if the last map file was edited and saved, the [Skip] button would not be disabled. -Since the same button is used for the single Skip forward/backward function, the text of that button changes: Whenever a backward skip is available, the button is shown as [Skip (<)], otherwise [Skip] is shown. -Minor internal changes to the About box to help with maintenance. (should not result in any visible changes) -Changed Settings tab "Backup map file" to "Backup map file(s)", since the user might actually be handling more than one file. :-) v1.1.6 (Build 6 Alpha) (25th September 2004) Fixes: -Made the existing border checking less stringent. If a MAP file contains an invalid IHW line entry, MapBorder would falsely identify borders as invalid, even though that map file would work perfectly under Oziexplorer. (Ozi doesn't need the IWH line) The error message associated with this error has been replaced with a warning. Additions: -Per the above fix, there is a new tickbox in the Settings tab: "Display Warnings/Diagnostics". Useful if you have a map series with an error that causes MapBorder to falsely identify existing borders as invalid, or if you are manually repairing MAP files. -Added a right-click option to the [Skip] button. If you've clicked once too many and gone over a map that you didn't intend to, right-click the skip button and it will go back one. This is not a full-featured backward step, it can only return to the last skipped MAP file. Changes: -The 'Configure Defaults' tab has been renamed to 'Settings'. -The help file has been updated for the new features/changes. v1.1.6 (Build 5 Alpha) (24th September 2004) Fixes: -The CM entry box is cleared once a map edit is complete. Previously, it would not have cleared if using the "Load Folder" function. -Supports early version map border specification lines (MM1A & MM1C). Previously would crash with early version map files that contained these lines. Once edited, the old style lines are replaced with the new style MMPNUM, MMPXY and MMPLL lines. Additions: -The About box now shows the OziAPI.dll version. Please note that OziAPI.DLL v1.08 reports as v1.07, this appears to have been an oversight before 1.08 was released. So how do you tell the difference between 1.08 and the real 1.07? Mapborder will abort at startup with an error that a particular function is not present in OziAPI.DLL. v1.1.6 (Build 4 Alpha) (10th September 2004) Fixes: -When selecting 'Load Folder' and a network folder was last selected, there may be a significant delay before the folder selection dialog appears. (The delay appears to be a Windows networking "thing", and beyond my control) A status bar message to this effect has been put in, advising to please wait. -During a 'Load Folder' operation, and under certain conditions, the "undo" button was not cleared at each following map edit. -When not applicable, the background colour of the "point number to insert" box is greyed out, before, it remained a lighter colour, and not always clear that this function is not applicable at that time. v1.1.6 (Build 3 Alpha) (4th September 2004) Fixes: -Added hint for Config Tab: "only find unmodified maps" tickbox. -When processing folders and using the skip button, it would start counting at 1, but continue counting backwards from the last number. -When inserting a fourth corner marker, the Save button would not become active. -The Load Folder dialog box has been modified to allow network drives as well. -When processing folders, if all maps are being modified and saved, the counter would not update for the very last map. v1.1.6 (Build 2 Alpha) (18th August 2004) -Perhaps it was because I wasn't used to it, but I found the autostarting of oziexplorer right at the begining a little unnerving. So I put it back to when the Load MAP/Folder buttons are clicked. -After all the unsucessful workarounds, I finally managed to get the file and folder dialogs to stay on top after oziexplorer was auto-started. -Changed the help file again to reflect the autostart point of Ozi, and some updated some messages. v1.1.6 (Build 1 Alpha) (17th August 2004) -Oziexplorer is now automatically started maximised, not minimised. This was done for several reasons: -It makes sense that you can immediately see what you're doing within ozi (where you can't if it's minimised, duh) -It saves the user from maximising Oziexplorer themselves. -The second point was sometimes no longer possible just by clicking Ozi on the taskbar since version v3.95.3g4. However, the whole reason I had started Ozi minimised in the first place, was because I couldn't get the file or folder dialog boxes to come to the top and be visible if Ozi was started automatically. So, to fix this: -The way Mapborder automatically loads Oziexplorer has changed. Now, Oziexplorer is loaded at program startup, not when the load map/folder buttons are pressed. -The help file was changed to update a new error message, and to remove a redundant message. A few minor hyperlink discrepancies in the help file were also fixed. -A good proportion of the auto-start and Ozi path detection code has changed, please report any bugs. The release has been changed to Alpha, because there still needs to be testing done. v1.1.6 (Build 0 Beta) (14th August 2004) -Now has the option of sequencially processing all MAP files found in a specified folder. Useful if you need to do many maps, as it saves the trouble of loading every single file manually. -Related to the new Load Folder option, a [Skip] button allows the user to skip over the currently selected file, and proceed to the next one. -The far right hand side of the Status bar shows which file you are up to, and of how many. -A reasonable proportion of the button code was changed in this release to allow for this new feature, and will thus need to be tested further. -The help file has been updated to show this new feature. -Corrected the MENU: File-Restore Defaults selection, to include some variables that were left out in the previous release. v1.1.5 (29th July 2004) Bugfixes: -Corrected fault where the decimal separator was incorrectly saved, under regional settings that did not use the period as the decimal separator. -While adding, moving or deleting points, two quick, consecutive map clicks would cause an error. This has been fixed, by disabling mouse clicks while the points and/or track are being redrawn. v1.1.4 (25th July 2004) -Added [AutoInc] tickbox (Auto Increment). Operation is associated with CM: manual insert point. If ticked, will automatically increment the number entered in the CM: box. -The CM: edit box and AutoInc tickbox are greyed out if (Insert) radiobutton is not selected. v1.1.3 (18th July 2004) -Improved smart insert. Now looks for non-perpendicular possibilies, if distance between new point and existing point is less than alternative perpendicular, it uses that instead. Note that with this feature enabled, a point will ALWAYS be inserted. -Added an option to disable non-perpendicular smart inserts (so it works same as before). -Added confirmation when resetting configuration variables to factory defaults. -If loading existing border from MAP file for further editing, mode is changed to [Insert]. -Changes to help file: Further explain smart inserts and how they work. Added pulldown menus to help. Added several (already existing) submenus to Contents section. A few other minor spelling changes. v1.1.2 (6th May 2004) -Improved screen positioning and checking. Under some circumstances, it would be possible to position Mapborder past the edge of the screen and it still not recognise that it was positioned in such a manner (and thus start at centre). v1.1.1 (2nd May 2004) Changes: -Some documentation corrections. -Some error message changes to make the message more descriptive. -Removed "Save PLT track file of new border", because it is not _really_ applicable to MapBorder, and this functionality is now performed by my IndexMap utility. v1.0.10 (build 2 beta) (21-Apr-2004) Cosmetics: -A couple of very wide dialog boxes where split into two lines. -A few minor internal changes to neaten code. Changes: -Improved error checking of datum of loaded MAP file. Now detects if the datum of the map is not supported by ozi. v1.0.10 (build 1 beta) (18-Apr-2004) Cosmetics: -Minor fix to Mapborder Icon. -Corrected Status Line text after saving a MAP file (status line was not updated). -Added a couple of "Loading MAP file.." Status Line messages when loading maps, just in case map load takes some time. -Changed Status Line cosmetics to a more "standard" windows style status panel. -A few minor internal changes to neaten code. v1.0.9 (build 7) (15-Apr-2004) Bugfixes: -While auto-starting Oziexplorer under some conditions, mapborder would obtain an incorrect map path, and save this to the INI file, effectively overwriting the previously correct path with the new invalid path. Cosmetic changes: -Added hints to links in about form, The Mapborder and Oziexplorer homepage URLs were not apparent otherwise. -Corrected a hint. v1.0.9 (build 6) (10-Apr-2004) -Multiple instances of Mapborder are now disallowed. v1.0.9 (build 5) (7-Apr-2004) -Improvement in ozi auto-start code. More reliable, and startup time should be faster as well. -Added Oziexplorer homepage to About form. v1.0.9 (build 4) (1-Apr-2004) Changes: -Slight improvement of code when starting ozi automatically. I still need to do some work in this area. -Restricted the number of colours for the original and new border lines -Colour selections now use real colour names, not the delphi colour constant names. -Re-enabled StayOnTop for testing. If you can read this, it means I've forgotten to take it out. v1.0.9 (Build 3) (31-Mar-2004) Changes: -The text representation of the date & time of all the saved track points are now included. -The [Load MAP] button will now start Oziexplorer if it is not already started. You will have to start oziexplorer manually at least once before doing this, otherwise it does not know where the executable is. Mapborder always assumes the executable name is "oziexp.exe". -There are new active links for email, and the Mapborder home page within the Mapborder "About" dialog box. v1.0.9 (Build 2) (27-Mar-2004) Changes: -Minor change to the icon, slightly rounded off the edges. Bugfixes: -Some buttons were not disabled after a Save operation was performed. v1.0.9 (Build 1) Changes: -Added an option to save the new border as a track file. The new *.PLT track file is in the same folder, and has the same name as the .MAP file. Bugfixes: -Improved checking of existing (original) corner markers: If any lines in the *.MAP file appear invalid, or, any of the MMPLL lines in the *.MAP file appear out-of-order, or, there are more or fewer MMPLL lines than expected, or, any corner markers are positioned outside of the map image range, then, the original border is deemed invalid, and the user is required to enter a new border from scratch. In earlier versions, it was possible some grundged lines could cause Mapborder to crash. -In some cases, it was possible with a (grunged) original MAP file, the new MAP file would also appear grunged. v1.0.8 (build 9) Changes: -Put warnings about Alpha or Beta software releases back into the About dialog box. -Changed the code for the up/down buttons and associated text boxes for the border widths. They should however, operate the same as before. Bugfixes: -Correctly handles *.MAP files with Map Scale Factors other than 1. -Fixed the MapView window line workaround (wrong datum, don't ask me how I missed this). v1.0.8 (build 8) -Cosmetics: Move CM: text slightly to line up with text box. Text changes within the about box. About form can now resize if larger fonts are used. -There is a bug (or oversight) within the Oziexplorer MapView window that does not close (draw the last track line) for closed polyogon track types. A workaround has been implemented within Mapborder so the lines drawn within the MapView window now appear correct. v1.0.8 (build 7) (24th March 2004) Changes: -Changed the program icon, added copyright for Oziexplorer and other cosmetic changes. Bugfixes: -The 'Show All Tracks' button within Oziexplorer is automatically enabled now. There is no need to manually press it anymore. -The new track border width is now correctly modified when the up/down buttons are used. v1.0.8 (build 6) -The Mapborder form size can now stretch to fit enlarged font sizes. v1.0.8 (build 5) Bugfixes: -Removed Stay On Top (STILL causing problems, sigh). Mapborder now behaves like a "normal" application. -The border width weird counting thing is now fixed. No really, not like last time, really this time. v1.0.8 (build 3) Changes: -Added a Restore Defaults menu option, to clear the user preferences to "factory" defaults. -Loading original border can now be undone. -Delete All can now be undone. -Undo memory has been upped to 500 actions. {to cater for load Original Border and Delete All} Bugfixes: -Enough is enough. After stuffing around with the StayOnTop problems and fixes (both by-the-book and brute-force fixes) I've had enough- Removed the Stay On Top selectable feature, and leaving it out. The form now is configured to stay on top and will remain that way. -The [Delete All] button is now enabled (oops, broke it in the last version). -Border width scroll buttons were not syncronised, would have a weird counting order thing happening. -The order in which the buttons are highlighted when the tab key is pressed have been neatened. v1.0.7 (Build 7) -Stay On Top feature has been re-written. The procedure to reproduce the StayOnTop bug does not result in a fault. The side-effects/faults that were present, are now gone. v1.0.7 (Build 6) -The Add, Insert, Move and Delete functions are now grouped together. The selected function remains active until changed by the user. This allows for easier inserting, moving or deleting of points since you don't have to press buttons every time. -Removed Stay On Top option- this was causing a variety of problems. I will need to do some more work in this area before returning this option. -Reorganised code to make it neater (internal changes). -Improved idiot-proofing somewhat. -The point selection code for the Delete and Move functions now has a limited range. Previously, it would pick the closest point (regardless of where you clicked and how far away it was). Now it picks the closest point that is ALSO within a 30 pixel radius of the clickpoint. If there are no points within a 30 pixel radius, it beeps and does nothing more. -Corrected some spelling. -Border widths are now user configurable. -The last used folder is now recalled when starting Mapborder instead of the default Oziexplorer map path. -The Corner Marker numbers are now viewable for both the original AND new borders. And can both be individually enabled or disabled. -Made the Smart Insert routines smarter. v1.0.6 (Build 7) (14th March 2004) Changes: -The [Insert] button now has smart capability. If you don't enter any point number into the CM: (corner marker) field, it will attempt to auto-detect the number. It is not always possible to reliably detect (depending on the existing map border), so it still accepts manual entry of corner numbers. v1.0.6 (Build 4) Changes: -The [Delete] button is now "smart" It deletes the closest point you click to. There is no need to specify a point number anymore. -The [Move] button is now "smart" It needs two mouse clicks on the map image, The first click should be on the point you wish to move, The second click should be at the new target spot to move to. -Added an [Undo] button. It undeletes deleted points, it unmoves moved points, and deletes created and inserted points. There is a 100 point undo buffer, so you can go back up to 100 actions. Loading the original border cannot be undone and clears the undo buffer. The [Delete All] button cannot be undone and also clears the undo buffer. I have added appropriate warnings to this effect. -I have removed the delete last button. The new [Delete] and [Undo] buttons are better, and are somewhat less confusing than the old buttons. Bugfixes: -Would crash if any blank lines were present in the map file. Fixed. -The [Delete All] button would not correctly clear the track, AND it would stuff things up if you tried to add more points. (I broke it on v1.0.5). -I've tried to fix the 'Stay on top' bug, where mapborder will not stay on top. Still don't know if I squashed this, as I still haven't found a way to reliably reproduce it. v1.0.5 Changes: -Merged the create border and edit border pages into one. -The corner marker indicators now show CM: for Corner Marker: rather than MB: (Map Border:) I had used before, which makes more sense. -The corner marker indicators are now always available, enabled as per the configuration "Show CM Numbers" tickbox. This enables or disables the corner marker display. Disabling this option helps with redraw speeds on slow machines. -Track redraws may be faster in some instances. Bugfixes: -All operations now first check to see if Oziexplorer is running before continuing, in case Oziexplorer was shut down in the middle of an operation. -Added other various checks around the code. v1.0.4 (12th March 2004) Changes: -After saving a new border, Mapborder re-loads the new map so users can see the changes (if MapView window "show corner markers" is enabled). -The version number is included in the windows standard EXE information. The version number is available in the "FileVersion" property. The condition of the software release (alpha/beta etc) is available in the "BuildState" property. -Tracks 74 & 75 (original and new borders) now have descriptions. -Closing down Mapborder is now available through the 'File' menu item. -An "about" dialog box is now available through the 'Help' menu item. -Mapborder now closes the Oziexplorer API on exit. This is the recommended procedure to prevent errors, especially if running on Windows 2000. Note that OziAPI.DLL v1.08 MUST be available. -If any backup files were created, on exit, you will be asked if you want to delete them. -The Mapborder icon has changed slightly, the old one was partially obscured if used as a shortcut. -The colours of the original and new map borders are now user configurable. -All tickbox options and colour selection options are saved automatically to the INI file. -The Mapborder screen docking position is saved in the INI file, and restored to the same spot on startup. In the event Mapborder is positioned off the edge of the screen, it will be repositioned to the centre the next time it is started. -Added capability to modify existing borders without starting from scratch. Corner markers can be inserted, existing corner markers moved, or existing points deleted. -There are now three tabs to split up the different functions of Mapborder. The first tab is used when creating map borders from scratch, The second tab is used to modify exising borders, The third tab holds all the configuration options. Bugfixes: Nil. v1.0.3 Changes: Updated and cleaned up documentation. The way the original (blue) map border was handled, has changed. Previously, the track would only be created and drawn if the [Draw original border] tickbox was checked. Now, the original border is always drawn, but only actually shown if the tickbox is checked, otherwise, it's just hidden. This now enables you to see the original if you initially had the tickbox unchecked, and changed your mind afterwards. Changed the format and colour of the border point count display. (I had originally intended it to look like that anyway). Bugfixes: The original blue map border display had a bug where the very last point drawn may use the wrong map datum. The saved border locations previously were rounded off to about 3-4 decimal places where it should have been at least six, fixed. v1.0.2 Corrected a problem where Mapborder.exe would be positioned past the edge of the screen. (Whoops, sorry!) Fixed the form size so it can't be changed. The window maximise option has been disabled. The [Delete last point] and [Delete all points] buttons were incorrectly enabled when they should not have been. Added a 'Stay on top' tickbox, so you can keep an eye on which point number you are up to. Added hints to the buttons and tickboxes. v1.0.1 Added [Delete All Points] button. Similar to the [Delete Last Point] button, but clears all the points. Added [Abort] button. Once [Start] has been initiated, you can stop and clear everything with the abort button. A beep will be heard if entry of more than 100 points is attempted. Various buttons are enabled and disabled as applicable: The [Save border] button only appears once four or more points have been entered. The [Delete last point] and [Delete all points] buttons are only enabled if there are some points to delete. If Oziexplorer had been shut down halfway through point entry, the software will effectively abort and start again when any of the delete last, delete all, or save buttons are clicked. v1.0.0 (7th March 2004) Initial write