[Plib-devel] ssgVtxArray fixes.

[Steve B. <sjb...@ai...>]

I've fixed a small mountain of errors in ssgVtxArray - there seemed to
be one underlying problem...

   ssgVtxArray::getTriangle

...should have been written specially for ssgVtxArray to do the index array
translation to underlying vertex numbers - but was in fact returning entries
into the index array.

Once that's fixed, several of the other functions that had to be written
uniquely for ssgVtxArray can now fall back to the ssgVtxTable implementation.
(There were comments in ssgVtxArray.cxx suggesting that this would be A Good Thing -
and it is!)

So, that's all committed.

Is there some reason why the index array is an array of 'int'?  Since the underlying
SSG classes don't allow more than 32k vertices/normals/colours/texcoords per leaf
node - it seems unlikely that this would be needed - and there are certainly speed
improvements to be had from using a 'short' index array.

Anyway - could someone who uses ssgVtxArray please try it out and let me know
if I broke something.

-- 
Steve Baker   HomeEmail: <sjb...@ai...>
              WorkEmail: <sj...@li...>
              HomePage : http://web2.airmail.net/sjbaker1
              Projects : http://plib.sourceforge.net
                         http://tuxaqfh.sourceforge.net
                         http://tuxkart.sourceforge.net
                         http://prettypoly.sourceforge.net