The Datafile PD-CD 5/DATAFILE_PDCD5.iso/utilities/p/povray2/ReadMe

Text File | 1994-11-13 | 5.4 KB | 96 lines

POVray2 Setup Version 1.12  -  July 1994
==========================

This fixes a couple of 'anomalous features' (read bugs) which were present
in Version 1.11 (the first release version). These are:

1.) In version 1.11, an error 'Bad filename .xxx at code 7670' was produced
if you deselected the save box option, and specified a system variable which
hadn't been defined in the 'Path' submenu. Since I supplied the program with
the default path set to <POVpicture$Dir> (which was defined during the boot
up sequence on my machine - see below), this error will almost certainly
have been produced if you tried to use version 1.11 in non-save-box mode
without first setting the path to something sensible (Using 'Save defaults'
from the icon bar menu will save your choice of destination path name).
Version 1.12 now checks the destination path name when 'Start' is clicked,
and will produce a warning if it is in non-save-box mode and the destination
path name is undefined/invalid (error 'Invalid desination path name' is
reported. This reflects the problem better than the rather enigmatic error
above). Also, non-existent destination directories are detected, and this is
also reported. Thanks to everyone who brought this one to my attention!

2.) Whilst fixing the above, I noticed the rather inconsistent behaviour of
the Path submenu itself. In version 1.11, if you had 'Use save box'
selected, then entered text into the path submenu, the 'Use save box' option
would be deselected, and the 'Path' menu item would be ticked. This is as
expected. If, however, you then changed the text in the submenu, the 'Path'
menu item would be deselected (i.e. its status was toggled). This obviously
should not happen, and has been fixed in version 1.12 (i.e. the 'Path' item
now remains selected when the text is changed, until you actually click on
the 'Path' item itself, or select 'Use save box'. This is what should have
happened originally.

3.) Version 1.11 had a rather restrictive limit on the maximum length of the
path and library names. This has now been increased.

POVray2 Setup Version 1.14 - October 1994
==========================

This version fixes a bug present in previous versions which prevented the
continue option from working, and allows loading of POV scene files
(filetype &376) by double clicking. Again, thanks to everyone who reported
this bug, and suggested the fix for it!

The !!Scenes directory
======================
As I mentioned above, the <POVpicture$Dir> system variable was always set on
my machine. This was done by the !!Scenes directory, which exists solely to
do this, and also to set up the #include library directory (note: it
expects the #include files to be in a directory called 'inc' which itself
is in the same directory as the !!Scenes application, i.e. 'inc' should be
in the same filer window as !!Scenes), and provide somewhere to store the
output scene files (obviously!). Since this was always present in my
machine, I didn't notice problem number 1 above until told about it! I had
meant to include !!Scenes in the first release (1.11), but I forgot....
Anyway, it's here now. It is, of course, completely independent of the POV
front end, which is in no way reliant upon it (other than to set up the
system variables, if you use them), and it's up to you if you want to use it
or not. Double click on !!Scenes to open the output scenes file directory.


Compatibility
=============
I've tried two versions of the executable on the front end. Version 2.0
(compiled by Pete Goodwin), obtained from HENSA appears to work properly,
but does appear to contain a number of bugs, notably that the library
option does not work, and neither, it seems does the continue option.
Version 2.2 (compiled by Adam Hamilton) is free from bugs, but expects the
format of #include lines to be Unix or DOS standard
(eg #include "colors.inc"). Whilst this makes porting of pictures from other machines easier, it seems a little unexpected when using scenes you've
created yourself - you have to say things like
#include "colors.<POVinc$Dir>.inc" if you've set <POVinc$Dir> as your
include directory, which is a bit confusing if you're used to Acorn
convention, although it does increase the portability of your scenes. Also,
using 2.2, in the library option, you must specify the directory which
contains the inc and gif etc. directories, rather than the directories
themselves (does this seem obvious? I suppose it does now, but it certainly
caught me out!).

I think the best way of using V2.2 is to have your include files in a
directory called "inc", and place this in the same directory as !!Scenes,
which will then set <POVinc$Dir> to point to it (as detailed above). Then,
make sure the 'Library' submenu of !POVray2 is set to '<POVinc$Dir>' (it's
already set to this by default as supplied). Then, just use #include
statements such as "#include colors.inc", and leave the library option
to take care of it.

On the whole, having been used to earlier versions of
POV, I think I prefer V2.0's way of accepting Arc style input, but this is,
of course only my opinion, and in any case I don't think you can get hold
of this version any more. You also have to accept the failure of the
library and continue options (at least, I think they are bugs - correct me
if I'm wrong on this). Version 2.2 also, I think, has some improvements in
the rendering algorithms, so on the whole it's probably worth using this
version....

Brian Ruth ([e-mail])