| | Re: LPub 4 Callouts (and other questions)
|
|
(...) models, so it is quite common for the assembly not to fit on the page. The workaround I have used so far is to make my own custom assembly images from LView and them manually put them in the final PDF file. That's what I did (URL) here>. Eric (15 years ago, 4-Dec-09, to lugnet.cad, FTX)
|
|
| | Re: Color page updated
|
|
Nobody ever listens to me on the issue of colors, but that doesn't mean I'll go quietly... (...) I don't see why they need to be added to the ldConfig file as long as they're documented somewhere and accepted as the standard default LDraw pallette. (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Official alternative model of set 8671
|
|
Hello, In the instructions of set 8671 (Racers - Ferrari F430 Spider 1:17) it says there are buildinginstrucions of an alternative model to be found on (URL) Alas these instructions were removed. The topic of missing or removal of official building (...) (15 years ago, 4-Dec-09, to lugnet.cad.dat.models.sets)
|
|
| | Re: LPub 4 Callouts (and other questions)
|
|
(...) OK, here goes. When an assembly is too large to fit on the page, LPub crops the image. When one drags the assembly image to another position LPub does not redraw the image. See: (URL) (15 years ago, 4-Dec-09, to lugnet.cad)
|
|
| | Re: Color page updated
|
|
(...) Sorry, but I really cannot understand the need to encode dithered colors. Personally I think that only colors used for parts should be coded, while, when you create a patterned part you can choose to use a "good enough" already coded color or (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: Color page updated
|
|
(...) It might fix it (I think it would still gum up the PT with over-zealous hold votes); but why break anything when we're just talking about adding fewer than 200 lines to the config file? I think it's a terrible idea to make dozens of (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
|
|
| | Re: Color page updated
|
|
(...) I have had parts on the Part Tracker held because they used one of these colors. That means it is limiting. (...) Color numbers 32-47 and 256-511 is not every color under the rainbow. (...) This is exactly the problem. (...) If this is the (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
|
| | Re: LPub 4 Callouts (and other questions)
|
|
(...) Well, I'm interested in helping to maintain current builds for the Macintosh. We're still at 4.0.0.1. If you update the SourceForge page with the current code, I will work on that - and then my interest might be rekindled enough to delve (...) (15 years ago, 3-Dec-09, to lugnet.cad, lugnet.cad.dev.mac)
|
|
| | Re: LPub 4 Callouts (and other questions)
|
|
(...) Hi Willy, This is not the kind of help I was asking about. I was asking if anyone was interested in helping with the software development of LPub. It is getting too large for one person to work on alone. If would seem you have issues with the (...) (15 years ago, 3-Dec-09, to lugnet.cad)
|
|
| | Re: Color page updated
|
|
(...) There are already two very old ways to specify RGB colors in LDraw files. One comes from ldlite with somewhere between 12 and 15 effective bits of color information, and the other from L3Lab/L3P with 24 bits of color information. If we're (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
|