Changing line width in a macro, in CC3+?
I'm working on a customized version of the very excellent STAIR.MAC, adding things to help me visualize which side opens on this floor vs the next, and so forth.
One thing I'm trying to do is draw lines around THREE sides of the background rectangle. Since I want it on only three, I can't use a HOLLOW fill style POLY and overstroke the bottom poly. That's fine, but I need a specific line width different from that used for the other parts of the macro.
I have older tutorials that use LWIDTH to change the line width, and I can type it in manually and change it, but when I use LWIDTH in a macro it doesn't work - I get told "Campaign Cartographer 3 does not understand the command: LWIDTH"
This is the section of code I'm working with:
SHEET STAIR_BORDER
FSTYLE solid
COLOR border
GV vLineWidth 3/8
LWITDH vLineWidth
LINE P1 P4 P3 P2;
GETSETTINGS
I don't have any extra blank lines in the middle of my macro, and I don't have extra whitespace at the end of a line, or accidental double-spaces. Can anyone spot what I've done wrong?
One thing I'm trying to do is draw lines around THREE sides of the background rectangle. Since I want it on only three, I can't use a HOLLOW fill style POLY and overstroke the bottom poly. That's fine, but I need a specific line width different from that used for the other parts of the macro.
I have older tutorials that use LWIDTH to change the line width, and I can type it in manually and change it, but when I use LWIDTH in a macro it doesn't work - I get told "Campaign Cartographer 3 does not understand the command: LWIDTH"
This is the section of code I'm working with:
SHEET STAIR_BORDER
FSTYLE solid
COLOR border
GV vLineWidth 3/8
LWITDH vLineWidth
LINE P1 P4 P3 P2;
GETSETTINGS
I don't have any extra blank lines in the middle of my macro, and I don't have extra whitespace at the end of a line, or accidental double-spaces. Can anyone spot what I've done wrong?
Comments
Thank you! I really couldn't see that at all
Thank you!
I need never fear the command line again.
Best explanation I’ve ever seen is that we expect our code to be right, and thus we see it right even when it’s wrong.
Doesn’t make it any less frustrating!
Awesome macro!