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 / 9023
9022  |  9024
Subject: 
Re: Mirrored parts and studs
Newsgroups: 
lugnet.cad.dev
Date: 
Wed, 2 Jul 2003 06:49:11 GMT
Viewed: 
3207 times
  
In lugnet.cad.dev, Steve Bliss wrote:
> In lugnet.cad.dev, Orion Pobursky wrote:
> 
> > 1.)  Nothing is wrong with the part.  The stud logos are added by an external
> > program and are not part of the DAT code.  This is, therefore, a limitation of
> > the external program and not of the part itself.
> 
> That is my opinion.  The programs should be changed, rather than the
> parts.
> 
> One thing to consider: even if we 'fix' all the part files so that all
> studs render non-mirrored logos, mirrored logos can still occur.  For
> example, if someone created a left-hand wing for an airplane, they might
> make the right-hand counterpart via a mirrored reference to the left
> wing:
>  1 7 0 0 0 1 0 0 0 1 0 0 0 1 leftwing.ldr
>  1 7 0 0 0 -1 0 0 0 1 0 0 0 1 leftwing.ldr
> In this scenario, L3P will render mirrored logos on the right wing's
> studs.
> 
> However, I'm willing to go with the idea outlined by Chris and Dave!  I
> think that is a reasonable compromise, despite what I said in the past
> about extra work and extra subfiles.
> 
> Also, if we're going to add any meta-statement (as Tore suggested), how
> about adding a single statement for the file header:
>    0 STUDSGOTHISWAY  0 0 1
> where the three parameters give a vector, indicating the 'up' direction
> for stud-logos.  That way, rendering programs could fix mis-rotated
> studs, as well as fixing mirrored studs.
> 
> > I'm axious to get a resolution on this since many otherwise good part are being
> > held up because of this issue.
> 
> I definitely would not hold a part because the studs aren't all lined
> up!
> 
> Steve

My only concern about letting the rendering programs do this is "how they know
which way to orientate the logo". Coding this within the .dat file (either with
a correctly orientated stud.dat or with metadata) is preferable to storing this
information in some other place and dispersing "Lego part" information in
several repositories.

I rarely (if ever) include a check for stud orientation in my parts review.

IIRC the 16x32 baseplates exist in two forms - with the Logo either aligned with
the long side or with short side. I would NOT be keen to have a part variant
just for this (non-functional) feature.

Chris



Message is in Reply To:
  Re: Mirrored parts and studs
 
(...) That is my opinion. The programs should be changed, rather than the parts. One thing to consider: even if we 'fix' all the part files so that all studs render non-mirrored logos, mirrored logos can still occur. For example, if someone created (...) (23 years ago, 2-Jul-03, to lugnet.cad.dev)

25 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