 | | Re: Problem with MLCAD arrows in other programs - and how to solve it
|
|
(...) Previous to the arrow generation version of MLCad, GHOST only applied to the line in which it is specified. It had no impact on any other lines. Now the definition of GHOST has changed. GHOST on the MLCAD ARROW line *implies* ghosting on the (...) (20 years ago, 30-Dec-04, to lugnet.cad)
|
| |
| | Problem with MLCAD arrows in other programs - and how to solve it [DAT]
|
|
Hello, when I used the new MLCAD arrows in submodels, I always had one problem: I couldn't ghost them. Only MLCAD interpreted the ghosted arrows correctly, the other programs (LPub, LDView...) didn't. Where's the problem? MLCAD does not ghost the (...) (20 years ago, 30-Dec-04, to lugnet.cad, lugnet.cad.ray, lugnet.cad.mlcad)
|
| |
| | Boat rigging and 3-way cylinder intersection
|
|
Wondered when these (pn 6057 and pn 2541) would be pulled up! I suppose I should have asked back when I sub-parted the small rigging to make the large rigging, but I took the easy way out and just stuck with how the original official part had done (...) (20 years ago, 30-Dec-04, to lugnet.cad.dat.parts)
|
| |
| | Re: more detailed Status (of File) in Parts Tracker?
|
|
(...) And in the past, I believe replies have universally disagreed with your position. Just to be clear, let me restate my position: Blindly ignoring unofficial fixes to subfiles would allow the PT to certify files for release that reviewers would (...) (20 years ago, 29-Dec-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: MPD Wizard 1.0b
|
|
(...) That's a great suggestion. It gives me something to work on when I fly back home on Thursday. -Orion (20 years ago, 29-Dec-04, to lugnet.cad.dev)
|
| |
| | Re: BBB wheels
|
|
(...) Just to clarify, yes they are usable, but at over 600K and 10000 lines each, they use some serious resources when rendering. I unfortunately don't have a computer with a huge amount of resources, and I don't think it's necessary. I assume they (...) (20 years ago, 29-Dec-04, to lugnet.cad.dat.parts)
|
| |
| | Mac MPD Utility 1.2.1
|
|
Hello folks! I'm pleased to announce Mac MPD Utility (MMU, to coin an acronym) has been updated to version 1.2.1, which adds a few new features and a bit of resilience to the 1.2 look. You can download this 50k behemoth at: (URL) metadata is fixed (...) (20 years ago, 28-Dec-04, to lugnet.cad.dev.mac)
|
| |
| | Re: BBB wheels
|
|
(...) I too have used them without any noticable problems. I don't know how efficiently modelled they are but they are quite a complicated (in terms of amount of faces) part. Tim (20 years ago, 28-Dec-04, to lugnet.cad.dat.parts)
|
| |
| | more detailed Status (of File) in Parts Tracker?
|
|
Happy Holidays, Y'all! :D I have brought up, in the past, a point of concern I have with the Status displayed by the Parts Tracker. I have believed, and continue to believe, that a file's Status should be calculated *independently* of whatever (...) (20 years ago, 28-Dec-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: MPD Wizard 1.0b
|
|
(...) Yes, as I didn't try to change it on the fly ;o) An optimisation that could be done would be to remove one of the two spaces before subfile names. To make MPDWizard the Swiss army knife of MPD, you could add a "Test MPD" function that would (...) (20 years ago, 28-Dec-04, to lugnet.cad.dev)
|
| |
| | Re: MPD Wizard 1.0b
|
|
(...) Cool, thanks. I've been programming in Delphi for 3 years now but my knowledge is all self taught and I learn something new just about everytime I set down to code. (...) It was in FormCreate, I forget why I moved it. I think I'll move it (...) (20 years ago, 28-Dec-04, to lugnet.cad.dev)
|
| |
| | Re: MPD Wizard 1.0b
|
|
(...) Not entirely. The program may still do wrong when the Windows settings are changed while the program is running. I recommend the following at the end of Main.pas (not in FormActivate): ... initialization Application.UpdateFo...atSettings := (...) (20 years ago, 27-Dec-04, to lugnet.cad.dev)
|
| |
| | Re: ~Use and ~Moved
|
|
(...) But I just don't think there is a need to some big changes. For example LEGO's internal taxonomy is simply horrid (AFAIK). (...) Hm, I don't think so. For example some set references 44237 and I don't have any 44237... Does that mean I can (...) (20 years ago, 27-Dec-04, to lugnet.cad.dat.parts)
|
| |
| | Re: MPD Wizard 1.0b
|
|
(...) I'm curious, did I fix the decimal separator issue? -Orion (20 years ago, 27-Dec-04, to lugnet.cad.dev)
|
| |
| | Re: ~Use and ~Moved
|
|
(...) No big deal. :) Peeron uses ~Use tags, LDraw doesn't. (...) I feel that it's unlikely that all fans are going to change their behaviour/data whenever TLC makes a switch. There are too many of us, and we all have different levels of access, (...) (20 years ago, 27-Dec-04, to lugnet.cad.dat.parts)
|
| |
| | Re: MPD Wizard 1.0b
|
|
(...) Thanks Orion, works fine now! Philo (20 years ago, 27-Dec-04, to lugnet.cad.dev)
|
| |
| | Re: ~Use and ~Moved
|
|
(...) Sorry, I didn't know that, I thought it was an LDraw issue. (...) It's also the id currently in use by TLC and I think it's easier to mimic their system as close as possible, than to reinvent a wheel. (...) Aliasing is the reply. 44237 and (...) (20 years ago, 27-Dec-04, to lugnet.cad.dat.parts)
|
| |
| | Re: ~Use and ~Moved
|
|
(...) I think this is a Peeron question more than an LDraw question. For me, it would be confusing to have two different numbers in use for what's a functionally identical part. It kind of depends on the direction you're coming from -- as far as (...) (20 years ago, 27-Dec-04, to lugnet.cad.dat.parts)
|
| |
| | Re: ~Use and ~Moved
|
|
(...) I think I'm missing something here. I downloaded 44237 from the PT and couldn't find "~Use" anywhere. In fact, I don't think I've seen "~Use" in official part files. -Orion (20 years ago, 27-Dec-04, to lugnet.cad.dat.parts)
|
| |
| | ~Use and ~Moved
|
|
Hi, could anybody explain these? For example 44237 is valid mold number for 'new' Brick 2 x 6. I don't know what are differences to 2456 and I don't care much. For inventory purposes the number 44237 is important, I think. So why '~Use' - why it (...) (20 years ago, 27-Dec-04, to lugnet.cad.dat.parts)
|
