Posted the new version 0.9b in first post.
Main change is C3C support. Here's the full list:
changes from 0.8b to 0.9b
Features and functionality:
- added C3C (BIQ) support. [Added new terrain types, note: Marsh and Volcano will be visible but unpickable in the brush picker when using non-C3C maps, if pasted from a C3C map into a non-C3C map they will revert to: marsh-> grassland ; volc-> mountains.]
- added change tile bonuses functionality to Tile properties dialog, changed the layout and interface of dialog.
- added selection tools and new menu; analyse selection, deselect tiles of type/terrain, select all/none
- made resources gfx slighlty oversized on map to enhance visibility, added resource gfx toggle in Options-Map gfx
Bug Fixes:
- fixed the reset code in the Resize and Nudge Dialogs so that they reset properly after applying the tool - should fix fatal errors after using the 'apply' button :O
- fixed error with pasting tiles containing modded resources into non-modded map - If you paste tiles with resources that don't exist in the target map (the resourceID number is > max No.of resources) the resource will now be deleted.
- fixed minimap scrolling 'sticking' with very small maps
Misc:
- added BIC Mode indicator in map properties dialog. Useful because C3C editor can save files with .bic/.bix extensions - but actually saves them in BIQ file format!
MapTweaker will detect that these files are actually BIQ files and save them as such. Added a pop-up to notify user when such a map is loaded too.
- improved the paint terrain and paint resource functions to better detect whether they should paint or not.
- overhauled the InfoPanel code, messages outputted to user should be more meaningful... (removed some useless messages, added some useful ones, increased the default no of retained messages to 50, added a max no of messages and purge messages options to Options-General)
please note this is still very much a beta, I have some suspicions about altered start locations in mapTweaker being the possible cause of a bug... (if I'm right it will be fixed soon) use at your own risk anyhow!
All feedback welcome