New build of AfterGRASP is up for download:

http://www.aftergrasp.com/download/agsetup_20060202.exe

Made note, I've finally got the directory listing for the download
directory at aftergrasp.com working (had to install a PHP script to
generate the page on the fly):

http://www.aftergrasp.com/download/

----------------------------------------------------------------------------
Thu, 02 Feb 2006

->root wasn't being filled in correctly by XML load.


New command TOMEASURE, it takes a string and if it's a numeric constant
followed by a measurement suffix it will output a measurement object.

   xpos = tomeasure("50pct")
   ypos = tomeasure("3.2in")
   imageput @xpos @ypos example.gif


The routine which translates ASCII into float had a small rounding error
now fixed. For example 100.547 was being stored as 100.5470000001
This was preventing some floating point constants from being compiled
correctly by AGCOMP.


AGCOMP was storing floating point constants as 30 bit floating point.
If a number could not be accurated represented in 30 bits (23bit frac,
6bit exp, and 1 bit sign), then the original string version of the
number was stored.  Now AGCOMP will also try fixed point scaled integer
based on INT23BITVALUE/1000. To store this in place of a 30 bit floating
point value, it uses the invalid exponent of 0 with sign of 1. This allows
common base ten values to be stored more accurately without resorting to
storing the original string version.


AGCOMP now generates BASECMD encoding for all the measurement commands
including:

  centimeters
  inches
  millimeters
  percentage
  picas
  pixels
  pixelsx
  pixelsy
  points
  size

This allows these commands to take up one less 32bit word each use
when encoded into compiled AGC file. Also allows for more complex
compound commands (like 12.5pct being stored in a single 32bit word).


AGCOMP when combining a constant with a BASECMD used to only support a
signed 23bit integer. Now it supports a 21bit intger, with flags for
scaled integers (divided by 1000), and for a leading tail. This allows
an expression like 12.5pct, which compiles into (12.5 topct) to be
encoded as a single 32bit word. Previously it would be encoded as
pushtail, pushnumber 12.5, call cmd_topct. Three 32bit words.


All these changes mean that any AGC files compiled with older versions of
AGCOMP may not play correctly in the new AGPLAY runtime.

Also AGC files compiled with this new version of AGCOMP absolutely will not
play correctly with older AGPLAY runtimes.

----------------------------------------------------------------------------

Reply via email to