On Fri, 13 Jan 2012, Aaron Horn wrote:
> Our issue is that we are loosing a boat load of content, it seems that > this occurs when the log is open in more than one location... So the > log is being played out on RDAirPlay in Studio 1 but a user makes > changes to the log in Studio 2 on RDLogEdit - if the user in Studio 2 > saves all their work but then someone in another studio saves also, > their work is lost. Many years ago I had a similar problem at WCRB with a music scheduling program I wrote. In those days announcers scheduled their own music, and two or three of them would often be working on the same schedule. I solved the problem by writing each transaction into the database immediately, then repainting the screen with the current database content. Thus, if another user made a change in the meantime, it would be reflected in the new screen content. It wasn't perfect, but it was good enough. In terms of Rivendell, each user needs to sign out a log for a period of time: Joe gets Saturday from 2 to 3; Molly gets Saturday from 3 to 4; or else one can assign specific logs to specific individuals. Rob _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
