WiT 8.3 Service Pack 4
Bug Fixes and Incompatibilities
WiT
- When a data object was displayed as text and there was only one line
and the line was longer than the computer screen, a horizontal scroll bar
appeared but the window was so short that the scroll bar covered most
of the text.
Also, it was impossible to scroll the last few characters of the text
into view.
- When a data object was displayed as text and there were more lines than
can be fit on screen, the horizontal that appeared covered part of the
last line, which could not be scrolled into view, unless the window
was made wider manually, causing the horizontal scroll bar to disappear.
Now the initial window size is correctly calculated so that the
horizontal scroll bar never appears in the first place.
- In WiT configuration files, paths with spaces were not read correctly.
- In 8.3 sp 3, the change made to allow the Object Editor to scroll
through a large object had a side effect: array objects did not resize
properly after the array size had been changed.
- When 'Base priority' is set to Fixed (the default), WiT was sluggish
to utilize all availabel execution threads, because the scheduler
system priority was set too low. Now a lower limit is placed on
the WiT scheduler priority so that scheduling response is always fast.
This was only an issue when using more virtual threads than physical
processors to similate highly parallel execution.
- Multi-column parameters were shown with overlap.
Standard Libraries
- 'const' operator when given strings containing '\' might crash if
the sequence after the slash was a semi-valid octal or hex number,
such as '\xk' or '\01w'.
Now semi-valid octal or hex sequences are considered as invalid
and the characters are accepted without conversion.
- 'convexHull' operator did not work on 16-bit images
- 'overlayData' crashed if a graphic object contained 0 points.
- Ellipse graphics in 'overlayData' always drawn with fill even when fill
was inactive.
Engine
- WiT Engine ActiveX (obsolete but still should be backwards compatible.
New applications should use VB.Net) sometimes failed in the 'Init' method.
- WiT Engine ActiveX 'controlDisplay' method sometimes failed for the
same reason as the 'Init' method.
- If an application used the WiT Engine ActiveX and the application
exited when the loaded WIC was still running or paused, a warning
about freeing data pops up, although no ill effects occurred after
the warning.
- WiT Engine 'simple' WIC used 'surface' instead of 'image', causing
demos that used this WIC to behave incorrectly.
(This error was introduced in 8.3.3)
C Programming
- When compiling a C++ operator library using Visual Studio 6,
a cryptic compiler warning appeared.
This was caused by the gMemFile.h file which was included
indirectly by the corObj.h file.
- When using WiT Manager to create a library with dependence on other
library contexts, the operator definition file becomes unreadable
by either the WiT Manager or WiT itself, causing all operators in the
library to be unusable.
