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 / 5527
5526  |  5528
Subject: 
Re: Searching for parts
Newsgroups: 
lugnet.cad.dev
Date: 
Wed, 8 Nov 2000 09:46:10 GMT
Viewed: 
5071 times
  
In lugnet.cad.dev, Steve Bliss wrote:
> In lugnet.cad.dev, Lars C. Hassing wrote:
> > It doesn't matter whether subfile A.DAT references B.DAT or not.
> 
> Does it matter if C.DAT references B.DAT *before* referencing A.MPD?  This
> would change the example to:
> 
> > > A.MPD:
> > > 0 FILE A.DAT
> > > 1 16 0 0 0 1 0 0 0 1 0 0 0 1 B.DAT
> > > 0
> > > 0 FILE B.DAT
> > > some stuff
> > > 0
> > > 
> > > B.DAT:
> > > some other stuff
> > > 0
> > > 
> > > C.DAT:
> > > 1 16 0 48 0 1 0 0 0 1 0 0 0 1 B.DAT
> > > 1 16 0 0 0 1 0 0 0 1 0 0 0 1 A.MPD
> > > 0

Yes, it does matter. L3P/L3Lab give you a warning
  SKIPPING "a.mpd" Line 4: FILE b.dat already read: 0 FILE B.DAT
and 'some stuff' gets treated as part of file A.DAT.
So here 'some other stuff' and 'some stuff' get drawn.

> > An MPD should be regarded as a collection of files which is automatically
> > unpacked before loading, so the scope is public.
> 
> That makes sense, and is simpler to implement.  And could even be useful,
> under certain circumstances.
> 
> > I would have preferred the scope to be private...
> 
> For MPD, I don't agree.  But I feel there needs to be a follow-on to MPD,
> designed specifically to support submodels within a single model file.  It
> should give consideration to issues of scoping and visibility.

Right, my concern was the ability to compose a Datsville DAT file with
references to many MPD files submitted by contributors.
It should be OK for two authors to use the same subfile name,
e.g. "roof" in my example: http://news.lugnet.com/cad/dev/?n=4188
/Lars



Message is in Reply To:
  Re: Searching for parts
 
(...) That's what I assumed. (...) Does it matter if C.DAT references B.DAT *before* referencing A.MPD? This would change the example to: (...) That makes sense, and is simpler to implement. And could even be useful, under certain circumstances. (...) (26 years ago, 7-Nov-00, to lugnet.cad.dev)

10 Messages in This Thread:



Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

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