 | | Re: dll file for use with Visual Basic Express
|
|
(...) I should be more clear with VB. I am talking about VBExpress that is a NET Framework language. As far as I understand with the NET Framework it is possible to use a DLL that is written in VB also with the other Framework languages. So maybe it (...) (16 years ago, 19-Jun-08, to lugnet.cad.dev)
|
| |
| | Re: Edge lines in patterns
|
|
(...) Well :-) The short answer is that I was using 606p02 as a reference, and it has edge-lines... I have now been made aware that this wasn't the best example I could have picked :-D Anyway...I'm about to start an overhaul of all the 32x32 (...) (16 years ago, 19-Jun-08, to lugnet.cad.dat.parts, lugnet.cad)
|
| |
| | Re: dll file for use with Visual Basic Express
|
|
(...) I really should have responded to your original message before posting my message about LDView's parser. As far as I'm concerned, having a public VB parser for LDraw files would be great. I won't use it, but if others find it useful, that's (...) (16 years ago, 19-Jun-08, to lugnet.cad.dev)
|
| |
| | Re: dll file for use with Visual Basic Express
|
|
(...) I know that LDView is a very good tool. And I know also that the code is under GPL. But there are people out there (me too) that do not know about C or C++. So it would be great to have a DLL to handle the core methods (and maybe objects) for (...) (16 years ago, 19-Jun-08, to lugnet.cad.dev)
|
| |
| | Re: New POV-Ray Edge Tracing Utility
|
|
(...) Ah, thanks for the clarification. -Mike (16 years ago, 19-Jun-08, to lugnet.cad.ray)
|
| |
| | Re: dll file for use with Visual Basic Express
|
|
I forgot to mention something fairly important (which may be obvious). LDLoader is a library for loading LDraw files into an internal memory format that is easy to deal with. It handle parsing, error checking (and reporting, via callbacks), and some (...) (16 years ago, 18-Jun-08, to lugnet.cad.dev)
|
| |
| | Re: dll file for use with Visual Basic Express
|
|
(...) For what it's worth, LDView is Open Source (GPL v2), and all of its LDraw file loading code is kept in a separate library (which I call LDLoader). This library depends on one other of my libraries (which I call TCFoundation, short for Travis (...) (16 years ago, 18-Jun-08, to lugnet.cad.dev)
|
| |
| | Re: New POV-Ray Edge Tracing Utility
|
|
(...) It certainly COULD be modified. However, it's up to Lars whether or not this actually happens. I looked at the mesh2 syntax, and changing to using it wouldn't really be trivial (although it probably wouldn't be all that difficult). Bear in (...) (16 years ago, 18-Jun-08, to lugnet.cad.ray)
|
| |
| | Re: dll file for use with Visual Basic Express
|
|
(...) I like the idea, I had some head breakers while trying to read LDraw files correctly the first time (especially regarding to reading recursive winding information). But I think, if there was going to be an 'official' LDraw api it should be (...) (16 years ago, 18-Jun-08, to lugnet.cad.dev)
|
| |
| | Re: New POV-Ray Edge Tracing Utility
|
|
(...) Could L3P be modified to use the mesh2 primitive? I notice also that L3P doesn't output the "insidevector" parameter, so LDraw creations can't be used in CSG operations. This is disappointing. -Mike (16 years ago, 17-Jun-08, to lugnet.cad.ray, FTX)
|
| |
| | License questions
|
|
Hello All, I'm starting work on POV-Ray export for my LD4DStudio project and was wondering about the LDraw license. I'm planning to generate POV-Ray files/objects per highlevel LDraw part. In the resulting source I will include all '0' lines from (...) (16 years ago, 18-Jun-08, to lugnet.cad.dev)
|
| |
| | Re: dll file for use with Visual Basic Express
|
|
(...) I like the idea. Naturally, I would like a portable LDraw library even better. How useful would a VB library be to Linux or Mac LDraw users? (There are at least a few!) In any case, a generic API could certainly make it easier to create new (...) (16 years ago, 17-Jun-08, to lugnet.cad.dev)
|
| |
| | dll file for use with Visual Basic Express
|
|
Is there anybody that it interested in an dll that comes with objects and methods to handle ldraw related files? It would not be for showing the parts but could be base to develop that. Any comments are welcome. cu mikeheide (16 years ago, 17-Jun-08, to lugnet.cad.dev)
|
| |
| | Re: Edge lines in patterns
|
|
(...) I think we do not need to specify the use of edgelines more than we have done, if everybody knows what edgelines are and that in some cases they are not shown in pictures/renderings. So they should be as nature only on edges. If there are (...) (16 years ago, 17-Jun-08, to lugnet.cad.dat.parts, lugnet.cad)
|
| |
| | Re: Edge lines in patterns
|
|
(...) The spec intentionally didn't put absolute limits on what color 24 could be used for, so I think it's up to the reviewers. My tendency would be to hold the part, but not because it does something that goes against the spec, but instead because (...) (16 years ago, 17-Jun-08, to lugnet.cad.dat.parts, lugnet.cad)
|
| |
| | Edge lines in patterns
|
|
Hi guys, I thought we had specs for almost everything, but I was proven wrong. Looking at this pattern (URL) see 24colored edges around the pattern. I was going to hold vote it, since I never "edged" a pattern - and I made a lot of them in my career (...) (16 years ago, 17-Jun-08, to lugnet.cad.dat.parts, lugnet.cad)
|
| |
| | Re: Another part review question - about headers
|
|
(...) Hi Jim, since the admins check the header and also modify them before shipping (Unofficial to Official for example) I would just "novote with comments" for NEWLY submitted parts to make the author aware of the new specs and the tools (...) (16 years ago, 17-Jun-08, to lugnet.cad)
|
| |
| | Re: Another part review question - about headers
|
|
(...) Thanks, Steve. I wasn't sure there even were issues with the header - I was just looking for example reviews, and trying to figure out what purpose, if any, the specifications play. Jim (16 years ago, 17-Jun-08, to lugnet.cad)
|
| |
| | Re: Another part review question - about headers
|
|
(...) If the header is the only problem, certifying is fine -- just note the issue, so the admins can clean up the header later. If it's a question of the header's content (ie, "is that the right title?", etc), then you might go for novote. (...) (...) (16 years ago, 17-Jun-08, to lugnet.cad)
|
| |
| | Re: Another part review question - about headers
|
|
(...) Hi Willy, Thanks for the background. So, if the header just needs to be cleaned up, you recommend novote with a note about the header format? If I can ask for one more example, how would you respond to a header like this? 0 Car Mudguard 4 1/2 (...) (16 years ago, 17-Jun-08, to lugnet.cad)
|
