 | | Re: announcing TrackDraw (BrickFest preview)
|
|
(...) There is nothing wrong with using .NET, and most of the "crap" you refer to is already present in Windows XP. I've developed many .NET programs and they all work well and my clients are all happy with the way .NET works on their systems. (...) (21 years ago, 7-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: announcing TrackDraw (BrickFest preview)
|
|
(...) Why you did it in MICRO$OFT .NET now if we want to use your program we need to install 30mb of crap .NET anyway your program is the 1st ine to use it I haven't seen any yet apart from MICRO$OFT LONGHORN a.k.a next windows in 2005 (21 years ago, 7-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: announcing TrackDraw (BrickFest preview)
|
|
(...) I noticed you're using .Net So it might actually work on Linux boxes since the Framework is also available for Linux. See: (URL) for more info about a .Net framework implementation. -Frank (21 years ago, 7-Aug-03, to lugnet.cad.dev, lugnet.off-topic.geek)
|
| |
| | Re: Orange in LDraw
|
|
Another solution is to leave things alone, but change the applications palette to suit the user's taste. Color is tricky. (21 years ago, 7-Aug-03, to lugnet.cad.dev)
|
| |
| | announcing TrackDraw (BrickFest preview)
|
|
I've been working on TrackDraw, a replacement for Track Designer, for six months or so. I'll talk about it at BrickFest on Saturday. You can read a little about it, and see the BrickFest PowerPoint slides here: (URL) not ready to release the program (...) (21 years ago, 6-Aug-03, to lugnet.trains, lugnet.events.brickfest, lugnet.cad.dev) !
|
| |
| | Re: Star Wars mini models 1st wave render & Orange in part
|
|
(...) Maybe a light source is really close, but the blue seems rather bright. I'll have to try it myself. There's not an official LDraw color for Dark Blue yet, is there? I checked (URL) (...) 484 looks like the right orange to me, based on your (...) (21 years ago, 6-Aug-03, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Star Wars mini models 1st wave render & Orange in part
|
|
(...) It is dark blue. In fact that's the darkest I can get it wiht LDraw color number since I used dithered Black and Blue. (...) Unfortunately no (...) I used 484. 25 seemed too dark. -Orion (21 years ago, 6-Aug-03, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Star Wars mini models 1st wave render & Orange in part
|
|
(...) Looks nice, esp. the AT-ST. Colors seem wrong on the Slave I (I think the blue should be dark blue). Missing the TIE Bomber, though. Are the cylinders for the TIE Bomber up yet? Question related to another topic: what color orange did you use (...) (21 years ago, 6-Aug-03, to lugnet.cad.ray, lugnet.cad.dev)
|
| |
| | Re: Orange in LDraw
|
|
(...) I personally prefer 484 over both 25 & 462, although this may be an optical trick (brain sees a progression, and logically picks the middle color as the correct color). But 462 is defintely too yellowish. John P.S. I FTXed Orion's message. (21 years ago, 6-Aug-03, to lugnet.cad.dev, FTX)
|
| |
| | Orange in LDraw
|
|
I did a color comparison of the color orange in LDraw: (URL) brick on the left is the current LDraw color 462 The brick in the middle is color 484, the dither of Yellow and Red (the dither of Red and Yellow, 334, is currently defined as Gold Chrome) (...) (21 years ago, 6-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: LEdit Command line question [DAT]
|
|
(...) The only way to do this with LEdit is to create your own part file, consisting of one line: 1 16 0 -24 20 1 0 0 0 1 0 0 0 1 3001.dat If you store that file in your ldraw\parts directory, you can use it in LEdit as a part, in place of 3001.dat. (...) (21 years ago, 6-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: Command line commands in dat parts
|
|
(...) But for the less commonly used tools ... it does nothing. At this time, CMDLINE is really just a comment. Maybe someday, some renderer/editor will make use of it, but not yet. Steve (21 years ago, 6-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: LEdit Command line question
|
|
(...) Most of the meta commands are used outside of the original LEdit program. ROTATION CENTER is currently only used in MLCad (I make use of it frequently). If you're not able to use MLCad (I don't see why not), then I suggest making a custom part (...) (21 years ago, 4-Aug-03, to lugnet.cad.dev)
|
| |
| | LEdit Command line question
|
|
My ignorance of meta-commands is very nearly complete, so I throw myself on the mercy of my peers here in lugnet.cad.dev Is there a way to "set" the rotation point of a part that will work in LEdit? For example, if I'd like the 2x4 brick 3001.dat to (...) (21 years ago, 4-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: Command line commands in dat parts
|
|
(...) I forgot to add that this link: (URL) my draft LDraw spec and it contains a list of all the known META commands and links to the website for the programs that use them -Orion (21 years ago, 4-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: Command line commands in dat parts
|
|
(...) It's a LDLite META Command. Supposedly the command gives a default color for the part though I've never really seen it in action. For the most commonly used tools (MLCad, LeoCAD, L3P) this command does nothing. -Orion (21 years ago, 4-Aug-03, to lugnet.cad.dev)
|
| |
| | Command line commands in dat parts
|
|
Can someone tell me what a "CMDLINE -C0" means? And if there is a website that explains what the other commands are and how they are used. Thank you, Paul (21 years ago, 4-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: * LDrawDesignPad LDDP 1.5 Beta released *
|
|
(...) Well this problem my be out of our hands. We've been using SynEdit for our editing component and since this code is not written by us, fixing problems with it is difficult. (...) When code ocmponent that we used for the editor was swapped the (...) (21 years ago, 3-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: * LDrawDesignPad LDDP 1.5 Beta released *
|
|
(...) [SNIP] (...) I’d like to move the triple 3, say, into position 1 or another line. I click and select the 3 numbers + spaceholders. once the triple is selected in 1.4 the cursor becomes an "arrow" and you can drag’n’drop the selection into the (...) (21 years ago, 3-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: * LDrawDesignPad LDDP 1.5 Beta released *
|
|
(...) I don't know what he is using, but I do know that enabling and disabling menu animations can produce completely unexpected side-effects. Assuming your Windows version is recent enough to support menu animations, you might want to switch them (...) (21 years ago, 3-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) That's right, Don. Please see (URL) continued: (...) Yes, it will. Tony said: (...) Good initiative! If the file gets too big or unhandy for POV, I will reconsider the L3PARTS mentioned in (URL) (21 years ago, 3-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: * LDrawDesignPad LDDP 1.5 Beta released *
|
|
(...) I'm not sure what you mean by Drag 'N Drop. Could you elaborate more? (...) Again, I not sure what you mean. (...) Hmm... I have a look at it. I pretty much just ported the code from L3Check to Delphi. (...) I'll put this on the todo list. (...) (21 years ago, 2-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: * LDrawDesignPad LDDP 1.5 Beta released *
|
|
(...) hi, thx for making a great tool even better. I really like the winding button and the fakt that now you can select multiple lines and rewind them in one go! working with the old plug-in was a lot of clicking and mouse-hoovering (nontheless thx (...) (21 years ago, 2-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: * LDrawDesignPad LDDP 1.5 Beta released *
|
|
To all those who downloaded and got an '.dll not found' error after install, I've uploaded the fix to this problem. -Orion (21 years ago, 2-Aug-03, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
This is just my opinion since I started all this by suggesting to Lars to add POV support into L3P in the first place. By adding a few .dat primitives (not POV primitives) to the .dat definition, then you don't have to tie yourself to any renderer. (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Now that would rock. For my personal use, this would almost entirely solve the problem. I could whip up a single file that contains all the parts I want to fix, run it through L3P, manually fix the parts in the resulting file, and then include (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) I asked Lars a while back if he could wrap all the part definitions with IF NDEF statements so that someone could define the parts they wanted in an external include file and the rest would use the standard L3P code. Hopefully when a new (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Because parts with inline POV code work with the version of L3P that we have now. Why not start by building a library of modified official parts, but with the explicit goal of eventually converting them into POV only parts when L3P or some (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest? [DAT]
|
|
(...) Here is my $0.01.... This is how I have started handling Ldraw/PoV parts: The 3626bp6f.dat is availabe on the parts tracker here: (URL) is some line wrapping happening here, I will need to fix it later) 0 Minifig Head with Female Eyes with Red (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) I agree with Steve on this issue: no POV code in offical parts with the possible exception of primitves. I feel this way for a few reasons: - It could be construed the POV is the Official rendering program of the LDraw.org library. This can (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Why not just a library of POV code only parts, ala LGEO/Raves, only compatible with the LDraw.org library? We could host this project on Sourceforge so anyone who was interested could develop. I think if we do it Pov only, LDraw.org is more (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Okay... then I'd like to open this up to a question for the community: Is anyone interested in working on a single shared repository of ldraw-compatible parts with inlined POV-Ray code? How many authors out there are comfortable with both (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) Yes, it's pretty much still the case. I would really prefer to not have any POV code in the parts library at all. But if there must be some, I think it should stay in the primitive files. (...) I think a better solution is to work on POV (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Inline POV code in official parts?
|
|
What's the current plan for POV-Ray code in official parts? I have been out of the loop for a while, but my last understanding was that parts with inline POV-Ray code don't have any chance of getting certified on the parts tracker. Is this still the (...) (21 years ago, 28-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Primitive substituion and part reviews
|
|
(...) They should not warrant a Hold review. Put comments in the review, and if you think the issue is serious enough, go for a NoVote review. (...) If the pattern allows, it would be good to add a color-matched ring primitive around the outside of (...) (21 years ago, 28-Jul-03, to lugnet.cad.dev)
|
| |
| | Primitive substituion and part reviews
|
|
To what extent, if any, should rendering errors caused by primitive substitution warrent a Hold vote on the PT? An example of this would be a disc shaped pattern surrounded by a ndis. Would it be appropritate to add a small, color matching ring (...) (21 years ago, 27-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) So you're saying that if I ask for the GL_RENDERER etc strings after a window resize I'll get the same ones I started with no matter what? (I added some code to check it anyway just in case) That really sux. Who designed that feature, (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) OK, I looked at the code above, and all it seems to do is tell its OpenGL context to update every time the window is resized. If their glut doesn't do this, then it is broken. As far as I know, there isn't any equivalent to this in Windows. (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) Found some more info. This makes it even more clear. (URL) it only shows icky Cocoa code. I may have to examine the apple glut sources to see how much of this is actually handled in glut. I wouldn't be suprised to find some bugs there. And I (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) The OS is selecting the drivers. If I want to select them myself I have to write all sorts of icky OS specific code. (...) It gets worse. I did some searching on this. Apparently, according to the source on this page, I may need to check if my (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
