[Libburn] Thoughts about writting writting progress

[Derek Foreman]

On Sat, 6 Dec 2003, Tiago Cogumbreiro wrote:

> Hi again,
> I was trying to develop the writting progress for libburn, while
> browsing throughout each part of the write_disc code i encountered a
> minor sitback, how would i describe the progress of writting when we are
> writting the lead-out and lead-in, could the user have access to
> detailed status of the progress?

struct libburn_progress sucks pretty bad, eh? :)

> On a lesser imporant issue, maybe users would like to know when they the
> drive is performing lead-in/out so maybe a more detailed progress could
> be implemented with a status for describing the device work.

Yeah, we should definately provide that information.


leadin and leadout (for raw modes) are just seperate "tracks", and we do
know their sector lengths and extents (first leadin varies in length from
disc to disc)

We could just add an enum to the progress struct... lead_in,
user_data_area, lead_out...  (session_close?  erase?)