Development Blog

oh oh oh oh super secret special surprise. my guess is LINUX support.

Undo functionality is my absolute least favorite thing to program

We can testify.

-Every Leadwerks 2 user, ever.

This now seems like such a pleasantly short list though I know the documentation will be time consuming. Please don't forget simple examples. The good news here is that less is more, usually. Don't try to get clever or "advanced." Also, I noticed on the last two occasions I tried to help people that the wiki had better examples than the documentation page. For example the GetEntityAABB wiki has a clear picture illustration whereas the doc page doesn't. It works wonders to illustrate what the example is doing.

4 out of 79 classes are documented now!

I would usually recommend a good ebook to listen while coding since it kills the part of your brain that tries to think, but doing documentation is a good candidate for some angsty rock.

hophop! I like this I would definitely buy it, I think it will be my Christmas present to myself

Command pattern, for undo functionality. Needs a project to be designed that way from the outset. But if anyone's creating anything with multi-level undo, look up command patterns for inspiration.

You guys are making a really simple idea sound really fancy. A command pattern is just an integer id for the action, and maybe a couple extra parameters. Why does that even need a special comp. sci. term? It's a bad approach because you have to do special programming for each action the program can take.

While I agree that the "command" "pattern" (both in quotations intentionally) is ridiculous, the simple approach of saving every state of the program for each action is lazy (but that's not bad per se) and extremely memory consuming.

 

What I'd do is have a reverse action for each action, push the action to a stack, and pop the reverse on undo. Tadah.

Terms such as those used to described patterns are just handy for communicating. That's all they are, descriptions, not implementations. It's a surprisingly common misconception among developers (where I work anyway).

A per-entity undo would be also cool. Sometimes you made something wrong with one entity, but you want to keep the rest how it is.

While I agree that the "command" "pattern" (both in quotations intentionally) is ridiculous, the simple approach of saving every state of the program for each action is lazy (but that's not bad per se) and extremely memory consuming.

 

What I'd do is have a reverse action for each action, push the action to a stack, and pop the reverse on undo. Tadah.

You don't save it for the entire program, only for the relevant objects.