 | | Re: LPub missing pages in the layout
|
|
(...) It was missing trailing STEPs that was the problem. I'll see if I can recreate it tonight. (19 years ago, 17-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub missing pages in the layout
|
|
(...) Dean, I tried to recreate this, by adding trailing steps to all my models/submodels in pedmatic, and it didn't cause any problems. If you can recreate this it would be a great help to me. Kevin (19 years ago, 17-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub problems
|
|
--SNIP-- Thanks for all that. I noticed something else but need to test it more (and probably look through .cad in depth again) but when I use 0 LPUB PAGE PLI NO at the start of my file, no layout images get generated at all. I may be misusing it or (...) (19 years ago, 17-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub problems
|
|
(...) This has been changed to ../Images for nonlayout web pages and ../Layout for pages generated through the layout process. (...) This has been fixed to SEPARATOR. (...) This has been fixed. (...) I've got to chase down the "trailing step messes (...) (19 years ago, 17-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub bug: Page Number Font
|
|
(...) This bug has been fixed and will be available in the next release. Kevin (19 years ago, 17-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub building instruction progress
|
|
(...) Are you drawing in the same *direction*? LineTo(x,y) draws a line upto >>but not including<< <x,y>. This is a thing of the Windows API that's always been there (since Win 1.0). The same goes for rectangles, I think. (I think the LPub results (...) (19 years ago, 16-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub building instruction progress
|
|
(...) Very cool, Jaco! (...) I'm not quite sure why Borland's graphics routine does this. I use the exact same points to draw the triangles and the lines. (...) Yes, this is a bug, and it is in the area that I has just been heavily rewritten. If you (...) (19 years ago, 16-Jun-05, to lugnet.cad)
|
| |
| | LPub building instruction progress
|
|
Kevin (and others interested), Take a look at this: (URL) you can imagine by now, I am quite happy about this result :-) Though I have two points I like to do better: 1. There is a "halo" effect arount one of the pointers of the callout in step 8 2. (...) (19 years ago, 16-Jun-05, to lugnet.cad)
|
| |
| | Re: Callout a single part
|
|
(...) You are so right! How can I be so ignorant? (...) Thanks so much again! Jaco (without a "k" :-) (19 years ago, 16-Jun-05, to lugnet.cad)
|
| |
| | Re: Callout a single part
|
|
(...) Jacko, I originally developed mine in MPD file, but presented it as non-mpd file. The file you presented above is not in valid MPD file format. The first line needs to be: 0 FILE single-callout.ldr The file with this minor correction works (...) (19 years ago, 16-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub and margins, margins, margins......
|
|
(...) Of course! I should have thought better... (...) ...but using a parameter in the LPub interface would leave the LDraw code resolution independant. Philo (19 years ago, 16-Jun-05, to lugnet.cad)
|
| |
| | Re: Callout a single part [DAT]
|
|
(...) Right. This indeed works. However it does not seem to work in an MPD file. Render this: 0 New Model 0 Name: single-callout.ldr 0 Author: MLCad 0 Unofficial Model 0 BUFEXCHG A STORE 0 LPUB CALLOUT BEGIN 1 0 0 0 0 1 0 0 0 1 0 0 0 1 (...) (19 years ago, 16-Jun-05, to lugnet.cad)
|
| |
| | Re: Callout a single part [DAT]
|
|
(...) This worked very well. I have this for my sub-model: 0 New Model 0 Name: single-arrows.ldr 0 Author: MLCad 0 Unofficial Model 1 8 0 8 0 0 0 -1 0 1 0 1 0 0 3023.DAT 1 8 0 -72 0 0 0 -1 0 1 0 1 0 0 3023.DAT 0 MLCAD ARROW 8 0 -16 0 0 0.707107 (...) (19 years ago, 16-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub and margins, margins, margins......
|
|
(...) Well, I really like the idea of things relative to page size. I've been trying to figure out how to make this work. But, don't we achieve the same thing with DPI/DPI and absolute size? (...) Hey, I make up new meta commands all the time! (...) (...) (19 years ago, 15-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub problems
|
|
(...) <snip> (...) I have made this change per Don's recommendation. (...) Kevin (19 years ago, 15-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub problems
|
|
(...) I don't think this is the best way either. The best fix is to just get rid of the C:\ and go with a good relative path. I tested this a while back and found that entering "../Images" in the lpub URL box works on both IE and Mozilla. My image (...) (19 years ago, 15-Jun-05, to lugnet.cad)
|
| |
| | Re: Callout a single part
|
|
(...) It just creates an alternate solution for something that I have already provided. (...) I'm wondering if this will work in your higher level model: 0 BUFFEXCHG A STORE 0 LPUB CALLOUT BEGIN 1 0 0 0 0 1 0 0 0 1 0 0 0 1 sub8callout.ldr 0 LPUB (...) (19 years ago, 15-Jun-05, to lugnet.cad)
|
| |
| | Re: Callout a single part
|
|
(...) Sorry, I meant: By placing LPUB SUBMODEL_STEP BEGIN IGN prior to the 0 STEP command in a submodel, the following steps will be ignored until the next LPUB SUBMODEL_STEP END meta command and not show in the callout. (19 years ago, 15-Jun-05, to lugnet.cad)
|
| |
| | Re: Callout a single part [DAT]
|
|
(...) I agree that it does, but I think it is a bit too circuitous. I suppose this is too difficult to implement in LPub For now then making a submodel for each callout with only one part and no step in it, doing it like this makes me (once again) (...) (19 years ago, 15-Jun-05, to lugnet.cad)
|
| |
| | Re: LPub and margins, margins, margins......
|
|
(...) Hello Kevin, I would prefer having all dimensions relative to page size. This way you can render fast, small rendering for debug and webpages, and with the same "source code" create high-res renderings for printing (ideally even CSI/PLI images (...) (19 years ago, 15-Jun-05, to lugnet.cad)
|
