 | | Re: number notation in official parts
|
|
(...) Thanks for the info. I've always used perl scripts to convert oddly formatted data to a consistent format and then read it like that. Nice to know I don't always have to. If it could only read some of the more bizarre Fortran formats I'd never (...) (14 years ago, 12-Mar-10, to lugnet.cad.dev, lugnet.off-topic.geek)
|
| |
| | Re: number notation in official parts
|
|
(...) All float specifiers (e, E, f, g, G) are treated identically by the scanf functions. When scanning floats, they always recognize all float formats. One other thing about %g on output is that it automatically strips trailing zeros, which %f (...) (14 years ago, 12-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) Ahhh. I'd never heard of %g before now. I'm so used to %f and %e it had never occured to me that there might be a mixed option. Handy to know as I suspect it would be helpful in reading files of unknown format. I'm sure Delphi has some hideous (...) (14 years ago, 12-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) Actually, in C, %g does exactly this. Having said that, I think LDDP is a Delphi app, so it uses Pascal, and I don't remember how Pascal does formatting. --Travis (14 years ago, 12-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) I definitely know this. I see them far too much in my job as a numerical physicist ;) My point is that to write in mixed format (some %f and others %e) requires some strange coding unless there is a weird language which does it automatically. (...) (14 years ago, 12-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) Hmm, I thought I killed that "feature". I'll look into it as I find time to finish up LDDP 2.1 -Orion (14 years ago, 11-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) I mostly agree with this policy. (...) There is nothing strange in the routines, it is the standard format used to represent very large or very small numbers in a limited number of digits. Actually since values never get very large in LDraw (...) (14 years ago, 11-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) My suggestion would be to read numbers in that notation but never write them. I'm not sure why LDDP would write them that way (it would require some strange output routines) but if one thing writes them then it's best to read them. Tim (14 years ago, 11-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) I think it should be forbidden in official files as the benefit is very small and it is not good human readable. Benefit would be smaller filesize, as 0.0004 (6 characters) has more characters than 4E-4 (4 characters). Against could be 0.4 (3 (...) (14 years ago, 10-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) Such notation is not noted in any specs.. neither allowed or forbidden. At least, I can't find such. Maybe we should bring this up at LSC at some point? (FWIW I sent this in yesterday but it seems the server ate the message.. resending it) (...) (14 years ago, 9-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: number notation in official parts
|
|
(...) Such notation is not noted in any specs.. neither allowed or forbidden. At least, I can't find such. Maybe we should bring this up at LSC at some point? -Santeri (14 years ago, 9-Mar-10, to lugnet.cad.dev)
|
| |
| | number notation in official parts
|
|
If I rotate a part in LDDP the result may look like this: 1 16 4E-15 4 -20 0 0 1 0 -1 0 -1 0 0 stud4.dat This can be read by LDView and MLCad as a valid number. Is such notation allowed in official parts? It is nowhere explicit allowed or (...) (14 years ago, 8-Mar-10, to lugnet.cad.dev)
|
| |
| | LDSwitch Sample #1: Do/Undo [DAT]
|
|
Don't know if you prefer to make input here or at SourceForge, so I crosspost. Please give feedback where you like, here or at SF. Here's the first sample LDraw code snippet. Set the value of the variable Rev028_Changes to Do or Undo, run the (...) (14 years ago, 23-Feb-10, to lugnet.cad.dev)
|
| |
| | LDSwitch Project on SourceForge
|
|
(...) I've just registered myself and my first project at SourceForge: (URL) to join or just input! /Tore (14 years ago, 23-Feb-10, to lugnet.cad.dev)
|
| |
| | LDSwitch?
|
|
Is the name/keyword/META-command LDSwitch/!LDSWITCH free to use or is it taken? I think it's not taken (in the LCad context), so I wish to claim it if noone protests. /Tore (14 years ago, 23-Feb-10, to lugnet.cad.dev)
|
| |
| | Re: Undo/Redo Information META Tags? Or Options Buttons?
|
|
(...) And I'm not sure this would be the optimal solution either. This options thing is more like a case switch than a series of if statements. (...) Thanks for your input, Kevin. I am looking for a friendly solution that won't output any code that (...) (14 years ago, 19-Feb-10, to lugnet.cad.dev)
|
| |
| | Re: Undo/Redo Information META Tags? Or Options Buttons? [DAT]
|
|
(...) Well, you could easily do the above using the C preprocessor and #ifdefs, but that would be outside any LCAD application (and make the original file hard to work with in any modeler). #ifdef LDBOXTER_LEVEL_D /* crude simplification */ 1 15 0 (...) (14 years ago, 19-Feb-10, to lugnet.cad.dev)
|
| |
| | Undo/Redo Information META Tags? Or Options Buttons? [DAT]
|
|
I've been thinking hoe nice it would be if there was some kind of system of tags that enabled the user to store undo and redo information in a model after the model building application is closed. Now, there are a great number of LCAD apps of which (...) (14 years ago, 19-Feb-10, to lugnet.cad.dev)
|
| |
| | Defining LED Colors in LDConfig?
|
|
I've been thinking about that talk of limiting the colour definitions in LDConfig.ldr to part colours with a few expectations, and I agree with that. But I wish to throw in an idea that I don't even believe in myself but yet want to air. Is it (...) (14 years ago, 10-Feb-10, to lugnet.cad.dev)
|
| |
| | Re: LDraw Names for Monorail Parts
|
|
(...) It makes more sense for "Monorail" to be a valid CATEGORY than some of the existing ones, so I added it a while ago. The definitive list is at (URL) Chris (14 years ago, 21-Jan-10, to lugnet.cad.dev, lugnet.trains)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) I'm using WinGrep ((URL) and/or Copernic Desktop Search ((URL) for local searching, and have turned off all Windows indexing. Copernic is awfully fast (but it creates huge indexes), while WinGrep is better (IMO) for source code searches. The (...) (15 years ago, 22-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: Unofficial Parts Path
|
|
(...) This is a nice tip, thank you. Yes, I agree that it would be nice to be able to arbitrarily enable/disable/set/configure the paths LDraw (ok, maybe not ldraw.exe and ledit.exe per se) uses to search for parts. Mike (15 years ago, 22-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) This is true in XP as well if you have "Windows Desktop Search" (or something similar) installed. I wish I could disable *that*. (15 years ago, 22-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) Yeah, and the "improvements" in Vista and Windows 7 are, as far as I'm concerned, even worse. Also, I'm not sure how XP behaves, but in Vista/Windows 7 if you have indexing turned on and search new files, it will silently not return any (...) (15 years ago, 21-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) Thanks, Travis, I have already managed to chase that annoying dog away, it was just to right-click on him or so. Maybe I'll turn that whole assistant off, too. Isn't it strange that in the efforts of making the search faster and easier, they (...) (15 years ago, 21-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) I know your question has already been answered, but to get rid of the dog, see here: (URL) getting it to search all files is also described here: (URL) that the above solution should work even if you have indexing turned off. I'm not sure if (...) (15 years ago, 21-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) 2" worked just splended. /Tore (15 years ago, 20-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) Read here, (URL) how to add extensions to the XP file search. Or get WinGrep, (URL) Anders Isaksson (15 years ago, 20-Dec-09, to lugnet.cad.dev)
|
| |
| | Re: XP File Search Refuses To Search .LDR Files!
|
|
(...) Aah, nevermmind. I installed good old Total Commander and got a much better file search without bugs and foolishly grinning dogs. /Tore (15 years ago, 20-Dec-09, to lugnet.cad.dev)
|
| |
| | XP File Search Refuses To Search .LDR Files!
|
|
Sorry for posting slightly off-topic, but the X-Pee thing drives me completely insane. I do a file search just like I always have done in previous systems, but in XP, the search fuction just refuses to search in .ldr files. I was looking for (...) (15 years ago, 20-Dec-09, to lugnet.cad.dev)
|
| |
| | Inliner is back
|
|
You may have noticed that Inliner have had problems with winding. That should be solved now. You can find the current version (2.2.0.0) at (URL) (15 years ago, 11-Dec-09, to lugnet.cad.dev)
|
| |
| | LDConfig Manager 1.0
|
|
Because of the current discussion about the LDConfig.ldr I needed a tool to visualisise all the used colors. So I just coded LDConfig Manager. It is far from beeing complete and maybe buggy, but it works for me. Maybe you are also interested in (...) (15 years ago, 6-Dec-09, to lugnet.cad.dev, lugnet.announce, lugnet.cad)
|
| |
| | Re: LDraw Boxer development
|
|
(...) There are some additional boxes on my web page: (URL) is indeed a very useful tool. I just wish I had more time to create boxes. Mike (15 years ago, 25-Nov-09, to lugnet.cad.dev)
|
| |
| | LDraw Boxer development
|
|
I am happily surprised to see that my old utility ldboxer is still in use. (URL) may have underestimated the potential of this idea. However, it needs a total upgrade. First, we need to add new parts to the \B library. Please come in with (...) (15 years ago, 24-Nov-09, to lugnet.cad.dev)
|
| |
| | LETGUI new version 1.4.0.0
|
|
I have just uploaded a new version of LETGUI package, that contains the new tool Slicerpro (Version 1.1). You can download the updated package from (URL) (15 years ago, 1-Nov-09, to lugnet.cad.dev, lugnet.announce, lugnet.cad)
|
| |
| | Re: calc_z4.c (Was: Math Problem Again)
|
|
(...) True, but such triangles will not be visible in the 2-D front view of the UI and therefor not clickable - unless the program is buggy. And if you can't click on them, the function never has to encounter data from them. Hopefully... /Tore (15 years ago, 26-Oct-09, to lugnet.cad.dev)
|
| |
| | Re: Unofficial Parts Path
|
|
[SCAN_ORDER] 1 = SHOW <LDRAWDIR>Parts 2 = HIDE <LDRAWDIR>Parts\s 3 = HIDE <LDRAWDIR>P 4 = HIDE <LDRAWDIR>P\48 5 = SHOW <LDRAWDIR>Unofficial\Parts 6 = HIDE <LDRAWDIR>Unofficial\Parts\s 7 = HIDE <LDRAWDIR>Unofficial\P 8 = HIDE (...) (15 years ago, 25-Oct-09, to lugnet.cad.dev, FTX)
|
| |
| | Re: calc_z4.c (Was: Math Problem Again)
|
|
(...) Actually, if the original triangle is (for example) in the Y-Z plane, then just passing in an x4 that's different from x1, x2, and x3 will result in a failure. The equivalent goes for an initial triangle in the X-Z plane. --Travis (15 years ago, 25-Oct-09, to lugnet.cad.dev)
|
| |
| | Re: Unofficial Parts Path
|
|
(...) Ten letters folder name... may it always remain a quasi standard! /Tore (15 years ago, 25-Oct-09, to lugnet.cad.dev)
|
| |
| | Unofficial Parts Path
|
|
Unofficial Parts Path Unofficial parts should not mixed with official part. Therefore the a quasi standard has been established as follow: Unofficial files should be stored in a directory structure like follows: <LDRAWDIR>/Unofficial/P (...) (15 years ago, 25-Oct-09, to lugnet.cad.dev)
|
