Another odd behavior - a shapefile that displays in the MapWin viewport returns 1 when the property Shapefile.NumShapes is accessed. Needless to say, it has more than 1 polygon. However, another shapefile that only has 2 polygons returns the correct number, which in this case was 2.
Is there a limitation in the Shapefile class where it cannot handle multipart geometries? This may account for much of the bizarre, nonfunctioning behavior that I have been experiencing.
Is there a limitation in the Shapefile class where it cannot handle multipart geometries? This may account for much of the bizarre, nonfunctioning behavior that I have been experiencing.
