WAsP Map Editor version 8.3.0.238. This is meant to be the last version 8.3 release. Further bug-fixes and new features are introduced in Map Editor version 9. If manually installing, please copy the EXE-file into a special folder like C:\Program files\WAsP\BinBeta\. Modify the folder name as appropriate to fit to National versions of Windows Operating System. 29 bugs have been fixed since beta-build 206: 1) Automatic editing during read-in (point thinning, merging of roughness-lines) did not cause the map to be reported as "changed". Now, in such a case, the map is marked as having been edited causing the usual save-query to be issued before closing. 2) Maps with Lat-lon projection (degrees coordinates) were saved with insufficent horizontal resolution ( 0.1 degree). Now, such maps are saved with a horizontal resolution of 1.0E-7 degree. 3) Selecting a large number of lines on basis of attributes (e.g. an elevation interval) might cause the program to lock up. This has been fixed. 4) In the RIX-graphics, the high-slope-indicating radial lines were missing; this has been fixed. 5) Extraordinary lines - hight-contours, roughness-lines or N/A-lines, i.e. extremely large (>128 K points) or with no points at all - would cause errors. Even very large lines may now be displayed, while zero-lines are skipped. 6) Autojoin with interactive confirm created an error regarding "focusing a disabled form" - has been corrected. 7) Elevations from 1000m and upwards were displayed with E-format; has been corrected so a fixed format with decimals is always used. 8) Opening a map file in the Map Editor directly from the Windows Explorer would create an error; has been corrected. 9) A number of bugs re. automatic roughness-cosistency checking have been fixed. 10) Version 208 would sometimes not open background maps; has been fixed. 11) Automatic joining of twin-line nodes during calculation of nodes would lead to an infinite loop - has been fixed. 12) Under certain circumstances map clipping would crash. This has been fixed. 13) Node-anchoring could be lost when saving the map file. This would happen if the line ends were very close, but not coinciding. Has been fixed. 14) Opening crash in case of map marked with the General Transverse mercator projection. Has been fixed. 15) Crash when transforming a very wide Lat-Lon map to Transverse Mercator projection. Would happen if the map width were close to the maximum allowable for the projection transformation (max. 1.5 zone width from central meridian to Eastern and Western map boundary). Has been fixed. 16) Huge consumption of memory space during on-screen digitization, in the end preventing re-loading of a background map. Has been fixed. 17) Map-clipping of large maps exceedingly slow. Has been fixed. 18) A few inconsistencies have been fixed re. preparation for version 9. 19) DXF-Maps were improperly opened: Incorrect lists of heights and roughnesses might occur, and the file-reading process could be very slow. 20) Nodes, dead-ends and cross-points were not always updated after editing or moving a roughness line. 21) Calculation of roughness-line crossinngs ("crosspoints") was too slow. Has been greatly improved, making it 2-3 times faster. 22) Crash might occur when performing multi-reference-point transformation if some reference points were identical. Safer error-trapping has been implemented. 23) Map-Adding would - due to an unexpected side-effect of some bug-fixing - create a memory access-violation. Has been fixed. 24) With an open map-dsiplay window with a background map, a projection transformation would not cause the display window to be updated properly (a large fraction of white space would appear). Has been fixed. 25) When editing the projection discription, a change in projection zone would sometimes not be effectuated. Has been changed. 26) Line(s) thinnig would create an error. Has been fixed. 27) Error during map transformation (e.g. of projection) if some lines were selected in the display window. Has been fixed. 28) Roughness line-face labels in line-property editing box could be wrong. Has been fixed. 29) The options to calculate elevation and RIX-numbers for the cursor-point by typing "R" and "A", respectively, would create an error. Has been fixed. In addition, please consult the "What's New?" topic in the on-line Help.