To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 11022 (-40)
  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)


Next Page:  5 more | 10 more | 20 more | 40 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR