 | | Re: Web browser compatibility testing request
|
|
(...) Looks fine in Opera 8.3. I'm sure I can test it on Lynx for you too ;) Tim (17 years ago, 17-Jan-07, to lugnet.cad.dev)
|
| |
| | Re: Web browser compatibility testing request
|
|
(...) The above was worded badly. I'm most interested the above browsers. However, if you use some other browser, please test it in that as well, and report the results. --Travis (17 years ago, 17-Jan-07, to lugnet.cad.dev)
|
| |
| | Web browser compatibility testing request
|
|
I'm adding a new feature to LDView that will generate a parts list web page for any model being viewed in LDView. The HTML code that I'm generating makes heavy use of CSS, and I don't have some browsers that users might use. While my output (...) (17 years ago, 17-Jan-07, to lugnet.cad.dev)
|
| |
| | Re: LSynth electric cable cross section oriention problem
|
|
(...) Me too! Kevin (18 years ago, 27-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: LSynth electric cable cross section oriention problem
|
|
(...) Hi Kevin, Another possibility to investigate is to change the up vector in inverse proportion to the bezier curve change. That would mean it would twist less where there's a sharper bend, and would possibly end up looking more authentic. But (...) (18 years ago, 26-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: LSynth electric cable cross section oriention problem
|
|
(...) Leo, In case you didn't get this far, I solved the above problem and can now control twist all through a cable segment from start point to end point. I calculate the up vector for the start of segment, and the up vector for the end of segment. (...) (18 years ago, 26-Nov-06, to lugnet.cad.dev)
|
| |
| | LDAO problem
|
|
i guess this would be the correct spot for the message. i have a install problem with LDAO. i install it, and when i stat it i get error 76 , path not found. (18 years ago, 26-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: LSynth electric cable cross section oriention problem
|
|
I've got up/side/front vector stuff working now, so that I can control the orientation of cross sections of electrical cables at the start of a segment defined by two constraints. My issue now is that I don't know how to force the twist so that the (...) (18 years ago, 24-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: bend thingie creator.
|
|
(...) Let me check my archive of LDraw related programs and if I have it I'll email it to you. -Orion (18 years ago, 24-Nov-06, to lugnet.cad.dev)
|
| |
| | LSynth electric cable cross section oriention problem
|
|
Hi, I've got a reworked version of LSynth with a major problem... I cannot figure out how to control the twist of the cross section. I use bezier curve to created the nicely curved set of points, and compress it by tossing out points until the angle (...) (18 years ago, 24-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: bend thingie creator.
|
|
(...) Koen, I tried to email you using your address, and I tried to download your bendie thingy creator. It is gone. Does anyone have a copy of this so I can play with it? Kevin (18 years ago, 24-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: *** Correction: LDView Version 3.1 Released ***
|
|
(FUT lugnet.cad.dev) (...) Actually, all the string handling code for the path stuff is fine (and cross-platform to work in both Windows and *nix). After doing some investigation, I discovered that the problem is that when we do a stat on the (...) (18 years ago, 22-Nov-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
A sincere thanks to all of you. Your comments made me go back over (again) my export code, and I found an error. Now it works as expected. I was getting funny rotations because I mis-ordered the elements of the transformation matrix, duh. Seems (...) (18 years ago, 20-Nov-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
(...) I agree with Tim. It looks fine to me. If there were any mirroring going on, then either the orange and red would be swapped on the unwrapped box, or the green and grey would be swapped. The picture in LDView has a rotated camera angle (...) (18 years ago, 19-Nov-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
(...) Google uses the right handed system but indeed rotated by 90 degrees, LDraw also uses the right handed system but 180 degrees rotated. It should not matter how you show the model, the coordinates are interchangeable, but if you want to use (...) (18 years ago, 19-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
Tim Gould wrote: > It is still a right-handed system. The handedness is unchanged by rotation (in (...) So the original designer of the LDraw program just decided to use this orientation of the right handed system. if so then it starts making more (...) (18 years ago, 19-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
(...) That looks like a correct mapping to me. Unless I'm mistaken the red and orange are on the same sides in both pictures. The unwrapped boxes are definitely identical and unless you've moved them in one or the other the whole thing is right. Tim (18 years ago, 19-Nov-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
Hi, Here's my box test model in SketchUp. (The above model is the same model unfolded.) (URL) When I export this model to a .dat and open it in LDView, the green side is the top-view, blue is the front view (as expected), and I would expect the (...) (18 years ago, 19-Nov-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
(...) In LDraw +z is backwards, not forwards or more strictly +Z points away from the camera when X is right and -Y is up. Tim (18 years ago, 19-Nov-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
(...) I've been having difficulty with importing/exporting .dat files from SketchUp. In SketchUp, if you stand at the Origin; X is right, Y is forward, and Z is up. The LDraw Primitives Reference ((URL)) says the LDraw axes are: X is right, Y is (...) (18 years ago, 19-Nov-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
(...) It is still a right-handed system. The handedness is unchanged by rotation (in ldraws case 180*x from standard). Tim (18 years ago, 19-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
As I understand it, LDraw has negative y in the up direction, which is neither right nor left handed, but something else entirely. I don't know that it has a name. James (18 years ago, 19-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: LDraw coordinate system driving me crazy
|
|
(...) I've always understood it is: X positive is right X negative is left Y Positive is bottom Y Negative is top z Positive is back z negative is front In fact you can show this by adding a brick in MLCad and moving it around, watching how the X, Y (...) (18 years ago, 19-Nov-06, to lugnet.cad.dev)
|
| |
| | LDraw coordinate system driving me crazy
|
|
Hello all, I'm having difficulties with the ldraw coordinate system. As fas I understood it it's Right handed, just like OpenGL. So X positive is right X negative is left Y Positive is top Y Negative is bottom z Positive is front z negative is back (...) (18 years ago, 19-Nov-06, to lugnet.cad.dev)
|
| |
| | Re: Question to parts authors about BFC CERTIFY
|
|
In lugnet.cad.dev, Travis Cobbs wrote: > So, my question is this: should I remove this warning from LDView for commands > that contain options in addition to CERTIFY and CW/CCW? I definitely think that > it's appropriate to warn when multiple (...) (18 years ago, 12-Oct-06, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Question to parts authors about BFC CERTIFY [DAT]
|
|
As many parts authors are aware, LDView produces a warning if it finds more than one instance of the CERTIFY option among the BFC commands in one file. For example, the following will produce a warning on the second BFC command: 0 BFC CERTIFY CCW 1 (...) (18 years ago, 12-Oct-06, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: Part 3650a
|
|
Here's a resurrection of an OLD thread... :-) I've recently begun to store all my TECHNIC sets, which range from about 1988 to present, all have been stored MISB (well, OK, they've been stored in the original box after I opened, inventoried by bag, (...) (18 years ago, 8-Oct-06, to lugnet.cad.dev)
|
| |
| | Re: Bug in LDGlite?
|
|
(...) My first guess would be the -z-6000 arg. I think this places the near clipping plane way back behind the camera. What you want to do is put it in front of the camera, as far out as you can without clipping the model, so you squeeze the space (...) (18 years ago, 5-Oct-06, to lugnet.cad.dev)
|
| |
| | Bug in LDGlite?
|
|
hi, any ideas what's wrong with this batch file: set LDGLITE_EXE="C:\Prog...ad\LDGLite 1.1.8\ldglite" for %%a in ("MOTM_*.dat","MOTM_...OTM_*.mpd" ) do %LDGLITE_EXE% %%a -fh -v10240,7680 -s2 -z-6000 -Z6000 -i1 -q -cg25,45,0 -mS%%~na1.png for %%a in (...) (18 years ago, 4-Oct-06, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) I found that performance went down somewhat when I copied and pre-translated all the studs too. I could be creating a memory cache penalty. Anyway it is only one matrix multiply per stud (stud is already flattened in itself), which goes onto (...) (18 years ago, 9-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
The thread seems to be splitting from the original point, It is a fact that OpenGL generally places a depth of 16 on any transforms. If an LDRAW model in MPD format was presented to OpenGL as a raw data block I suspect that OpenGL would easily hit (...) (18 years ago, 8-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) Actually on modern cards strips are always slower than optmized lists. You can always try adding degenerate triangles to stitch strips together to save the cost of multiple render calls (too bad PC cards don't support a primitive reset index). (...) (18 years ago, 8-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) Well, typically the multiplies that occur for different studs have the same rotation and scaling aspects, the only thing different is the position. So instead of repeating the multiplication on the original matrix, if the top left 3x3 values (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) Okay... 15% speedup is substantial... that means that it's better to pre-transform the subfiles when generating the operations for the current file. I won't worry about the maximum depth any more then. (...) How does a renderer know which (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) Same here for LDView. LDView always flattens part geometry, and this seems to improve performance enough to be noticed. LDView does use a display list for each part, and a nested display list for each nesting level above that (as long as you (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) MPD files don't add that many extra levels... usually only 2, isn't it? Further, the only stacking that generally needs to occur at the mpd level is modification of the modelview matrix, which opengl guarantees a minimum of 32. It's only in (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) I tested the performance of, and saw a decent gain from flattening part geometry. (Perhaps 15% in BrickDraw3D for QuickDraw3D or OpenGL.) What this means is that when a part is prepared into a drawing list, it is not a list of calls to (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) As far as building instructions go, LPub only provides for unique background color/backdrop for up to four levels. This is about as much as I've ever seen in LEGO building instructions. The renderers take care of nesting within individual part (...) (18 years ago, 7-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Maximum depth of ldraw models?
|
|
(...) Hmm. I use MPD models a lot, there can be several levels of nesting within a single .mpd file, and I have been known to refer to .mpd files from other .mpd files. I'm not sure how deep my nesting of model files goes, but I'd be a little (...) (18 years ago, 6-Sep-06, to lugnet.cad.dev)
|
| |
| | Maximum depth of ldraw models?
|
|
I notice that no maximum depth is given by the standard. How potentially non-compliant would a renderer be if it fails because parts in a model are too deeply nested (a maximum of as little as 16 on some OpenGL implementations). I notice that no (...) (18 years ago, 6-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Well, one that I have gives a warning message that says it can't handle color 24 and substitutes 16 for such lines. But I wasn't sure if that was correct behaviour. Another one that I've played with quietly accepts such lines, but appears to (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Actually, that grep doesn't return anything. '^[ \t]*1 24' does return hits from three files, though. Every single place in the library that this is used, it's used in a reference to one of the edge primitives. The edge primitives use color 24 (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) In the case of some kind of direct color, I guess the rendering program is free to do whatever it wants. The simplest action would be to default to black (either LDraw 0, or RGB #000000). I'd be interested to hear what actual rendering (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
Okay... that makes sense. But what if the contrast color for the current file's main color is just an RGB value rather than a color index? What should the subfile's contrast color be set to in that case? Thank you for your help, by the way. >> Mark (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) The contrast color within the subfile would be defined in the normal way - use the main color for the subfile, and look up the contrast color from the color table. The fact that the originating linetype 1 used color code 24 shouldn't matter by (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Right... but what should the contrast color be defined as within the subfile? The same? >> Mark (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Not exactly -- just use the current contrast color as the main color for the subfile. Whenever a subfile is rendered, it should already be looking up the local contrast color based on the local main color. Steve (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Does that mean that it would be appropriate for a renderer to just swap the main and contrast colors when it encounters such a line, or what? I just want know what a renderer is supposed to do. (...) Well, doing grep '^1 24 ' on the parts (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) It will be the constrast color for the constrast color. Which may be the same as the main color -- but it may not. Also, some viewers (like L3Lab) may balk at rendering a file which uses color 24 in a line type 1. Steve (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) OK, I was partly right. There actually is a standard defined for colour extensions, you can view it here (URL) it only applies to colours defined either in ldconfig.ldr, or in the part files or model files themselves. And it is still up to the (...) (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: What does a subpart with color=24 mean?
|
|
(...) Hi Mark, I'm pretty sure there is no standard for that, and it depends on which renderer you use. ROSCO (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | What does a subpart with color=24 mean?
|
|
How is the contrast color defined for line type 1, when color=24? >> Mark (18 years ago, 5-Sep-06, to lugnet.cad.dev)
|
| |
| | Re: Proposal for MLCad.ini Enhancements
|
|
(...) hi allen, many thx for the .ini file fixes you sent me via mail. I'll load them up asap. the rest is michael's territory as I'm only the maintainer of the data. bye, w. (18 years ago, 19-Aug-06, to lugnet.cad.dev)
|
| |
| | Proposal for MLCad.ini Enhancements
|
|
In the course of writing a minifigure generator for my Bricksmith program, I've really come to appreciate how nifty it is to have something like the MLCad.ini file to work with. I've very grateful to the people who designed and maintain it. However, (...) (18 years ago, 18-Aug-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: 48 directory and non filename only line 1 part file names
|
|
(...) Yes, basically. It wouldn't make any sense to add the parts\s directory, because those files are segments of parts -- they aren't complete objects in any sense. They are only intended to be used by part files, which should refer to them (...) (18 years ago, 31-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: 48 directory and non filename only line 1 part file names
|
|
(...) <snip> (...) Is it correct to assume because of this, the 48 and s dirs must not be added to the part search directories list? Roland (18 years ago, 31-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: 48 directory and non filename only line 1 part file names
|
|
(...) I've decided to drop the whole option for now, so the 48 dir is only used if parts reference to it by 48/xxx.dat . Roland (18 years ago, 31-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: 48 directory and non filename only line 1 part file names
|
|
(...) <snip> As might be expected, Steve's replies were correct (as far as I know, anyway ;-). (...) While it's true that this isn't all that useful, it can still be done, even though some parts reference primitives from the 48\ directory directly. (...) (18 years ago, 30-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: 48 directory and non filename only line 1 part file names
|
|
(...) Not exactly. The files in the ldraw\p\48 directory are all based on a 48-faceted approximation of a circle. The regular primitives in ldraw\p are all based on 16-facets. Just because a file is in one directory does not mean a corresponding (...) (18 years ago, 30-Jul-06, to lugnet.cad.dev)
|
| |
| | 48 directory and non filename only line 1 part file names
|
|
Hello all, Still working on the LDraw loader. The 48 directory in ldraw\p, as far I understand it, is a 'alternative' source for primitives, not? Jet I see some (unofficial) files using type 1 lines with the 48\ attached to the part name reference (...) (18 years ago, 29-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) It's my work system, but I rarely use 2005. Most of my customer projects demand use of Delphi 6 Pro. Because that's what the customer itself owns. I maintain their code so I have to use their tools. Because of this I don't justify spending (...) (18 years ago, 27-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Probably. As I was reading the thread it was *loading* the MPD file that was considered two-pass, and my algorithm is definitely only one-pass for that (and no extra fixups after reading it all). OTOH, if the file should be rendered on screen (...) (18 years ago, 27-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Don't know about that, source-wise (all my work projects are still Delphi, Win32 only). In .NET you definitely don't have to care about the language an assembly was written in, you just use it. (...) If that is your work development system, I (...) (18 years ago, 27-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) I suspect there's two definitions of "pass" at work here. I would consider a two pass algorithm to be anything requiring two loops (which we must have either way as their is no reference order specified in MPDs). Another way of considering it (...) (18 years ago, 27-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Actually I can't get my head around 'searching for a file in the cache' as equivalent to 'do a second pass of the source file'. Every part is searched for in the cache. Each source line is only read and parsed once. What am I not (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Delphi 2005 (9) is part of Borland Developer Studio (BDS) 2005. It also contains C# Builder and Delphi for .net compilers. But I mainly use Delphi for win 32 development. Since BDS 2006 C++ Builder is also included in the suite. But I decided (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Is Delphi 2005 Delphi (Pascal) only? I've got BDS2006 at work and that contains both Delphi and C++ and C#. Going .NET would make it easy (?) to use a C++ library from Delphi, I think. (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Thanks for the pointers, I'm working with Delphi 2005 Pro win32 at the moment (LD4DModeler was written in Delphi 6 Pro). So I can't use you're library. But I will certainly take a look at it. I sometimes write stuff in C++, but for a living (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
Lars C. Hassing wrote: [snip detailed explanation] Thanks for the insight of you're L3P ldraw reader routines. (...) If you mean by public, public to all children and not the whole world, this fits perfectly in Anders Isaksson vision. See my reply (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) This is actually very logical. And it fits in the description from the 2000 post pointed to by Lars. So all objects in the mpd are available for recursive children of the main part, being the first place to search. (...) I don't think stuff in (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) That is a two pass algorithm. It's optimised by only searching files that have already appeared but the search in stage II is a second pass. Tim (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) What about the following algorithm (assuming everything is cached): - whenever a file reference is read, search for the file in the cache. if not found, add it as an empty file and flag it as 'incomplete' - whenever a 'file' is seen, search (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) It seems to me that an MPD is functionally equal to a disk folder which has been added to the (beginning of the) search path for parts. No more, no less. If a part is found in the search path it is used, if it is not found it is ignored (with (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) You're right, but Jacob invented the MPD, so I guess I just followed his wish, though I would have preferred the scoping. Also he suggests a way to get scoping anyway: "0 FILE house1/house1.dat" which nicely reflects the storage on the disk. (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Wow, that's impressive. I'm pretty sure it's accidental, too. (Accidental on my part; your L3P parser was obviously there first.) (...) LDView only has one file open at a time also (unless I'm mis-remembering my implementation), since the (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) You're welcome. (...) I think local scope is the "correct" thing to do as long as local scope means that only files inside an MPD file can access other files inside the MDP file. Files stored external to the MPD shouldn't, in theory, be able (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) I actually consider that to be two-pass, and that's essentially what LDView does. The only extra thing it does is that it checks for 0 PART meta-commands in the first pass, and puts the file data for the sub-files into their own separate (...) (18 years ago, 26-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Well, if you read all postings on MPD through the last seven years you should be able to piece the correct answer together :-) I believe the L3 parser (used in L3P, L3Lab and "ldglite -l3") reflects that information. > However, I can tell (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Sorry, you're right every part in the mpd should see any of the other parts. May be Ldraw.org should post a set of 'testcase' files to be used as a reference for programmers. For each file there should be a description of the expected results (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Is that what I said? I didn't mean to... If an MPD contains main.dat, a.dat, and b.dat, then a.dat should be able to 'see' b.dat. I make heavy use of the MPD format while working on part files. Inside a single MPD, I typically have long chains (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) You can do it in one pass (if you don't count the loading of the file to a stringlist). Wile walking through the file you build you're objectlist with subparts. Afterwards you go recursively through the list of subparts. This way all mpd (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Snip, very thourho explanation, thanks! (...) I was thinking of doing the local scope approach mentioned by Steve. But maybe I keep it optional realizing I always end up disappointing some people with ether approach. I was planning to create (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) I mentioned in my other (long) post that I don't think that MPD files should be required to have a .mpd extension. However, I'd like to add more here in answer to your specific question. I could be wrong, but I'm almost positive that it is (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
As you have pointed out, the spec is indeed ambiguous. Consequently, there's probably no correct answer as to how things should work. However, I can tell you what I do in LDView, so that you have an idea of how at least one MPD-compatible program (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: MPD file loading search order
|
|
Thanks Tim and Steve, I think I will go with Steve's advise to let only the main part in the mpd see the other parts in the mpd. This will give a much cleaner recursive approach, in which I can easily support sub mpd's. Further more I think I will (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Tim pointed you at the actual MPD spec. You may notice that is is vague on a lot of points -- it basically leaves it up to the program authors. My comments below are what makes sense to me, thinking as someone who might create complex MPDs. (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) My apologies. I just looked there more closely and it doesn't seem to answer anything. To answer what I'm fairly sure of (but far from certain): I think that the correct lookup order is internal, ., [MODELS], [PARTS] Yes MPD files must have (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) --SNIP-- (...) Hi Roland, Try (URL) for the file specifications. Hopefully that should answer some queries. Tim (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | MPD file loading search order
|
|
Hello All, I'm implementing a LDraw file loader and was wondering about some details concerning mpd. I could not found enough info about this elsewhere, or I may overlooked it. [1] When loading a MPD file should I keep checking the first level of (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: Unable to compile LDGLite 1.0.7 from Source on SuSe Linux
|
|
I'd use the "daily snapshot". It should match the latest Windows and Mac releases. I just never got around to testing linux build of of version 1.1.8, as you can see. Anyhow, main.c should include the bumpy case "StdAfx.h". I stuck a few linux stubs (...) (18 years ago, 30-May-06, to lugnet.cad.dev)
|
| |
| | Re: Unable to compile LDGLite 1.0.7 from Source on SuSe Linux
|
|
I could compile on Fedora Core4 with this patch: --- ../ldglite/main.c 2003-08-15 03:26:15.000...000 +0200 +++ main.c 2006-01-09 19:22:08.000...000 +0100 @@ -1388,7 +1388,7 @@ int lineheight = 14.0; int charwidth = 9.0; - extern void (...) (18 years ago, 28-May-06, to lugnet.cad.dev, FTX)
|
| |
| | Unable to compile LDGLite 1.0.7 from Source on SuSe Linux
|
|
Having downloaded and unzipped the 1.0.7 source from SourceForge (and having had similar errors trying the version recommended on the LDraw getting started guide), I am having difficulty getting it to build. At first, when I was building, it was (...) (18 years ago, 27-May-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: LDList stud count feature (Was: LSC - current status?)
|
|
Tore Eriksson schrieb: (...) Is it possible to include a separate directory where the unofficial files are? cu MikeHeide (18 years ago, 18-May-06, to lugnet.cad.dev)
|
| |
| | Re: LDList stud count feature (Was: LSC - current status?)
|
|
(...) Yes, and now I know what the problem was: the scan takes 56 minutes on my computer, with no sign of life from LDList, so I assumed that LDList must have had crashed. But of course, it takes some time to count the studs from some 5 000 files. (...) (18 years ago, 18-May-06, to lugnet.cad.dev)
|
| |
| | Re: LDList stud count feature (Was: LSC - current status?)
|
|
Do you have the latest version? 'Search by stud count' wasn't there until 4.0 (I think). Check the version in the caption bar (top of the window). Get 4.1 from: (URL) installing, you must also do a 'Scan' again, to rebuild the index. (18 years ago, 18-May-06, to lugnet.cad.dev)
|
| |
| | LDList stud count feature (Was: LSC - current status?)
|
|
(...) /Tore (18 years ago, 17-May-06, to lugnet.cad.dev)
|
| |
| | Re: LSC - current status?
|
|
(...) That's where LDList (my LDRAW Part search program) comes in - you can even search on the number of studs :-) (URL) Anders Isaksson, Sweden BlockCAD: (2 URLs) (18 years ago, 17-May-06, to lugnet.cad.dev)
|
| |
| | Re: LSC - current status?
|
|
(...) Could the translation not be managed at the user end? For example we could make a program "partstranslate" which reads in one or more translation table(s) (just Swedish in this case) and goes through all parts adding a new line something like (...) (18 years ago, 17-May-06, to lugnet.cad.dev)
|
| |
| | Re: LSC - current status?
|
|
(...) Actually, I don't have a problem with changing part header information with an admin edit without destroying the existing votes, and have done this many times. I would draw the line at changing data which affects the integrity of the part - (...) (18 years ago, 17-May-06, to lugnet.cad.dev)
|
| |
| | Re: LSC - current status?
|
|
(...) the aim is to lower the bar for newbies and people who don't speak any english. assuming that you are not fluent in italian or german, just try to match the following words with their german and italian counterparts: brick plate tile slope (...) (18 years ago, 17-May-06, to lugnet.cad.dev)
|
