 | | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes —Kevin L. Clague
|
| | | (...) Hi Mike, I've added it to the list. Minimally I could see it affecting construction image size, and possibly some quality and anti-aliasing controls, but I'm not sure it makes sense to affect rendering of parts for part list images and BOMs, (...) (22 years ago, 2-Apr-03, to lugnet.cad.dev)
|
| | | |
| | | | | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes —Mike Walsh
|
| | | | "Kevin L. Clague" <kevin_clague@yahoo.com> wrote in message news:HCqIBJ.12tn@lugnet.com... (...) [ ... snipped ... ] (...) current (...) build (...) construction (...) not (...) BOMs, (...) For this type of LPub run I am not concerned about image (...) (22 years ago, 2-Apr-03, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes —Jake McKee
|
| | | | (...) I think this is a great idea, and can provide another recent example of why this would be wonderful to have. Using LPub, I recently ran a large model with about 6 submodels. I kicked it off before I went to bed, and it had completed by mid-day (...) (22 years ago, 3-Apr-03, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes —Kevin L. Clague
|
| | | | (...) My solution to the above is to give you explicit control over construction image render window size and PLI render window size. You can set these sizes small for test runs. Is this acceptable? It will be available in the next LPub release. (...) (20 years ago, 4-Oct-04, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: LPub and Lsynth page for tracking enhancement requests and bug fixes —Mike Walsh
|
| | | | "Kevin L. Clague" <kevin_clague@yahoo.com> wrote in message news:I52p4z.1xwI@lugnet.com... [ ... snipped ... ] (...) construction (...) sizes (...) LPub (...) I believe that will do. Thanks, Mike (20 years ago, 7-Oct-04, to lugnet.cad.dev)
|
| | | | |
