Undo - include layout or event sheet name

Reviewed guidelines

[X] I have read and understand the suggestion guidelines

Checked for duplicate suggestions

[X] I checked for existing similar suggestions

Summary

Currently, when using the undo function, it tells you what was undone but not what layout or event sheet it occurred on. As projects start to get much larger, this can become an issue if working across multiple tabs at once. Occasionally, devs will want to undo multiple actions in one go and may not know how far back they should go. Without a history bar to refer to, it can be quite challenging if trying to undo a sequence of actions like in this scenario.

Possible workarounds or alternatives

Not that I've discovered. I've discussed this with other devs on the Discord and they've mentioned similar issues with no in-built solution.

Proposed solution

Something that would make life easier would be to include the event sheet or layout name as part of the undo dialogue prompt. For example:

This could be expanded on further to include event sheet line IDs if desired.

Alternatively, a history bar (akin to how Adobe Photoshop logs events) would be an even better solution, though perhaps more difficult to implement than the first suggestion.

Why is this idea important?

Once a project reaches a certain size, there are issues that arise that may not be noticeable to a small project. I believe the undo function is one of these issues. In my last game, it was not uncommon for me to work across half a dozen or more tabs at any single moment, and stepping back even a couple of times with the undo function could result in some pretty big headaches if I was looking to reverse a series of actions. Having at least a bit of extra information in those dialogue popups would go a long way in helping to lower the stress that comes about when working on large projects.

Additional remarks

My last project had over a 100 event sheets and layouts combined, with something like 15,000 events. Undoing multiple sequences could be a real nightmare if I wasn't paying close attention or stepped away from the PC for a bit. As I start a new project and reflect on my previous one, I believe this is one of those things that would certainly help to improve the quality of life in C3 moving forward. Thanks.

Scirra / Construct-feature-requests