To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 8535
8534  |  8536
Subject: 
Re: Latest BFC Spec?
Newsgroups: 
lugnet.cad.dev
Date: 
Sat, 22 Mar 2003 00:26:29 GMT
Viewed: 
826 times
  
In lugnet.cad.dev, Travis Cobbs wrote:

This actually brings up the point (that may have already been brought up and
rejected when BFC was discussed years ago) that it would make sense to have
a force flag that would force certification on even when your parent is not
certified or clipping has been disabled.

I could kind of see that, but not in the parts library.  I would expect
that any file in the library that specifies NOCLIP does it for a good
reason, and should not be overrode (overridden?).

What I could maybe see in the parts library is a 'force on if it's not
specified' option.  So if a parent file has NOCERTIFY, this type of force
on wouldn't do anything.  But if the parent has no BFC statement at all, it
would.

That way parts wouldn't have to be treated as special cases by the renderer.
The BFC spec already says in the implementation section that the renderer
should pretend that all superfiles are certified when it processes a part.
A flag like FORCE-CERTIFY (or somesuch) would remove this special case.

But then all parts would need to have the FORCE-CERTIFY setting.  Which
would be another statement/option for the renderer to handle, and another
flag for the renderer to track.  It makes as much sense to check whether
the file is a part or not, and default CERTIFY/NOCERTIFY accordingly.

Steve



Message has 1 Reply:
  Re: Latest BFC Spec?
 
(...) I hadn't thought about NOCLIP. (...) I think that FORCE would be more useful if it overrode NOCERTIFY, but not NOCLIP. When you say NOCERTIFY, you're saying you don't know how the file should be culled. When you say NOCLIP, you're saying you (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)

Message is in Reply To:
  Re: Latest BFC Spec?
 
(...) This is really no different from the fact that the incoming certify state has to also be on. So a subfile won't be BFC'd unless all its parents are certified and it is certified as well. Also, presumably if you refer to a subfile in a section (...) (22 years ago, 13-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

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR