I went through similar issues with my music scheduling programs. In the end, it turned out to be easier for the users to solve this problem by communicating among themselves than to craft a technical solution. Technical solutions to this sort of problem tend to be messy (e.g. user shuts down computer without properly logging out, so log stays locked forever).
Rob On Thu, 22 Jun 2017, Patrick wrote:
Today someone was voice tracking and another person went into the log editor accessing the same log. I believe the way the log editor works is the entire log is loaded in and then written back when done, causing any voice tracks recorded during that time to be overwritten. If this is true, would it be a good idea to place some kind of lock on the database when someone is voice tracking that prevents the log editor from opening the same log, at least without some kind of warning message? Patrick
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
