Subject:
|
Re: Latest BFC Spec?
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Thu, 20 Mar 2003 05:32:02 GMT
|
Viewed:
|
671 times
|
| |
|
|
In lugnet.cad.dev, Kyle McDonald writes:
> I also think it's not the best idea to trigger different behavior
> based on what directory a DAT file is located in. I think some sort
> of flag in all part files would be useful. However I'm not sure (and
> I haven't looked yet) that there isn't already some Flag we can key
> on without adding another BFC level meta-command.
>
> Is there a line in the header already that declares that file is
> a 'Part' or a 'Primitive' ??
There are currently a number of flags that indicate that a file is a part.
The official one is only present in files that have been updated since it
was made official. However, this isn't a problem, since any BFC-certified
part is guaranteed to have the indicator.
The thing is, it might make sense to force BFC on in a file even when it's
not actually a part. I can't think of anything off-hand, but it seems to me
that a command that forced BFC to be on would handle all possible cases,
whereas treating parts as special would only take care of parts.
As a matter of fact, once I do get BFC working in LDView, my behavior will
indeed be triggered by whether or not LDView considers a file a part, and
not by what directory the file came from. I do parse the meta-statements
that indicate a file is a part.
--Travis Cobbs (tcobbs@REMOVE.halibut.com)
|
|
Message is in Reply To:
 | | Re: Latest BFC Spec?
|
| I saved this thread for later reading, and I've got a few questions now. Sorry if I'm resurrecting something everyone thought was dead :D (...) Once the parts library is fully BFC certified, will there ever be a need to use CLIP or NOCLIP? I'm not (...) (21 years ago, 20-Mar-03, to lugnet.cad.dev)
|
38 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
