In the draft "BRL-CAD Database Format" there is mention of perhaps
having a registry of attributes so as to declare publicly use of
certain key words, e.g., 'MUVES_component' which is being used in the
AJEM community.

Has there been any work in that direction, or is that not feasible or
desired now?

<ramble>

We had a discussion some time ago about air codes, region IDs and such
and I don't remember what the final resolution was, but I notice
"default" attributes in the output files from g2asc on old TGMs show
something different than red on the same TGM in .g form.  In
particular, in the old TGMs air is zero by default.  In asc form {air}
doesn't show at all for those old TGMs without an air code explicitly
set but edcodes still shows that value as zero while red shows null
for air.

By referring to the asc form (and confirmed by red) It looks like the
current "standard" attributes (those shown by attr) are:

  region
  region_id
  material_id
  los

I guess for old TGMs I can still interrogate the hard-wired struct
region variables:

    int                 reg_regionid;   /**< @brief Region ID code.  If <=0, 
use reg_aircode */
    int                 reg_aircode;    /**< @brief Region ID AIR code */
    int                 reg_gmater;     /**< @brief GIFT Material code */
    int                 reg_los;        /**< @brief approximate line-of-sight 
thickness
equivalence */

But I have to say I like the ease of using attr these days--much
easier than the original methods.  And on new TGMs I am making good
use of attr--hence the question about a standard registry for those of
us who are  in the business of exchanging TGMs.

</ramble>

Regards,

-Tom

Thomas M. Browder, Jr.
Niceville, Florida
USA

------------------------------------------------------------------------------
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

Reply via email to