These patches are only applicable for MetaEdit+ 3.0, pre-Service Release 1. We strongly recommend using Service Release 1 instead.
The patch links below are direct links to the .pat files, which are binary files that MetaEdit+ can read with its 'File in Patches' function in the startup launcher. Download the patch by selecting 'Save to file' in your browser: do not attempt to view as HTML pages! Check the size afterwards: some browsers appear to download these as ASCII files, when they are in fact binary files.
What's new?
1.6.99: Improved ntexecute3.pat, updated imagemap.txt to mention Netscape 4.5 problem.
How to use patch files
The basic idea is to run a clean MetaEdit+ image, file in the patches using the button in the initial Startup Launcher, then exit the image which saves the image with those changes. Patches must be filed in in order, only optional patches may be omitted.
More detailed instructions are here.
All patch files are supplied 'as is', with no guarantees, and no liability for any
damages is accepted by MetaCase Consulting.
Beta Patches
These patches are not fully tested, nor normally necessary for operation of MetaEdit+: install them and use them with care, and only if you want or need the changes mentioned.
- Image maps for HTML reports (new feature)
- Previously, GIF pictures in HTML generated from MetaEdit+ were not clickable maps. This patch, imagemap.pat, adds a client-side map automatically to an HTML file whenever a gif file is generated. See the documentation in imagemap.txt for more details. Here's a quick example of the output. You can also download an updated and new report for Project Model for after this patch (make sure after download that the newline character is correct for your platform!).
- External commands in NT
- Under Windows NT, executing external commands may fail because of inconsistencies between Windows 95 and NT. MetaEdit+ uses external commands to open on-line help, open External Element property values, and for external; ... execute; commands in reports. The ntexecute3.pat patch corrects the format of these calls to work in NT. It replaces the previous ntexecute2.pat, which had problems with filenames with spaces in, and can be applied on top of ntexecute2.pat.
- Pop-up menu starts with 'relabel as...' in Windows
- For certain mouse drivers in Windows, in particular some wheel or Intellimouse types, the number and mapping of buttons may be reported wrong to MetaEdit+, making it difficult to open the normal pop-up menus. For a normal two button mouse, one button should be a normal selection click, and the other should open a pop-up menu for the selected item. If there are three buttons, the last one will open a menu for the window, beginning with 'relabel as...'. Holding down Control while opening pop-up menus will allow you to temporarily swap the second and third mouse buttons and open the normal pop-up menu (you will need to do this to choose 'file in' while applying this patch!). The buttons.pat patch will swap the second and third buttons in MetaEdit+. You may also try adding the following lines to the end of your win.ini file (legal values are 2 or 3), and restarting MetaEdit+ (you need not reboot):
- [Visual]
- MouseButtons=2
- Central European fonts do not work
- In MetaEdit+ in Windows with Central European fonts, the standard Arial font is used (or something else), not Arial CE. This beta patch, cefonts3.pat, allows you to use the CE fonts. Note that there is some chance that strings using these characters will cause problems when used with or imported with images without this patch. Also, if images have this patch, but no CE fonts, the standard fonts will be used: many characters still look right, but some are mapped to something completely different, e.g. r hacek to o slash.
Known Problems
- Re-exporting models with Graph Manager after garbage collect causes problems to re-importers
- Updating previously imported models is based on the objects' unique identifiers, OIDs, in the source database. If some exported objects are garbage collected in the source database, their OIDs are freed to be used again for new objects. Exporting one of these new objects with the same database name will give problems to importers who previously imported the old object. Workaround: do not perform garbage collect in databases used as sources for repeated exports. Performing 'condense versions' is safe.