Feature Request... Time and Date on Undo List.

This morning I came into the theater to unscrew a problem that occurred while I was away. Our console is in a location that is NOT secure, and never will be because the powers that be didn't see this as a priority when they built the theater. While I have taken steps to keep outsiders out of the console (Magic Sheet with cues that use only touch 4 Paradigm presets and standard fixtures.)

Occasionally I will come in to find that someone has made their way into the system (like this morning). Most of the time I can figure out the issue fairly quickly, other times (like this morning) it was a little more involved.

When I talk to my management and or security, I have no idea when this actually happened because undo doesn't have any sort of time record (that I can find). 

Aside from terrorists breaking into the board as listed above, I could see a time listing being useful when programming shows too when one might need to back out of a 'really great idea' one had.

Lastly, is it a memory issue that make it that the undo is wiped out when we save? Some times you save not realizing that you built a gremlin into the works. When you go to undo and realize that the history is gone... My primary job here is producer / video editor. I save and save often. I kind of have that same mentality when I program my ION. I am ctrl updating all the time. 

Parents
  • +1 on the removing the undo wipe.  I have never understood why this is considered ok.  It makes it so I do not want to save the file.  If it is a memory issue, cap the number of undos and make it a FIFO dump of undo data.  Maybe only the last 100 undos are available.

    Also, persisting undo data in a save would be helpful as well.  When I was still a software developer, I worked on a product where every change was saved to the file.  This allowed us to be able to undo all the way back to the first thing place in the file.  It was very handy at times.

    Steve

Reply
  • +1 on the removing the undo wipe.  I have never understood why this is considered ok.  It makes it so I do not want to save the file.  If it is a memory issue, cap the number of undos and make it a FIFO dump of undo data.  Maybe only the last 100 undos are available.

    Also, persisting undo data in a save would be helpful as well.  When I was still a software developer, I worked on a product where every change was saved to the file.  This allowed us to be able to undo all the way back to the first thing place in the file.  It was very handy at times.

    Steve

Children
Related