 | | 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)
|
