From: Manuel Clos <llanero@ja...> - 2001-09-24 19:56:08
... and also the problem with copying a CD with a single device.
My proposal is to add funcs to the GCDMaster class. We need RecordDao
and DuplicateDao, because are the only cases where extra high level
control is required. Since the dialogs are per Device and are
independent from the projects, there is no problem with the gcdmaster
object managing them.
So, the Audio Project requests to burn 5 copies of a Project. Instead of
calling CdDevice->RecordDao we will call gcdmaster->RecorDao that will
take care of calling CdDevice->RecordDao multiple times and also
requesting a new CD to be inserted.
For the duplication case, gcdmaster will start a CdDevice->ExtractDao
with a temporary name (we need a global temp dir in preferences!), and
after that it will start a CdDevice->RecordDao after requesting a new CD
to be inserted.
We should warn the user if multiple copies and on the fly are requested,
since only makes sense when you run out of space, gcdmaster should also
handle this to launch a Extract + many Records or always launch a
We can intercept the status signal in gcdmaster to know when a process
finished, or let the Progress Dialog inform gcdmaster.
We will have a queue of pending operations. Also we will have a list of
current operations, since it was already needed, because nowadays
gcdmaster will exit even if there is some recording going on!
If no one has objections I will implement it in the next days.
Any comments wellcomed.
* Si no puedes hacerlo bien, hazlo bonito (Bill Gates)
* If you can't do it well, do it nice (Bill Gates)