40d Talk:Macro design

Updates to my work in progress

Wow thats a lot of updates to a page I was building, that had no links to, with no discussion page entires.., and I had to go to bed.

I like most of what has been done except for the following

• Changing a "Step to Far" to Off-by-one Errors
  • This is the exact oppiste of the common off-by-one error of arrays and for loops, while it is an error of just 1, this is missleading I think. Also "off-by-one" is really just a CS term.
• The Change (labled " Off-by-one") to make "current" into "initial"
  • This is wrong, as it can occure anywhere in the script not on just the inital movement.
• In Fast Movement
  • The Concept of the cursor jumping was removed and repalced with " the cursor moves ten squares instead of one". The old Term of "Jumping" gets across the idea of skipping/is-faster than ten squares of movement
• What was wrong with "(nearly half)"
• "Troubleshooting"
  • this is a "design" page, not a how to code page. thge Orginal "Problems to avoid" term is more toward the concept of "read this section first and have it in your head while coding". Not to figure out what when wrong after the fact. Hopefully if they design it right the first time, it will work perfectly with no debugging.
• I think the Second Edge Collion paragraph read a lot better the way it was.
• "applies to a comand" isn't correct.
  • Original didn't have that issue

Over all I'm glad for the help (espescally in the conversion to a 3rd person), I just didn't expect it until the page was activly linked some where. I'll make the above changes if I don't see a justifaction not-to comments. Larek 22:37, 12 November 2009 (UTC)

Heh, yeah, every edit you make shows up in Special:RecentChanges, and there are several people who watch that page. In general, as soon as you click save, people will see your change and look at it, and if it's in the main namespace, they will probably make changes, too. If you want to keep exclusive ownership over something, you can make a user page like User:Larek/Macro design. We'll still see it, but it's considered bad form to edit someone else's personal pages.

• Why do you say it's the opposite of an off by one error? The programming term is used to describe confusion in loop conditions when iterating over an array. It seems quite analogous to me; maybe you can elaborate.
• Re: current vs initial, my thought was that it's the starting point for a given series of movement commands. Personally I think that's clear from the context, but I'm open to other ideas.
• Would you be happy with "the cursor jumps ten squares instead of one"? I wouldn't have a problem with that.
• I thought "(nearly half)" would be obvious to anyone reading the numbers. In general, if text is unnecessary, then removing it means you get to the next necessary idea faster.
• You say it's not about debugging, but the first clause was already "When your script doesn't run as planned" before I edited. That sounds like debugging to me. Personally I don't think debugging is inappropriate on a design page; people following along are likely to need debugging strategies unless they somehow do everything perfectly the first time.
• I thought the edge collision section was missing some key concepts, specifically the possible disparity between changed-area and traversed-area which is the root cause of the problem in the first place. What advantages do you see in its original phrasing?
• Admittedly, "applies to" is metaphorical. I was trying to express that now instead of (normal jump)(backpedal jump) you have (backpedal jump)(normal jump), since the "backward" movement takes place earlier. I'll try to think of a better phrasing, but please feel free to come up with something yourself.

But welcome to the wiki, and thank you for contributing!

--HebaruSan 00:05, 13 November 2009 (UTC)