 | | Re: Use of arbitrary elements with LSynth
|
|
(...) I'll have to scope it out. (...) :^) by your ownb admission you have more experience than me, because I've never done it at all! If you would please I would be eternally gratefull. Kevin (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) You read undocumented code quite well! (...) Yup. But unfortunatly you want to combine open things (tubes) with closed loops (bands), and the program is fundamentally *not* written for that. Bummer. (...) Will the element do for now? Maybe we (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) I think I'll email it to you first this time. It looks like I must have implemented some of the changes mentioned in this thread here. (URL) a fix for the UPPERCASING bug and some stuff for UNITS, LENGTH and subfile NAMEs, but I don't remember (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
"Larry Pieniazek" <lpieniazek@mercator.com> wrote in message news:HDrH7u.1FKp@lugnet.com... [ ... snipped ... ] (...) You can get a full complemnt of Unix utilities for your PC (including Make) by installing Cygwin (which is free): (URL) It has a (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) OK, I did a little digging. If I understand what I am reading, the various types of things that can be synthesized are defined with constants in the lsynth.h include. Elsewhere in the code these constants are checked (driven by what's found in (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) Letting me peek at the changes would be cool, but feel to check it in. (...) Will you package a source release please? (...) Thanks, Kevin (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) I'm not sure. What are you trying to do? If just you're looking to browse the code, then follow the "Browse CVS" link near the bottom of the page at the URL given above. If you want upload changes to the code you'll have to get a CVS program (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) I found the code (I was looking for released files, not in the CVS tree) and have extracted it (via WinCVS) to take a look... (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Preview of multi-level callouts complete with pointers
|
|
<snip> (...) things (...) seperators (...) I wanted to point out that the callout facilities (which I am starting to think of as step layout facilities), is all *post* POV production work, which means it is instantaneous compared to POV time. Making (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Preview of multi-level callouts complete with pointers
|
|
<snip> (...) things (...) seperators (...) I wanted to point out that the callout facilities (which I am starting to think of as step layout facilities), is all *post* POV production work, which means it is instantaneous compared to POV time. Making (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) Sorry, not intending to shame you. You are looking in the right place, but I'm a neophyte on source forge. Don, what have I failed to do? Thanks, Kevin (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) Ya. I have made good use of LSynth for hoses and for rubber bands in my current project and found it easy to use so I'm definitely interested in using it!!!! (...) OK, well maybe you've shamed me into taking a look. I just went to sourceforge (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) If I recall, it was Kevin's lack of time that prompted him to open up the lsynth code and solicit your help. (I think he may have mentioned you specifically ;) Also, I imagine you could argue that contributing to lsynth satisfies requirement 3 (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) flex (...) I assume the lack of interest is in the coding, not the using :^) I have a similar lack of time. Kevin (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) That was the intent of the minimum requirements. I'd like this to be as open as possible too, without risking the integrity and competency of the decision making body by allowing someone to walk in off the street and get in. (...) Yep. I'm (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) Except for time/skill/interest. (mostly time) (...) I'm thinking that just allowing for a level of indirection might do the trick. If you added a way to just specify what part you wanted used for the stringing together, and allowed it to be (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) I agree that the slots should be open to everyone but I'd like to weed out those who are the "rainy day" LDrawers. In other words, you need to have proven your competency and commitment. We could go on and on about what qualification someone (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Right. The proposal is set up in such a way to encourage everyone - programmer or not - to discuss the issues publicly. When it comes to making decisions, a limited group of qualified people (in this case, programmers, parts authors, or (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) I agree, 100%. I think we should have more representation from the programming side of the community. :) Dan (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
I'm going to snip out the stuff I'm not going to comment on (...) I like this distiction. Now we can concentrate on forging a new path without having to worry about legacy DOS programs (...) I like this idea of having qualified members. You are (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Preview of multi-level callouts complete with pointers
|
|
(...) I was thinking more about this (and I've asked Miguel to help me with the resolution independent architecture of the new LPub features), and there are two *different* issues here. Issue 1: I want to render everything in low resolution (to save (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) Absolutely! Good point! (...) Kevin (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) But since you've made the source for lsynth available, there's no reason why Larry couldn't attempt to add the string part to the code himself and then submit the patches to you for official approval. Right? Isn't that the whole point of (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) Not currently. (...) Thanks for buying the book. You are right, it does not cover this. Currently LSynth only supports either open ended or closed loop. No mixing. (...) Yes. It would. There are a *number* of things it cannot do.... yet! (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Use of arbitrary elements with LSynth [DAT]
|
|
Kevin I've created an element that represents a small segment of string. It's not a real, legitimate LDraw part, per se, but I find it useful in my modeling. Is it possible to get LSynth to use this element? I'm looking for it to be treated similar (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Preview of multi-level callouts complete with pointers
|
|
(...) Well I guess the above "ascii draw" diagram didn't work too well with proportional fonts. Oh, well. (...) Per Jennifer Clark's recommendation in private, I'm going to convert the pointer units from pixels to scaling factors from 0 to 1, where (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev, lugnet.inst)
|
| |
| | Re: Some more LPub errors?
|
|
(...) Fixed. (...) Found it in part list image rendering, thanks. Fixed it. (...) I think that in the case of LSynth I can make this happen, but otherwise I think this is going to have to be left as "an exercise for the student". (...) Kevin (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub request
|
|
(...) I've modified LPub to ignore submodel parts as well as primitives when making PLIs and BOMs. To address your request more specifically... LPub would have to look for pairs of s/faxel1 through s/faxle5 and automatically substitute. I'd prefer (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Thanks, Kevin. I'd like to see some good discussion on this here before moving on it. Does anyone have any comments, concerns? (...) Thanks! I couldn't have put that together without you, the others we were mailing with, and the community (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) <snip> Thanks for all your efforts Tim. Lets get started! I appreciate all the hard work you put in on this. Lets put it to good use. Kevin (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) <snip> This is great stuff. Thanks, Tim for pushing this forward, others contributed, but you certainly did a great job including everyone's comments and pulling together a cogent draft proposal for the LSC. I plan to stand for election to it (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
Looks like you guys have spent a lot of time thinking about how to go about this in a fair and equitable way, very comprehensive. It feels a lot like the way standards are created in the high-tech world which benefits everyone! This is a great time, (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Some more LPub errors?
|
|
"Kevin L. Clague" <kevin_clague@yahoo.com> skrev i meddelandet news:HDpArM.n2J@lugnet.com... (...) the (...) Why not have an invisible LDRAW part with color, just like the LIGHT.DAT? -- Anders Isaksson, Sweden BlockCAD: (2 URLs) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Resolution
|
|
When authoring new elements, how important is the level of detail in LDraw format? That is, for more complex curves and surfaces, is it necessary to get as close to the real thing as possible? As an alternative, is it acceptable to get pretty close (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Preview of multi-level callouts complete with pointers
|
|
(...) The callouts are placed relative to outside edges or corners of the step image: Corners: TOP_LEFT TOP_RIGHT BOTTOM_LEFT BOTTOM_RIGHT Edges plus justification to the perpendicular edges TOP (LEFT, CENTER or RIGHT) BOTTOM (LEFT, CENTER or RIGHT) (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev, lugnet.inst)
|
| |
| | LDraw.org Standards Committee (LSC) Draft Proposal
|
|
As Orion posted earlier today, let's revisit the LDraw.org standards body idea. [1] Here is the draft proposal I mentioned earlier today on LUGNET. I'm posting it here for everyone to discuss. Several weeks ago, I worked with Kevin Clague, Larry (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev.org.ldraw, lugnet.cad.dev) !!
|
| |
| | Re: Preview of multi-level callouts complete with pointers
|
|
Hi Kevin, You've done it again! This is a HUGE improvement as it allows a much needed "step hierarchy", extremely useful for generating instructions - your step 0 is actually two steps. This is really great. I am probably being too inquisitive too (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Some more LPub errors?
|
|
(...) edges (...) Ah, this is different than what you first described. LPub tries to ignore primitives when making PLIs and BOMs. I wonder why it missed these. I can recommend a work around: PLIST BEGIN IGN PLIST END Kevin (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Some more LPub errors?
|
|
(...) I did that already just to make sure and got no error. Here's some more info I've found troubleshooting This error seems to occur when LPub thinks the X-Xedge.dat primitive are parts for the Construction Images and BOM. In other words LPub (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Some more LPub errors?
|
|
(...) Please try to run lpubtest.dat through L3P manually. I do not have a way to continue if L3P finds an error in the file. You may need to talk to Lars about this one. Kevin (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
