Not signed in (Sign In)

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

Welcome Guest!
Want to take part in these discussions? If you have an account, sign in now.
If you don't have an account, apply for one now.
  1.  
    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?
    •  
      CommentAuthorMonsen
    • CommentTimeJan 2nd 2020
     
    You have spelled it incorrectly in your macro.
  2.  
    This is what happens when you're lysdexic. Thank you!
    •  
      CommentAuthorMonsen
    • CommentTimeJan 2nd 2020
     
    You're welcome. Enjoy your macro writing, and don't hesitate to post your final version here to show it off.
    • CommentAuthorLoopysue
    • CommentTimeJan 2nd 2020
     
    Oh dear! I must be even worse because I've read it several times and can't see the spelling mistake at all.
    • CommentAuthorJimP
    • CommentTimeJan 3rd 2020
     
    Posted By: LoopysueOh dear! I must be even worse because I've read it several times and can't see the spelling mistake at all.


    LWITDH is incorrect. It should be LWIDTH
    • CommentAuthortaustinoc
    • CommentTimeJan 3rd 2020
     
    Posted By: JimP
    Posted By: LoopysueOh dear! I must be even worse because I've read it several times and can't see the spelling mistake at all.


    LWITDH is incorrect. It should be LWIDTH


    Which is to say, the D and the T are transposed, for those who are as dense as I usually am.
    • CommentAuthorLoopysue
    • CommentTimeJan 3rd 2020
     
    Wow!

    Thank you! I really couldn't see that at all :)
    • CommentAuthorJimP
    • CommentTimeJan 4th 2020
     
    No problem. One of my relatives has dyslexia, in that the middle of words flip.
    • CommentAuthorLoopysue
    • CommentTimeJan 4th 2020
     
    I have quite a lot of trouble when everything is in upper case. I think that's why I tend to prefer clicking buttons to typing commands.
    •  
      CommentAuthorMonsen
    • CommentTimeJan 4th 2020
     
    Posted By: LoopysueI have quite a lot of trouble when everything is in upper case.
    CC3+ isn't case sensitive though, the upper case for commands is just a convention, but you can just as well type it in lower case if you prefer.
    • CommentAuthorLoopysue
    • CommentTimeJan 4th 2020
     
    I think I'm having one of those wonderful revelation moments :D

    Thank you!

    I need never fear the command line again.
  3.  
    As a programmer without Dyslexia, I can confirm that this happens ALL. THE. TIME.

    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!