Now that we have asc2g and g2asc working reasonably, I took a look
at the import/export of ASCII files in MGED. The export simply runs
g2asc, so produces the same result as running g2asc. The import,
however, runs asc2g, then dbconcats the result into the currently open
db. By default, dbconcat ignores the _GLOBAL object; so title, units,
and color table do not get imported. This seems entirely reasonable when
the import is actually concating into an existing db that already has
stuff in it. But if we are importing into an empty db (i.e., title ==
"Untitled BRL-CAD Database", units == "mm", no color table, and no other
object in the db), perhaps we should also import the _GLOBAL object
attributes. Or maybe or slightly more complex set of rules, or user
input, should determine what parts of the _GLOBAL object get imported.
Any thoughts??
-John
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel