Number of coordinates returned by getVtxArrCoords

[Carl Ollivier-Gooch]

Hello, all.

Ting sent me an email asking why a 2D mesh is required to return three 
coordinates for every vert from this call.  So I went trolling in the 
email archives, and found that the most recent discussion we had of this 
(at least in email) was last April.  Summarizing that discussion, 
hopefully correctly:

Mark Miller:  Prefers that we specify one or the other, with a 
preference towards two coords for the 2D case.

Carl and Karen:  Prefer that we specify one or the other, with no 
particular preference between 2 and 3 coords in 2D.

Tim:  Prefers to leave this implementation dependent.

Given that status, I propose the following as a (near) consensus:

getVtxArrCoords will return two coords per vertex in 2D and three in 3D 
(that is, the number of coordinates returned will be num_verts_returned 
* geom_dim).  Unless I hear violent objections in the interim, I'll 
update the docs (and unit test) Friday morning.

Carl

-- 
------------------------------------------------------------------------
Dr. Carl Ollivier-Gooch, P.Eng.                   Voice: +1-604-822-1854
Professor                                           Fax: +1-604-822-2403
Department of Mechanical Engineering             email: cfog at mech.ubc.ca
University of British Columbia              http://www.mech.ubc.ca/~cfog
Vancouver, BC  V6T 1Z4                  http://tetra.mech.ubc.ca/ANSLab/
------------------------------------------------------------------------