Proof Updates

A Beta version of Proof 5 (P5) is now available.  Click here for details.

Release AY067 of Proof requires a license date of December, 2002 or later.  It includes no new functionality, but carries a release date that is closer to the latest release dates of other Wolverine products.

Release EC186 of Proof requires a license date of December, 2002 or later.  It includes the following additions/update:

A problem with fast-forwarding in animations containing plots has been fixed.

Release OV106 of Proof requires a license date of December, 2002 or later.  It includes the following additions/updates:

When writing abridged trace files for animations in which the color of a layout object (CPO) had been changed from that defined in the layout, Proof failed to include a "Set Color" command in the abridged trace file.  This problem has been fixed.

Release UG226 of Proof requires a license date of December, 2002 or later.  It includes the following additions/updates:

Proof's bitmap memory allocation routines have been modified to permit a small number of very large objects.  Every Proof object must be converted to bitmap form before it can be rendered.  Zooming in on very large objects can cause explosive growth of bitmap memory.  Proof previously imposed a limit of 1MB per bitmap.  This limit has been increased to 25MB, except in situations where total bitmap memory in use already exceeds 100MB.  In any case, zooming in on very large objects remains problematical.  Bear in mind that if a large object is also directional, one bitmap is created for every orientation the object assumes.

Proof 3D uses hardware geometry engines to perform rendering, so this problem does not exist in Proof 3D.

Release AN256 of Proof requires a license date of December, 2002 or later.  It includes the following additions/updates:

Proof's algorithm for computing accumulating path error tolerances has been smartened up.  When an object is placed on an accumulating path, Proof checks to see whether its placement violates declared for and aft clearances for the object and the objects ahead of it and behind it (if any) on the path.  Violations of declared clearances result in "encroachment" errors.  In the absence of an error tolerance (epsilon value), many encroachment errors would result from computational roundoff errors.  Accordingly, Proof has always used a tolerance value to forgive small errors.  While based on overall layout geometry, the computation of the tolerance value failed to properly account for certain extreme conditions (typically, the use of very large coordinate values).

Release EC195 of Proof requires a license date of December, 2001 or later.  It includes the following additions/updates:

For layouts with very large (X,Y) values, when drawing relatively small arcs, Proof incorrectly rounded arc pixel positions, resulting in arcs with flattened appearance.  This problem has been fixed.

Release OV215 of Proof requires a license date of December, 2001 or later.  It includes the following additions/updates:

Under certain circumstances, area fills in tall objects could be incompletely rendered in zoomed-in views.  Fills for such objects would simply stop at a given distance above or below the fill's seed point.  This was due to "safety valve" code that limits the vertical extent of fills.  The limits of the safety valve were established many years ago, when screen resolutions were lower than they are today.  The limits have been extended.

Release OV115 of Proof requires a license date of December, 2001 or later.  It includes the following additions/updates:

In rare instances, it was possible for an animation to generate "encroachment" error messages that were purely attributable to roundoff errors stemming from specifying trace file inputs with insufficient precision.  For example, users typically supply 4 digits to the right of the decimal point, and depending on the scale of a coordinate system, this may not be enough.  With this release of Proof, we have added an automatically-generated tolerance for encroachment errors.  Errors purley attributable to roundoff should no longer occur.

A problem with a string of attached objects starting and stopping when the string spans two or more paths has been fixed.  Prior to this fix, it was possible for attached objects to occasionally "jump" under such circumstances.  (We saw this happen exactly once in 15 years.)

Release UG175 of Proof requires a license date of December, 2001 or later.  It includes the following additions/updates:

A number of general  improvements have been made to security key interrogation.  Users who use more than one security key on the same machine should now see more logical behavior in the merger of product permissions and license dates retrieved from more than one key.

Release UG045 of Proof requires a license date of December, 2001 or later.  It incorporates the following update:

This release fixes a problem with an algorithm that Proof uses to reduce bitmap storage requirements for very large animations.  When an animation consumes more than 25MB of bitmap memory, Proof's memory allocation algorithm reduces the number of orientations of any object that are kept for reuse.  Prior to this release, under certain unusual circumstances, bitmap memory data structures could become cross-linked, leading to unpredictable behavior, including outright freezing.

Release UL255 of Proof requires a license date of December, 2001 or later.  It incorporates the following update:

This release fixes a problem with the use of date-formatted time displays on Proof's toolbar.  For those of you who are unfamiliar with this feature, a brief descriptions follows.  Clicking on View, Toolbar Date/Time Format displays a dialog boxes that provides a number of options for showing animation time as something other than a floating point number.  In this dialog box, you must specify a time unit, e.g., minutes.  You can then choose a format in which time/date is to be displayed, e.g.,

    Mon Jul 25, 2005 10:00 AM

Finally, you must inform Proof of the time and date corresponding to animation time 0.0.

When you save the current layout, Proof will write "Define Date" and "Define Clock" commands to the layout file.  For those of you who generate your own layout files, the details of these commands are available in Proof's on-line help.

The bug fixed in this release originated a number of months ago when international date formats were introduced for a Proof  OEM customer.

Release UL155 of Proof requires a license date of December, 2001 or later.  It includes the following additions/updates:

This release fixes a problem that was recently encountered for the first time in the 14-year history of Proof.  When creating or editing a bar graph In Proof Draw Mode, it is possible to drag the left edge of a bar to the right of the right edge.  In fact, all four edges can be "over-dragged."  When this happened, when saving the layout Proof would write bar position data that was rejected when reading when the layout was subsequently read.  Proof didn't like seeing bars whose right edges were to the left of their left edges.  Two corrections have been made to Proof.  Draw mode has been corrected to properly handle over-dragging.  Layout processing has been modified to handle non-conforming bars.  For example, if a bar's top edge is below its bottom edge, the definitions of the top and bottom edges are swapped.  This correction enables Proof to handle any nonconforming layouts previously generated in Proof Draw Mode.

Release AR155 of Proof requires a license date of December, 2001 or later.  It includes the following additions/updates:

This release incorporates a number of changes made to better support our OEM customers.  Non-OEM users are unaffected by these changes.

Release EC134 of Proof requires a license date of December, 2001 or later.  It includes the following additions/updates:

A problem with the interaction between demo pace settings and "normal" animation viewing speeds has been fixed.  The problem arose only in certain situations when a presentation script (PSF) file made use of multiple, consecutive "run *" commands, at least one of which required "rewinding" the trace file to its beginning, and an overriding pace was specified via the Presentation Mode user interface.

Release OV014 of Proof requires a license date of December, 2001 or later.  It includes the following additions/updates:

A problem with object collision detection has been fixed in p432.exe (the 32-bit color version of Proof).  8-bit color versions of Proof, e.g., p4.exe, are not affected.

Release CT244 of Proof requires a license date of December, 2001 or later.  It includes the following additions/updates:

Proof's on-line help is now in the form of HTML files.  The use of hyperlinks makes it possible to navigate quickly to the information you need.

You can now control how Proof displays the current animation time in its toolbar.  For example, you can specify a format that shows the current month, day, and year, and hour, minute, and second.  To use this capability, you must do two things.  First, you must specify your animation's time unit, e.g., seconds, and specify a time/date format.  You can do this by opening a layout and clicking View, Toolbar Date/Time Format.  Second, you must tell Proof the time and date corresponding to animation time zero.  For details, see the description of the Set Date trace stream command in Proof's on-line help.

Proof's handling of conflicting applications has been improved.  A conflicting application is an application that acquires exclusive control of the screen in such a manner that Proof cannot run.  Among such programs are Microsoft's NetMeeting and Remote Desktop Sharing.