Lars,
I don't have the VM-SDK manual :), but looking at the MB declaration:
Declare Function vmVoronoi Lib "vmTIN.dll" (pszTRIFile, pszTableName, psz3DpointsName
As String, ByVal lHullMode As Integer, ByVal dHullMargin As Float, ByVal
dwFunctionMethod, ByVal lDissolveMode As Integer, ByVal dBoundarySmoothness As Float,
pstRegionStyle As REGION_STYLE, pszBoundaryTabName As String, ByVal dwBoundaryRowID As
Integer, ByVal ProgressUpdate As Integer) As Integer,
I believe it is the psz3DpointsName variable your talking about. The psz3DpointsName
look a lot like psz3DPointFile. The psz3DPointFile is just a binary "workfile" used by
VM. I.e.you will not need 3D data to build 2D Voronoi polygons, remember VM is not a
real 3D application. VM calls it 3D because the variable holds a x,y and some third
value.
HTH,
Jakob
{
The MapInfo 3D Experiment
Lanstorp Consulting
http://www.lanstorp.com
}
Has anyone used the Vertical Mapper (2.6) SDK for generating Voronoi polygons
programmatically ?
I'm curious about the parameters to the vmVoronoi function. Is seems that it needs 3D
data to build inherently 2D Voronoi polygons.
Why is that ?
Is it really true / necessary, or is it a documentation error ??
I'm using MIPro 6.5, and using 7.0 is not an option.
