 | | Re: number notation in official parts
|
|
(...) Thanks for the info. I've always used perl scripts to convert oddly formatted data to a consistent format and then read it like that. Nice to know I don't always have to. If it could only read some of the more bizarre Fortran formats I'd never (...) (14 years ago, 12-Mar-10, to lugnet.cad.dev, lugnet.off-topic.geek)
|
| |
| | Re: number notation in official parts
|
|
(...) All float specifiers (e, E, f, g, G) are treated identically by the scanf functions. When scanning floats, they always recognize all float formats. One other thing about %g on output is that it automatically strips trailing zeros, which %f (...) (14 years ago, 12-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) Ahhh. I'd never heard of %g before now. I'm so used to %f and %e it had never occured to me that there might be a mixed option. Handy to know as I suspect it would be helpful in reading files of unknown format. I'm sure Delphi has some hideous (...) (14 years ago, 12-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) Actually, in C, %g does exactly this. Having said that, I think LDDP is a Delphi app, so it uses Pascal, and I don't remember how Pascal does formatting. --Travis (14 years ago, 12-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) I definitely know this. I see them far too much in my job as a numerical physicist ;) My point is that to write in mixed format (some %f and others %e) requires some strange coding unless there is a weird language which does it automatically. (...) (14 years ago, 12-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) Hmm, I thought I killed that "feature". I'll look into it as I find time to finish up LDDP 2.1 -Orion (14 years ago, 11-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) I mostly agree with this policy. (...) There is nothing strange in the routines, it is the standard format used to represent very large or very small numbers in a limited number of digits. Actually since values never get very large in LDraw (...) (14 years ago, 11-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) My suggestion would be to read numbers in that notation but never write them. I'm not sure why LDDP would write them that way (it would require some strange output routines) but if one thing writes them then it's best to read them. Tim (14 years ago, 11-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) I think it should be forbidden in official files as the benefit is very small and it is not good human readable. Benefit would be smaller filesize, as 0.0004 (6 characters) has more characters than 4E-4 (4 characters). Against could be 0.4 (3 (...) (14 years ago, 10-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) Such notation is not noted in any specs.. neither allowed or forbidden. At least, I can't find such. Maybe we should bring this up at LSC at some point? (FWIW I sent this in yesterday but it seems the server ate the message.. resending it) (...) (14 years ago, 9-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) Such notation is not noted in any specs.. neither allowed or forbidden. At least, I can't find such. Maybe we should bring this up at LSC at some point? -Santeri (14 years ago, 9-Mar-10, to lugnet.cad.dev)
|
| |
| | number notation in official parts
|
|
If I rotate a part in LDDP the result may look like this: 1 16 4E-15 4 -20 0 0 1 0 -1 0 -1 0 0 stud4.dat This can be read by LDView and MLCad as a valid number. Is such notation allowed in official parts? It is nowhere explicit allowed or (...) (14 years ago, 8-Mar-10, to lugnet.cad.dev)
|
| |
| | LDSwitch Sample #1: Do/Undo [DAT]
|
|
Don't know if you prefer to make input here or at SourceForge, so I crosspost. Please give feedback where you like, here or at SF. Here's the first sample LDraw code snippet. Set the value of the variable Rev028_Changes to Do or Undo, run the (...) (14 years ago, 23-Feb-10, to lugnet.cad.dev)
|
| |
| | LDSwitch Project on SourceForge
|
|
(...) I've just registered myself and my first project at SourceForge: (URL) to join or just input! /Tore (14 years ago, 23-Feb-10, to lugnet.cad.dev)
|
| |
| | LDSwitch?
|
|
Is the name/keyword/META-command LDSwitch/!LDSWITCH free to use or is it taken? I think it's not taken (in the LCad context), so I wish to claim it if noone protests. /Tore (14 years ago, 23-Feb-10, to lugnet.cad.dev)
|
| |
| | Re: Undo/Redo Information META Tags? Or Options Buttons?
|
|
(...) And I'm not sure this would be the optimal solution either. This options thing is more like a case switch than a series of if statements. (...) Thanks for your input, Kevin. I am looking for a friendly solution that won't output any code that (...) (14 years ago, 19-Feb-10, to lugnet.cad.dev)
|
| |
| | Re: Undo/Redo Information META Tags? Or Options Buttons? [DAT]
|
|
(...) Well, you could easily do the above using the C preprocessor and #ifdefs, but that would be outside any LCAD application (and make the original file hard to work with in any modeler). #ifdef LDBOXTER_LEVEL_D /* crude simplification */ 1 15 0 (...) (14 years ago, 19-Feb-10, to lugnet.cad.dev)
|
| |
| | Undo/Redo Information META Tags? Or Options Buttons? [DAT]
|
|
I've been thinking hoe nice it would be if there was some kind of system of tags that enabled the user to store undo and redo information in a model after the model building application is closed. Now, there are a great number of LCAD apps of which (...) (14 years ago, 19-Feb-10, to lugnet.cad.dev)
|
| |
| | Defining LED Colors in LDConfig?
|
|
I've been thinking about that talk of limiting the colour definitions in LDConfig.ldr to part colours with a few expectations, and I agree with that. But I wish to throw in an idea that I don't even believe in myself but yet want to air. Is it (...) (14 years ago, 10-Feb-10, to lugnet.cad.dev)
|
| |
| | Re: LDraw Names for Monorail Parts
|
|
(...) It makes more sense for "Monorail" to be a valid CATEGORY than some of the existing ones, so I added it a while ago. The definitive list is at (URL) Chris (14 years ago, 21-Jan-10, to lugnet.cad.dev, lugnet.trains)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) I'm using WinGrep ((URL) and/or Copernic Desktop Search ((URL) for local searching, and have turned off all Windows indexing. Copernic is awfully fast (but it creates huge indexes), while WinGrep is better (IMO) for source code searches. The (...) (15 years ago, 22-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: Unofficial Parts Path
|
|
(...) This is a nice tip, thank you. Yes, I agree that it would be nice to be able to arbitrarily enable/disable/set/configure the paths LDraw (ok, maybe not ldraw.exe and ledit.exe per se) uses to search for parts. Mike (15 years ago, 22-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) This is true in XP as well if you have "Windows Desktop Search" (or something similar) installed. I wish I could disable *that*. (15 years ago, 22-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) Yeah, and the "improvements" in Vista and Windows 7 are, as far as I'm concerned, even worse. Also, I'm not sure how XP behaves, but in Vista/Windows 7 if you have indexing turned on and search new files, it will silently not return any (...) (15 years ago, 21-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) Thanks, Travis, I have already managed to chase that annoying dog away, it was just to right-click on him or so. Maybe I'll turn that whole assistant off, too. Isn't it strange that in the efforts of making the search faster and easier, they (...) (15 years ago, 21-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) I know your question has already been answered, but to get rid of the dog, see here: (URL) getting it to search all files is also described here: (URL) that the above solution should work even if you have indexing turned off. I'm not sure if (...) (15 years ago, 21-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) 2" worked just splended. /Tore (15 years ago, 20-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) Read here, (URL) how to add extensions to the XP file search. Or get WinGrep, (URL) Anders Isaksson (15 years ago, 20-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) Aah, nevermmind. I installed good old Total Commander and got a much better file search without bugs and foolishly grinning dogs. /Tore (15 years ago, 20-Dec-09, to lugnet.cad.dev)
|
| |
| | XP File Search Refuses To Search .LDR Files!
|
|
Sorry for posting slightly off-topic, but the X-Pee thing drives me completely insane. I do a file search just like I always have done in previous systems, but in XP, the search fuction just refuses to search in .ldr files. I was looking for (...) (15 years ago, 20-Dec-09, to lugnet.cad.dev)
|
| |
| | Inliner is back
|
|
You may have noticed that Inliner have had problems with winding. That should be solved now. You can find the current version (2.2.0.0) at (URL) (15 years ago, 11-Dec-09, to lugnet.cad.dev)
|
| |
| | LDConfig Manager 1.0
|
|
Because of the current discussion about the LDConfig.ldr I needed a tool to visualisise all the used colors. So I just coded LDConfig Manager. It is far from beeing complete and maybe buggy, but it works for me. Maybe you are also interested in (...) (15 years ago, 6-Dec-09, to lugnet.cad.dev, lugnet.announce, lugnet.cad)
|
| |
| | Re: LDraw Boxer development
|
|
(...) There are some additional boxes on my web page: (URL) is indeed a very useful tool. I just wish I had more time to create boxes. Mike (15 years ago, 25-Nov-09, to lugnet.cad.dev)
|
| |
| | LDraw Boxer development
|
|
I am happily surprised to see that my old utility ldboxer is still in use. (URL) may have underestimated the potential of this idea. However, it needs a total upgrade. First, we need to add new parts to the \B library. Please come in with (...) (15 years ago, 24-Nov-09, to lugnet.cad.dev)
|
| |
| | LETGUI new version 1.4.0.0
|
|
I have just uploaded a new version of LETGUI package, that contains the new tool Slicerpro (Version 1.1). You can download the updated package from (URL) (15 years ago, 1-Nov-09, to lugnet.cad.dev, lugnet.announce, lugnet.cad)
|
| |
| | Re: calc_z4.c (Was: Math Problem Again)
|
|
(...) True, but such triangles will not be visible in the 2-D front view of the UI and therefor not clickable - unless the program is buggy. And if you can't click on them, the function never has to encounter data from them. Hopefully... /Tore (15 years ago, 26-Oct-09, to lugnet.cad.dev)
|
| |
| | Re: Unofficial Parts Path
|
|
[SCAN_ORDER] 1 = SHOW <LDRAWDIR>Parts 2 = HIDE <LDRAWDIR>Parts\s 3 = HIDE <LDRAWDIR>P 4 = HIDE <LDRAWDIR>P\48 5 = SHOW <LDRAWDIR>Unofficial\Parts 6 = HIDE <LDRAWDIR>Unofficial\Parts\s 7 = HIDE <LDRAWDIR>Unofficial\P 8 = HIDE (...) (15 years ago, 25-Oct-09, to lugnet.cad.dev, FTX)
|
| |
| | Re: calc_z4.c (Was: Math Problem Again)
|
|
(...) Actually, if the original triangle is (for example) in the Y-Z plane, then just passing in an x4 that's different from x1, x2, and x3 will result in a failure. The equivalent goes for an initial triangle in the X-Z plane. --Travis (15 years ago, 25-Oct-09, to lugnet.cad.dev)
|
| |
| | Re: Unofficial Parts Path
|
|
(...) Ten letters folder name... may it always remain a quasi standard! /Tore (15 years ago, 25-Oct-09, to lugnet.cad.dev)
|
| |
| | Unofficial Parts Path
|
|
Unofficial Parts Path Unofficial parts should not mixed with official part. Therefore the a quasi standard has been established as follow: Unofficial files should be stored in a directory structure like follows: <LDRAWDIR>/Unofficial/P (...) (15 years ago, 25-Oct-09, to lugnet.cad.dev)
|
| |
| | Re: calc_z4.c (Was: Math Problem Again)
|
|
In lugnet.cad.dev, Timothy Gould wrote: // calc_z4 by Tore Eriksson // credits to Ronan Webb for the superb formula double calc_z4(double x1,double y1,double z1, double x2,double y2,double z2, double x3,double y3,double z3, double x4,double y4) { (...) (15 years ago, 23-Oct-09, to lugnet.cad.dev)
|
| |
| | Re: calc_z4.c (Was: Math Problem Again)
|
|
(...) You also need a touch of code to catch when c=0 so that z4 is undefined ;) Tim (15 years ago, 23-Oct-09, to lugnet.cad.dev)
|
| |
| | calc_z4.c (Was: Math Problem Again)
|
|
(...) Sorry guys, just wanted to store this function in a safer place than my hard drive. :) I just don't want to remake it again...! Feel free to copy/paste/edit/port if you need it! /Tore // calc_z4 by Tore Eriksson // credits to Ronan Webb for (...) (15 years ago, 22-Oct-09, to lugnet.cad.dev)
|
| |
| | Re: Peeron_to_MLCad
|
|
(...) Hi Il'dar Ismagilov I'm sorry but I haven't received an email from you or I have cancelled it involuntarily. I have tested again Peroon_to_Mlcad with Internet Explorer 8.0 and Mozilla Fireworks 3.5 and there are no problems for me. Contact me (...) (15 years ago, 17-Oct-09, to lugnet.cad.dev)
|
| |
| | Re: Peeron_to_MLCad
|
|
(...) This program is interesting for me. But It does not work correctly now. I think the reason is that Peeron's html code has changed and a Peeron2MLCAD's parser needs an update. I have an universal parser from my another program and I prefer to (...) (15 years ago, 17-Oct-09, to lugnet.cad.dev)
|
| |
| | Re: reference for program author
|
|
In lugnet.cad.dev, Michael Heidemann wrote: -- snip -- (...) That sounds like a perfect task for somewhere on the wiki. That way information can be kept up-to-date whenever new discussions take place. (URL) created a quick article start for people (...) (15 years ago, 6-Oct-09, to lugnet.cad.dev)
|
| |
| | reference for program author
|
|
Many times during developing DATHeader I had questions that I tried to solve by searching in LUGNET posts and reading the documentation on LDraw.org. Often I had to make my own decision how to handle that problem. For example: Reading files with (...) (15 years ago, 5-Oct-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) Correction: 44489.dat should be 44809.dat Technic Cross Block 2 x 2 Bent 90 (Pin/Pin/Pin) Chris (15 years ago, 4-Sep-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) Thank you for all the comments on this (including those that veered off-topic). I like the "Cross Block" designation, especially as this is a common theme in the LEGO descriptions. It has the added benefit that it is shorter than "Joiner (...) (15 years ago, 3-Sep-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) Alright, that's cool...but how exactly would you suggest making the distinction between the three different 1x3 saddle joints? Perhaps like this: (...) And then you just need to assume that everyone knows exactly which order in which these (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) "cheese wedge". It won't come up as "slope grille" either, while Peeron produces seven different parts that merely include those words at various points in their descriptions. Sorry, but their search engine verges on being an excellent cure (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) I'd be for dimensions but not the hole sequence.. the hole sequence goes into redundancies IMHO. So for example I'd like 6536.dat to be "Technic Axle Joiner Perpendicular 1 x 2". (15 years ago, 28-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) LEGO database? To those who work for them, their part description may not be as optional as ours. However, that doesn't mean that we should make emotional choices. I worship TLG as much as the next AFOL, but we already know they don't put (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) I agree with Philo, would remove the Axle/Pin qualifier in front and go for example with "Technic Joiner Perpendicular 1 x 2 (Axle/Pin)" w. (15 years ago, 28-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) The LEGO database lists the following names: 6536 CROSS BLOCK 90° 32184 DOUBLE CROSS BLOCK 32068 TECHNIC STEERING-GEAR 3M 32291 TECHNIC CROSS BLOCK 2X4,85 41678 TECHNIC CROSS BLOCK/FORK 2X2 42003 CROSS BLOCK 3M 32557 TECHNIC CROSSBLOCK 2X3 I (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) Good thing number of Ldraw members has nothing to do with number of Ldraw users :) While I agree it would be nice if the two sources matched, unfortunately they serve totally different purposes, and that is unlikely to ever happen. BL has (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) So then, we shall say the same? Both us and BL have long-lived and complicated systems. I never really expected you or DATHeader to instantly change your way of life, but I believe that it is time to consider subtle changes to help bring our (...) (15 years ago, 28-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) Not to point fingers or start a flame war but as I recall everytime anyone has suggested that Bricklink change to conform to some other standard, it has been rebuffed by the BL admins. This lack of willingness to compromise has, at least in (...) (15 years ago, 27-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) Good thing you don't have to agree for the statement to still be true. Ldraw has just over 3 thousand members. BrickLink has nearly 110 thousand. Peeron is great for the one resource that it is most used for - historical instructions on LEGO (...) (15 years ago, 27-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) None of those parts should really be referred to as "axle joiners" or "pin joiners". The only parts that should have those names are the ones that join them end-to-end. These parts are all what a hardware store would recognize as a saddle (...) (15 years ago, 27-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) See, right there I couldn't agree with you less. I spend a lot more time producing a design in LDraw than I do plugging the parts list into Bricklink, and when I'm doing so I generally have to stick to part numbers rather than descriptions (...) (15 years ago, 27-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
Most of you know my opinion on this one - use BrickLink names. Our community is dispursed enough. We need to work to unify what we can. BrickLink names are the most widely used amongst the community. After all, how many people convert their LDraw (...) (15 years ago, 24-Jul-09, to lugnet.cad.dev)
|
| |
| | Re: Technic Axle Joiner / Cross Block descriptions
|
|
(...) I agree it is time to rationalize naming of this similar parts... I would go one step further and name all of them "Technic Joiner Perpendicular xxxx" since hole type sequence is described in the end of name, and a 6536.dat Technic Axle Joiner (...) (15 years ago, 23-Jul-09, to lugnet.cad.dev)
|
| |
| | Technic Axle Joiner / Cross Block descriptions
|
|
With almost all the "Technic Axle Joiner" parts on the Parts Tracker, I'd like to take the opportunity to rationalise the part descriptions which have developed over time as these parts have appeared. Currently we have: 6536.dat Technic Axle Joiner (...) (15 years ago, 22-Jul-09, to lugnet.cad.dev)
|
| |
| | DATHeader version 2.0.5 (The Reviewer Tool)
|
|
DATHeader is on the way not only to assist in getting a proper header for official DAT-files but also it is now a very useful tool for reviewers. You will have a listing of all tests with OK or ERROR message. Please note that not all errors that (...) (15 years ago, 9-Jun-09, to lugnet.cad.dev, lugnet.announce, lugnet.cad)
|
| |
| | Re: LDraw.exe removed from distribution?
|
|
(...) =( I delete them as well and I think that the current *old* AIOI also does not have them. Need to check.. -AHui (15 years ago, 4-Jun-09, to lugnet.cad.dev)
|
| |
| | Re: LDraw.exe removed from distribution?
|
|
(...) I don't know if you're the only one who does this, but doing so will also cause LDView's library update to fail, since those notes are the only files that allow LDView to know what has been installed. --Travis (15 years ago, 2-Jun-09, to lugnet.cad.dev)
|
| |
| | Re: LDraw.exe removed from distribution?
|
|
(...) I usually delete these notes so I'm not sure checking for them would be correct (unless I'm the only one who does this). -Orion (15 years ago, 2-Jun-09, to lugnet.cad.dev)
|
| |
| | Re: LDraw.exe removed from distribution?
|
|
(...) A good way would be to check for the presence of note*.txt files in the models directory. These show which updates have been installed. Prior to 2008-01 ths naming convention was NOTEyyrr.TXT, but now it is NOTEyyrrCA.TXT where yy is the (...) (15 years ago, 1-Jun-09, to lugnet.cad.dev)
|
| |
| | Re: LDraw.exe removed from distribution?
|
|
(...) Thanks, I think I'll check for the parts and p directories to determine if it's any kind of library, and issue a warning if ldconfig.ldr is missing when the official library is expected. ps: Sorry I responded slow, I'm having troubles posting (...) (15 years ago, 1-Jun-09, to lugnet.cad.dev)
|
| |
| | DATHeader version 2.0.4 for WINDOWS, LINUX and MAC
|
|
And here is the next release of DATHeader. The following happend: 1) Some more adjustments to recognize part type correctly 2) If EDIT commands used the current file will be unloaded. 3) Notify about wrong colors now without separate messages 4) (...) (15 years ago, 31-May-09, to lugnet.cad.dev, lugnet.announce, lugnet.cad)
|
| |
| | Re: DATHeader NEW as .NET application (version 2.0.1)
|
|
(...) I use it sometimes in the middle of part design to make sure I have a valid part header and be able to get smooth shading with LDView. Philo (15 years ago, 29-May-09, to lugnet.cad.dev)
|
| |
| | Re: LDraw.exe removed from distribution?
|
|
(...) I'd go with ldconfig.ldr. LDraw.exe is now legacy software (and is in fact not complaint with the current spec). Since ldconfig.ldr is per spec where color are defined, it should always be present in a 100% complaint distro. -Orion (15 years ago, 29-May-09, to lugnet.cad.dev)
|
| |
| | Re: DATHeader NEW as .NET application (version 2.0.1)
|
|
(...) If I would make the "Old Header" and "New Header" larger it would not fit good to smaller desktops. I am thinking of make to whole window able to maximise. That would then help both of us. At present DATHeader is designed to output a file that (...) (15 years ago, 28-May-09, to lugnet.cad.dev)
|
| |
| | Re: DATHeader NEW as .NET application (version 2.0.1)
|
|
Hello, I would like to have larger components "Old Header" and "New Header". Often the header does not fit to them and you have to scroll down both lists. And, please, make replacing "0" comments by "0 //" as option. This feature kill mlcad hide (...) (15 years ago, 28-May-09, to lugnet.cad.dev)
|
| |
| | LDraw.exe removed from distribution?
|
|
Hello all, I just downloaded the complete.zip and discovered LDraw.exe is no longer present. I take this is a step in creating the 100% CA distro? Anyhow, I always used LDraw.exe to validate (in LD4DStudio) if a folder is indeed the library's root. (...) (15 years ago, 28-May-09, to lugnet.cad.dev)
|
| |
| | Re: DATHeader version 2.0.3 for LINUX and MAC
|
|
(...) I have just found an error in DATHeader. The test for partdescription at subparts was not correct. Please download the bugfix from (URL) that side I have now also listed all tests that are performed by DATHeader and also the specification on (...) (15 years ago, 24-May-09, to lugnet.cad.dev, lugnet.announce, lugnet.cad)
|
| |
| | Re: DATHeader NEW as .NET application (version 2.0.1)
|
|
(...) Mike, I get a error on startup complaining about the xml file. I would also appriciate if you could add documentation for the new features (especially for the spaces in the title) explaining how it works and what's all about. Also some links (...) (15 years ago, 23-May-09, to lugnet.cad.dev)
|
| |
| | DATHeader version 2.0.3 for LINUX and MAC
|
|
I am proud to announce the release of DATHeader for the use on Linux and Mac machines. Windows machines are supported anyway. New feature in this version is the reviewer mode. You do not need to save the file to get the informations that DATHeader (...) (15 years ago, 23-May-09, to lugnet.cad.dev, lugnet.announce, lugnet.cad)
|
| |
| | Re: DATHeader NEW as .NET application (version 2.0.1)
|
|
(...) I have just tested the changed DATHeader also on UBUNTU/Linux with MONO. IT WORKS!!! Now as I have realized that there are differences between some functions that do the same on windows enviroment, but totally different on linux machines I am (...) (15 years ago, 18-May-09, to lugnet.cad.dev)
|
| |
| | Re: DATHeader NEW as .NET application (version 2.0.1)
|
|
(...) I have now found what happend. I use under windows the following code for a messagebox that gives an result back: answer = msgbox() But this does not work under MONO. Here I have to use: answer = messagebox.show(). So I have to check the (...) (15 years ago, 18-May-09, to lugnet.cad.dev)
|
| |
| | Re: DATHeader NEW as .NET application (version 2.0.1)
|
|
(...) At present I have no idea why color and rotation is not removed, but I will investigate. I did not checked the hand for being under MONO or not, only the function itself as I have detected trouble with that function under MONO. cu mikeheide (15 years ago, 17-May-09, to lugnet.cad.dev)
|
| |
| | Re: DATHeader NEW as .NET application (version 2.0.1)
|
|
(...) Thank you very much for your respond. As I noted before I have done some checks with MONO, but under windows enviroment. Now that I have your feedback I will try to eliminate those errors. As my UBUNTU (in a virtual box) does not run DATHeader (...) (15 years ago, 17-May-09, to lugnet.cad.dev)
|
| |
| | Re: DATHeader NEW as .NET application (version 2.0.1)
|
|
More (again on MONO): - Maybe turn the Option menu into a single Preferences button (like the ? button)? - Edit -> License Types -> Close closes DATHeader. Same for BFC Statements and Part Types - Edit -> Category brings up the popup box which asks (...) (15 years ago, 17-May-09, to lugnet.cad.dev)
|
| |
| | Re: DATHeader NEW as .NET application (version 2.0.1)
|
|
(...) Great job! Maybe one of the tools evolves so much that it becomes an all-in-one checker. :-) However for me it doesn't actually remove the COLOR definitions from files, nor the ROTATION definitions (it simply turns them into //-comments). (...) (15 years ago, 17-May-09, to lugnet.cad.dev)
|
| |
| | DATHeader NEW as .NET application (version 2.0.1)
|
|
Version 2.0.1 of DATHeader is now available for download at www.michael-heidemann.de as my other webspace is down :-( in the moment. There are now more tests performed. For example: - check for coplanarity (based on Philo's code) - check for double (...) (15 years ago, 17-May-09, to lugnet.cad.dev, lugnet.announce, lugnet.cad)
|
| |
| | Re: txt2dat 0.2.2
|
|
(...) Indeed, the default font, being based on the font used on LEGO tiles, was created without any kerning information. (...) Cool, no big hurry, the person that requested it doesn't use a Mac ;) ROSCO (15 years ago, 16-May-09, to lugnet.cad.dev)
|
| |
| | Re: txt2dat 0.2.2
|
|
(...) Update: kerning works fine with the "NASAlization" font on my site, so it's just a matter of using fonts that support the feature. Unfortunately it looks like the custom font upload feature is broken, so that's another thing to add to my list (...) (15 years ago, 16-May-09, to lugnet.cad.dev)
|
| |
| | Re: txt2dat 0.2.2
|
|
(...) I'm here! I'm catching up on LDraw developments. I updated txt2dat online to use the new version, so there is now a checkbox for the kerning option. I don't notice any difference with the default font, though, so either I haven't hooked it up (...) (15 years ago, 16-May-09, to lugnet.cad.dev)
|
| |
| | txt2dat 0.2.2
|
|
A new version of txt2dat is available. The only major change in this version is the addition of the -k option to specify glyph pair kerning. If you don't know what that means then you probably don't need it :) Get it here: (URL) that the Mac version (...) (15 years ago, 16-May-09, to lugnet.announce, lugnet.cad.dev)
|
| |
| | LETGUI new version 1.3.0.0
|
|
I have just uploaded a new version of LETGUI package, that contains the new tool Edger2 (Version 1.1). Added support for changed Ytruder V1.3. BUGFIX: If your file is located in a folder with spaces you where not able to view it with the editor or (...) (15 years ago, 15-May-09, to lugnet.cad.dev, lugnet.announce)
|
| |
| | New LDraw Tool for Parts author: Edger2
|
|
(URL) Lee Gaiteri's (URL) Edger> utility allows to create conditional lines between adjacent facets, and edge lines on outside (unmatched) facets. But it has a few drawbacks, such as requiring perfect match between facets (something hard to get (...) (15 years ago, 15-May-09, to lugnet.announce, lugnet.cad.dev, FTX)
|
| |
| | Re: Peeron_to_MLCad
|
|
(...) Hi Scott If I decide to write a new version of Peeron_to_MLCad I will take note of your suggestions. I am writing to you in private on technical aspects related to programming. (15 years ago, 11-May-09, to lugnet.cad.dev)
|
| |
| | Re: Peeron_to_MLCad
|
|
Now that I've had a chance to use Peeron_to_MLCAD, I must say again, excellent work. After getting everything setup, it was fun 'building' the model in MLCAD. The tutorial was great and very necessary, as I was overwhelmed by all of the buttons and (...) (15 years ago, 9-May-09, to lugnet.cad.dev)
|
| |
| | Re: Peeron_to_MLCad
|
|
That is pretty neat! It is kind of like getting a LEGO set in all digital form. All you need to do is put it together. I'll have to give this a try as soon as a I have some time. Thanks, Scott W. (15 years ago, 5-May-09, to lugnet.cad.dev)
|
| |
| | Re: Peeron_to_MLCad
|
|
(...) Jetro (15 years ago, 4-May-09, to lugnet.cad.dev)
|
| |
| | Peeron_to_MLCad
|
|
Hi All I have developed a program called Peeron_to_MLCad. It's useful to simplify the initial phase of implementation of existing Lego sets. With Peeron_to_MLCad is possible to reduce drastically the time needed to select the parts and find the (...) (15 years ago, 4-May-09, to lugnet.announce, lugnet.cad, lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: Convert to Wavefront object?
|
|
(...) Try: (URL) (15 years ago, 26-Apr-09, to lugnet.cad.dev)
|
| |
| | Re: Convert to Wavefront object?
|
|
(...) Yep. I created a minifig and imported the 3DS file into MeshLab. The improper BFC is very apparent. (You can see how part authors simply created one half of a part and then mirrored the primitives to create the other half.) -Mike (15 years ago, 14-Apr-09, to lugnet.cad.dev)
|
| |
| | Re: Convert to Wavefront object?
|
|
(...) Just to clarify, the above isn't quite accurate (on two points). First of all, LDView 4.0.1 (the latest release) doesn't support this at all. Secondly, LDView 4.1 (which is forthcoming, but hasn't had even a beta release yet) will have support (...) (15 years ago, 13-Apr-09, to lugnet.cad.dev)
|
