 | | Re: Suggestion: New column for hidden
|
|
(...) I think that sounds like a great idea, the hidden ones will be a lot easier to spot when scrolling if grey (and finding the RIGHT piece to unhide). -NB (20 years ago, 30-Sep-04, to lugnet.cad.mlcad)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
"Nico Kaiser" <nico@siriux.net> wrote in message (...) Are you 100% sure about this? Usually the stair effect is caused by a lack of anti aliasing. Rendering the image at a huge resolution then doing a resize with proper resampling is more or less (...) (20 years ago, 30-Sep-04, to lugnet.cad.ray)
|
| |
| | Re: Radiosity example (F1 Ferrari) once again
|
|
Am Sonntag, den 26.09.2004, 10:46 +0000 schrieb Jan Folkersma: (...) Well, I don't have a problem with "mixed" models with LGEO elements and standard parts. The big advantage of LGEO is, that the edges are rounded a bit, so you don't need the gap (...) (20 years ago, 30-Sep-04, to lugnet.cad.ray)
|
| |
| | Suggestion: New column for hidden
|
|
Hi Michael, It is occasionally useful to be able to see the description of a part when it is hidden. I would like to suggest a new column, maybe to the left of "type", that has an icon depicting whether or not the line is hidden. Maybe a little eye (...) (20 years ago, 30-Sep-04, to lugnet.cad.mlcad)
|
| |
| | Re: Wanted DAT-elements from set 7044
|
|
(...) (URL) is an early release, there is still quite a bit of file clean-up to do yet. After I split the quads that make up the sloping sides, the part did not look near as nice in L3Lab or in LDview. Some of the extra time required was due to JAVA (...) (20 years ago, 30-Sep-04, to lugnet.cad)
|
