Special:
|
[DAT] (requires LDraw-compatible viewer)
|
Subject:
|
Re: Callout a single part
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Thu, 16 Jun 2005 00:12:28 GMT
|
Viewed:
|
1534 times
|
| |
|
|
In lugnet.cad, Kevin L. Clague wrote:
> In lugnet.cad, Jaco van der Molen wrote:
> > > > This would be useful for decorated parts that are positioned in the model
> > > > so
> > > > that you cannot see the pattern.
> > > > Or parts that are partially "hidden" or that you want to point out
> > > > specifically.
> > > > http://www.hccamsterdam.nl/brick/scans/04000/4482/053.jpg (step 12)
> > > > http://www.hccamsterdam.nl/brick/scans/04000/4482/052.jpg (step 9)
> > > >
> > > > You could do this now with single parts by creating a submodel with the
> > > > one part
> > > > in it, use that submodel as a part and call that out.
> > >
> > > And this works. I use it often.
> >
> > I agree that it does, but I think it is a bit too circuitous. I suppose this
> > is too difficult to implement in LPub
> > For now then making a submodel for each callout with only one part and no
> > step in it, doing it like this makes me (once again) happy :-) Forget I
> > asked.
>
> It just creates an alternate solution for something that I have already
> provided.
>
> >
> > > > I am still looking for a way to do step 8 and 11 in the same example as
> > > > above.
> > >
> > > Why are step 8 and 11 unachievable in the current model of LPub using
> > > sub-models
> > > for callouts? Why do you want a different way to to what you can already
> > > do?
> >
> > Because in step 8 and 11 you see 2 parts floating, but when placed in the
> > model, they are fixed.
>
> I'm wondering if this will work in your higher level model:
>
> 0 BUFFEXCHG A STORE
> 0 LPUB CALLOUT BEGIN
> 1 0 0 0 0 1 0 0 0 1 0 0 0 1 sub.ldr
> 0 LPUB CALLOUT END
> 0 BUFFEXCHG A RETRIEVE
> 1 0 0 0 0 1 0 0 0 1 0 0 0 1 sub.ldr
>
> I'll check it out when I get home...... I don't think the CALLOUT code bothers
> to manage buffer exchanges, so you might be lucky enough to get the desired
> effect. If not, I'll see what I can come up with.
This worked very well. I have this for my sub-model:
0 New Model
0 Name: single-arrows.ldr
0 Author: MLCad
0 Unofficial Model
1 8 0 8 0 0 0 -1 0 1 0 1 0 0 3023.DAT
1 8 0 -72 0 0 0 -1 0 1 0 1 0 0 3023.DAT
0 MLCAD ARROW 8 0 -16 0 0 0.707107 -0.707107 -1 0 0 0 0.707107 0.707107 10 4 12 40 3 30 1 2 0 0
0 MLCAD SKIP_BEGIN
3 0 0 -4 0 -3.53553 -19 -3.53553 0 -14 0
3 0 0 -4 0 3.53553 -19 3.53553 0 -14 0
3 0 0 -14 0 -1.41421 -16 -1.41421 1.41421 -16 1.41421
4 0 -1.41421 -16 -1.41421 -1.41421 -56 -1.41421 1.41421 -56 1.41421 1.41421 -16 1.41421
0 MLCAD SKIP_END
And this for my higher level model:
0 New Model
0 Name: single-callout.ldr
0 Author: MLCad
0 Unofficial Model
0 BUFEXCHG A STORE
0 LPUB CALLOUT BEGIN
1 0 0 0 0 1 0 0 0 1 0 0 0 1 single-arrows.ldr
0 LPUB CALLOUT END
0 BUFEXCHG A RETRIEVE
0 LPUB PLI BEGIN IGN
1 8 0 8 0 0 0 -1 0 1 0 1 0 0 3023.DAT
1 8 0 0 0 0 0 -1 0 1 0 1 0 0 3023.DAT
0 LPUB PLI END
Kevin
|
|
Message has 1 Reply:
 | | Re: Callout a single part [DAT]
|
| (...) Right. This indeed works. However it does not seem to work in an MPD file. Render this: 0 New Model 0 Name: single-callout.ldr 0 Author: MLCad 0 Unofficial Model 0 BUFEXCHG A STORE 0 LPUB CALLOUT BEGIN 1 0 0 0 0 1 0 0 0 1 0 0 0 1 (...) (20 years ago, 16-Jun-05, to lugnet.cad)
|
Message is in Reply To:
| | Re: Callout a single part
|
| (...) It just creates an alternate solution for something that I have already provided. (...) I'm wondering if this will work in your higher level model: 0 BUFFEXCHG A STORE 0 LPUB CALLOUT BEGIN 1 0 0 0 0 1 0 0 0 1 0 0 0 1 sub8callout.ldr 0 LPUB (...) (20 years ago, 15-Jun-05, to lugnet.cad)
|
9 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
|
|
|
|
