 | | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) I'm sorry for the confusion here - Lar corrected me offline on the definition of 'subcommittee' (which technically typically means members drawn from the parent body [1], not the intent here). I didn't mean to imply that the 4+1/steering (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Resolution
|
|
(...) Hi Steve-- Thanks for taking the time to answer so thoroughly. All I can say is that I'm glad I'm not modelling official elements! Clone brands have quite a few odd cones, arcs, and domes that just don't fit the official primitives, and if I (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Yep. Steve and I have talked before about a voting mechanism. Basically, anyone who signed up to vote can vote. This mechanism hasn't been set up yet, but it can be discussed and set up in the relative near future - according to the proposal, (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Everyone who is interested in LDraw related stuff is part of the community. The LDraw community has some official organizations like LDraw.org and soon to be the LSC. It is my understanding that anyone who wants to vote for the nominees (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Me either. Snipped the next bit because it's a good summation of the roles... (...) And thanks muchly for that! progress on overall org goals had stagnated. a good sharp poke was a good thing. <more snippage> (...) What I think Tim meant here (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) hmm ... probably it's due to a non-proper knowledge of the english language but now I'm even more confused! as far as I understand we have Ldraw members, which are not part of the community, community members which are not Ldraw members, (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) [snip everything else, good stuff] I think I wasn't clear enough. As you read it, I don't agree either. I meant - this proposal is yet another catalyst to the issue of further organizing and defining LDraw.org. It isn't the LSC's job, but the (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) I don't think that what Kyle is describing is what I have in mind. LDraw.org is the natural group to designate that their will be an LSC committee. The committee is made up of "technically qualified" members. Only members of LDraw.org that are (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) formats. (...) ... (...) I interpret the "set in stone" statement to refer to the language as defined in 027 version of LDraw/LEdit. It is my belief that all the nuances (nucances :^) you mentioned should be described in the 0.27 document. The (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
In lugnet.cad.dev.org.ldraw, Tim Courtney writes: hi tim, (...) could you please sort this out in more detail? does it mean that the "Ldraw.org" file format will support, say 256 colors, no longer required to put dithered colors in subfiles, "set in (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) I think this looks very comprehensive - and I think the idea of choosing a small group of dedicated people to actually take the proposal forward is the way to go. I think this proposal is definitely a step in the right direction. ROSCO (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Resolution
|
|
(...) For general features, the standard rule of thumb is to model details which are 1LDU or larger. To cleanly model some features, you certainly can run into decimal places -- I typically go to 2 or 3 decimal places in part files. Any use of the (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Dan, there seems to be some confusion here on your part. Hopefully other posters have cleared it up for you, but I want to go on record here on what the vision was. If it wasn't clear from the proposal, that's at least partly my fault since I (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Sorry, I should have said, "how LDraw.org should function as an organization in the future." -Tim (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) I think you're misunderstanding, perhaps I wasn't clear enough in the proposal. The leaders who set up the LSC are only setting it up, they aren't the initial members of the LSC. These people were self-selected two years ago, based on the fact (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) You're mostly right. I suppose the proposal/message wasn't clear enough (and this is the part I was afraid of it not being clear enough in, so I tried to disclaim it). A couple years ago, the four of us posted this message: (URL) - sometime (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Hi Dan, (...) Unless I mis-read something, I think this initial group of 5 is the (parent organization) LDraw.org's leadership doing double duty as the initial Ldraw.org Stnadards Comitee for the sole purpose of setting up how the Standards (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) right. I was saying that the LSC needs to be qualified (as Orion pointed out), AND that the LSC needs more representation from the programmers. Currently, as far as I can tell, it has (from the stats I could gather): Jacob: parts author, (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) Not to worry, combining things is more of a stretch goal (if you'll pardon the pun). Just one is good enough for now. (...) Maybe that's the way to go. I think actually I would go with Band and then hand edit away the 1/2 (of the synthesized (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) Thanks Mike. Meanwhile I just installed make-3.79.1 and it makes lsynthcp OK without needing to install MSys. Gotta think about whether I want Cygwin or not... it's not like I don't have a bazillion other things I should be working on instead. (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | Re: Some more LPub errors? [DAT]
|
|
(...) Try this: 1 0 0 0 0 1 0 0 0 1 0 0 0 1 stud.dat 1 0 0 0 0 1 0 0 0 1 0 0 0 1 4-4edge.dat A little further investigation reveals that LPub quits on error no matter what the color of the edge. The exact error I'm getting is: 'L3P failed for file (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub request
|
|
(...) The short answer to your question is yes. Ldraw only looks in the PARTS, P, MODELS, or current folder. Two extension folders have been added to faciltate further separation: the PARTS/S folder is for subparts used by parts in the PARTS folder (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Some more LPub errors?
|
|
(...) Example please. (...) Quite possibly. I'll run through all calls to L3P and see what I can come up with. (...) This is a good idea. Jennifer Clark first suggested this for pneumatic hoses. My first throught is to have a special end cap part (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub request
|
|
Hi Orion, Why do we need to have the s\ in the DAT file? I'm probably showing my part definition ignorance here. Is it because LDraw does not know to look in s\? I'll fix the bug in LPub either way. Kevin (...) <snip> (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | LDraw File Format Standard Committee Update
|
|
Now the furor over this topic has died down, here the list of people interested in being a member of the Standards Body: Orion Pobursky Kevin Clague Steve Bliss or Chris Dee Larry Pieniazek Ross Crawford Paul Gyugyi Jacob Sparre Andersen We were (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Some more LPub errors?
|
|
(...) Some more on this, This idea doesn't have to confine to just color coded dots, it could also encompass lengths for pneumatic hoses as well. Maybe an added parameter to the PLIST BEGIN SUB meta command or an extension to LSynth. -Orion (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Some more LPub errors?
|
|
I found two more things that are styming my progress 1. LPub quits on error if a part has a color other than 16 for the X-Xedge.dat primitive. This shouldn't matter since L3P doesn't render edges and colors other than 16 aren't technically illegal (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub request [DAT]
|
|
(...) Even with the PLIST command, I still get a part not in PARTS.LST error unless I turn off the file checking. Here the example: 0 Test Axle 0 Name: Taxle.dat 0 Author: Orion Pobursky 0 Unofficial Model 0 PLIST BEGIN SUB 32199.dat 1 7 -30 -110 (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub request
|
|
(...) Orion, Please provide me with an example? LPub is coded to support parts\s directory. Kevin (...) (21 years ago, 21-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Preview of multi-level callouts complete with pointers
|
|
(...) CUTE!!! and loads of new metas! many thx. w. (21 years ago, 20-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Preview of multi-level callouts complete with pointers
|
|
(...) Thanks Anders! Kevin (...) (21 years ago, 20-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Preview of multi-level callouts complete with pointers
|
|
"Kevin L. Clague" <kevin_clague@yahoo.com> skrev i meddelandet news:HDMB7I.1E3L@lugnet.com... (...) It really looks great! I'd better start creating a MOC, so I have something to test LPub on :-) -- Anders Isaksson, Sweden BlockCAD: (2 URLs) (21 years ago, 20-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub request
|
|
Hi Orion, Go to Building Instructions->Controls and uncheck "Check DAT(s) against Part List". Kevin (...) (21 years ago, 20-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub request
|
|
(...) OK, I used the PLIST BEGIN command and I'm still getting the s/faxle1.dat not found in the PARTS.LST file error. I think (but haven't tried) that this problem will exist for any model that uses file from the /S directory. -Orion (21 years ago, 20-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Preview of multi-level callouts complete with pointers [DAT]
|
|
(...) Here is the top level DAT: 0 Untitled 0 Name: l0.ldr 0 Author: MLCad 0 Unofficial Model 0 WRITE LPUB PLI BORDER ROUND 0 1 10 0 WRITE LPUB PLI MARGINS 20 20 0 WRITE LPUB CALLOUT BORDER SQUARE 0 1 0 WRITE LPUB CALLOUT MARGINS 20 20 0 WRITE LPUB (...) (21 years ago, 20-Apr-03, to lugnet.cad.dev)
|
| |
| | Preview of multi-level callouts complete with pointers
|
|
I wanted to give you a peek at the progress I've made: (URL) is a three level design, with dual level callout images, complete with pointers to show you where the called out sub-assemblies are added. The PLI shows all the parts added at all three (...) (21 years ago, 20-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
Anders and Travis, Thanks so much for all the help. I can hardly wait to switch to PNG support. Bitmaps are lossless, but huge, and JPEG is compact but lossy. It will be great to just use the one format. Kevin (...) (21 years ago, 20-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
(...) I know that Anders already responded to this privately, but I'm posting this in case his response was different. The official PNG library (from the creators of the PNG format) has Borland C++ Builder 5 project files, along with some (...) (21 years ago, 19-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
"Kevin L. Clague" <kevin_clague@yahoo.com> skrev i meddelandet news:HDLAnL.1482@lugnet.com... (...) I sent the one I have found, and used, to your private mail. I use it with Delphi 5, so you shouldn't have too much trouble with C++ Builder 5, which (...) (21 years ago, 19-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | LD4DModeler status
|
|
I feel a little bad about the gigantic pause in LD4DModeler's (members.rott.chello...4DModeler) development. But I have picked it up again, currently I am fixing reported bugs and making the whole application ready to go 1.0 But also the long pause (...) (21 years ago, 19-Apr-03, to lugnet.cad.dev, lugnet.cad, lugnet.cad.ray, lugnet.announce)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
(...) Hi Anders, Yes. I'm using Borland C++ builder 5 and their jpeg unit. (...) Do you know of a Delphi compatible PNG package? I'd *love* to use PNG. Thanks, Kevin (...) (21 years ago, 19-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
"Jaco van der Molen" <jmolen@zonnet.nl> skrev i meddelandet news:HDJ79v.211H@lugnet.com... (...) Kevin, are you using Delphi? And the jpeg unit from Borland? There is a problem with jpeg pictures in the size range 1-2MB if I remember correctly. I've (...) (21 years ago, 18-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LPub 2.1.0.8 Available [DAT]
|
|
(...) Hi Jaco, Thanks for the DAT info on the failing behavior. I found and fixed an LPub bug. You can work around this bug by rearranging your DAT. Here is part of what you sent me, starting at the beginning: 0 STEP 0 ROTSTEP -155 135 0 ABS 1 7 0 0 (...) (21 years ago, 18-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LPub request
|
|
(...) Hi Orion, I recommend that you put a PLIST BEGIN IGN before the s/faxle1 and PLIST END after each s/faxle1. LPub will ignore these parts and not give you an error. Even better, create a stright version of the xale in a seperate dat and use (...) (21 years ago, 18-Apr-03, to lugnet.cad.dev)
|
| |
| | LPub request
|
|
I was trying to get a BOM for a model I did and LPub give me a file not found in the Parts.lst eror and quits. The particutlar error was the s/faxle parts used for the flexible axles. Here's my request: If Lpub detects s/faxle1 though s/faxle5, then (...) (21 years ago, 18-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
(...) Jaco, I need more spefic data than that. If you could quite the error mesage, tell me wheher it was doing construciton images, part list images, callouts or BOMs would help. As always, sending me the dats (and the config.lpb) would help so I (...) (21 years ago, 18-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
While rendering a model I got a JPEG error and LPub seems to stop. What is that error and what can I do about it? Jaco (21 years ago, 18-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
(...) It is supposed to. Can you tell me how you are using it? Buffer exchange and rotation steps used to not work correctly. I talked to Michael and got it sorted out. Maybe now you are expecting it to act like it did when it was broken? (...) (...) (21 years ago, 18-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
It seems that rotation step does not work anymore? (...) levels. This is nice!!! Jaco (21 years ago, 17-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
(...) Thanks Jake. I knew I was forgetting something. Kevin (...) levels. (...) (21 years ago, 16-Apr-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
(Cross posting to .inst) (...) (21 years ago, 16-Apr-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
|
| |
| | Re: LPub 2.1.0.8 Available
|
|
(...) This version of LPub does not support nested callouts, but this is in the works. To make nested sub-model callouts work, I will provide new meta-commands that describe the placement of a generated callout relative to the current step image (...) (21 years ago, 16-Apr-03, to lugnet.cad, lugnet.cad.dev)
|
| |
| | LPub 2.1.0.8 Available
|
|
LPub 2.1.0.8 is available from (URL) version of LPub adds these new features: - Sub-assembly callout image generation - Unique construction image background colors for up to four sub-model levels. - Proof mode to make Lpub do a dry run through the (...) (21 years ago, 16-Apr-03, to lugnet.announce, lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: Callout generation
|
|
"Kevin L. Clague" <kevin_clague@yahoo.com> wrote in message news:HDC5Gu.1ux3@lugnet.com... [ ... snipped ... ] (...) is (...) get (...) level. (...) seperated (...) I think so, I'd like to play with it. Mike -- Mike Walsh - mike_walsh at (...) (21 years ago, 14-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Callout generation
|
|
(...) For now, I decided to make callout generation a seperate pass of the model. By disabling construction image generation, you can make changes to the callout specifications in your DAT files, Generate -> Instruction Images, and you won't run (...) (21 years ago, 14-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Callout generation
|
|
(...) I recall some one (Dutch too) who started a Postscript project. It was about converting the LDraw format directly to PS. I asked this way back: (URL) (december 10 1999 :-) I got no reply... But then, Guido Heunen replied to another thread: (...) (21 years ago, 14-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Monkeypede
|
|
(...) Ok -- Steve Bliss ICQ'ed me and suggested trying L3Lab's Register File Types option to settle the MIME-types. Win2K doesn't allow you to manually edit the MIME-types through the interface, and I forget how to do it in the registry. So, I try (...) (21 years ago, 14-Apr-03, to lugnet.cad.dat.models, lugnet.admin.general, lugnet.cad.dev)
|
| |
| | Re: Callout generation
|
|
(...) Hi Kevin and Tim, Loads of info and URLs here: (URL) the mentioned book as PDF here: (URL) (21 years ago, 13-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Callout generation
|
|
(...) Hi Tim and Kevin, Since I'm a desktop publisher IRL and for longer I can remember I do know something about Postscript and Postscript programming. It is a fairly easy language to learn and understand. Think of it as POV but in 2D. I have a (...) (21 years ago, 13-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Callout generation
|
|
(...) Yes. I'm sure. FYI, I new nothing about LDraw file formats before I wrote LPub either ;^) I'm thinking that the whole page layout (including formatting of callouts, and callouts within callouts), is a whole new layer of concept in LPub (or an (...) (21 years ago, 13-Apr-03, to lugnet.cad.dev)
|
