Results (1 - 5 of 5)
- [7239]: Merge trunk changeset 7238 into adsk/2.4k branch stream. This is for ...
- ... 4k branch stream. This is for ticket #2192 (MgMultiGeometry::Deserialize doesn't work with MgAgfStream).
- By 11/30/12 12:46:07 —
- [7238]: Fix #2192 (MgMultiGeometry::Deserialize doesn't work with MgAgfStream) ...
- Fix #2192 (MgMultiGeometry::Deserialize doesn't work with MgAgfStream) I've updated the code in MgGeometry::Deserialize which peeks for the geometry type to account for the type of the passed-in MgStream. Only if it's a pure MgStream do we use the ...
- By 11/30/12 12:03:14 —
- #2192: defect: MgMultiGeometry::Deserialize doesn't work with MgAgfStream (closed: fixed)
- The following code currently fails: {{{ Ptr<MgMultiGeometry> geom = ...; MgAgfReaderWriter agfReaderWriter; Ptr<MgByteReader> reader = agfReaderWriter.Write(geom); Ptr<MgGeometry> multiGeometry = agfReaderWriter.Read(reader); }}} The MgAgfReaderWriter::Read call ...
- By 11/30/12 11:21:34 —
- [3502]: Fix #788 (MgCurvePolygon::Serialize & Deserialize handle inner rings ...
- ... This uncovered an additional bug in MgMultiGeometry:::Deserialize. In the non-tcpip-stream case it peeks at the stream to get the geometry type (a hack), and the code doing the peek was wrong. To get the geometry type from the stream you have to read the entire packet, and ...
- By 12/10/08 09:25:16 —
- #287: defect: wrong type of the buffer of more than one geometries (closed: wontfix)
- ... and then I make a MgMultiGeometry based on the MgGeometryCollection of these selected geometries, and then I make a buffer of this MgMultiGeometry. Theorectically, if these selected geometries are very close, the buffer geometry should be a single polygo ...
- By 10/15/07 06:06:28 —
Note:
See TracSearch
for help on searching.