David Thompson:
|> globals->Globe = _dxfCreateRotationInteractor (W, tdmGlobeEcho, 0) ;
...
|> typedef enum {tdmXYPlaneRoll, tdmZTwirl} tdmRotateModel ;
|
|Well, in c, wouldn't 0 be relative to tdmXYPlaneRoll?
That's what it's mapping to now. But I assume either the function
interface has changed since the implementer put this zero in, or the
implementer was just being careless. In either case it seemed worth a
double-check. I put a tdmXYPlaneRoll until someone tells me different.
|I've found lots of places in the code where initialization was done by
|just setting things to zero or worse NULL when that wasn't the
|appropriate type. I've tried to fix a lot of them when possible and did
|this by assigning what the compiler would have assumed 0 or NULL is.
Good. I've been cleaning some similar spots recently. One I found
this morning was using a (int *)1 pointer alongside NULL and other random
pointer values to indicate a special marked no-data condition -- that's
history (or rather, it will be tonight).
Randy
--
Randall Hopper (mailto:[EMAIL PROTECTED])
Lockheed Martin Operation Support
EPA Scientific Visualization Center
US EPA N127-01; RTP, NC 27711
