[Cdw-devel] Odp: Bugs prior to 0.5 release

[<cdw...@li...>]

Dnia 12-07-2010 o godz. 0:11 cdw...@li... napisał(a):
> 1) My current size of media stated at the bottom does not update to the CD
> media in the drive after pressing 'R'.  Although 'R' updates the far
> bottom
> left info window, the one next to it still remains at the size of a DVD
> media
> and never updates.
> 
> This window is "Approximate size of selected files:"
> 0.0/8152 MB in 0 items, 8152 MB free
> 
> The configuration:
> Maximal ISO volume size = Generic DVD (4.7 GB)
> Custom ISO Size = 8152
> 
> Or, should there be an "Auto (size)" option within the menu?
> "Maximal" is kind of vague term isn't it?  Do you mean, "Maximum ISO
> volume
> size"?

You would see current size of media updated in bottom right area of UI 
only if "Auto" option was selected in Configuration window -> Log and 
other -> Maximal ISO volume size. "Auto" option is in the code, but it 
is disabled by default. Even if it was enabled, it wouldn't work, 
because currently there is no code (yet) that would check disc type, 
look up disc size, and update information in UI. But the fact that there 
is "Auto" in the code hints that there are plans to make it work in one 
of future releases :)

So currently you can only see maximum ISO volume size which was 
configured in configuration window, but the value isn't automatically 
updated.


> 2) When pressing the "Delete" key within the Configuration Menus, it
> goes to
> other fields.  At first this scared me because I thought it was erasing
> fields,
> but then realized this is more of a smart feature.

This doesn't happen here. Delete key only removes content of fields, so 
it does the opposite... Maybe it is a matter of ncurses version? 
Weird... But you present it as something that isn't a bug?

> 3) Within the info window during a write session, shows the
> FIFO fill rate, ETA, % Megabytes, Track status remains as #1.  But
> there's no
> "Current Write Speed" ie. 48x's.  From my experience, the writing device
> never
> remains at a constant write speed and will fluctuate from slow writing
> and fast
> writing (probably depending on the outer and inner tracks of the media).
> 
> I'm guessing the current write speed is negotiated within other
> applications by
> "guessing" or using an algorithm to approximate the write speed from
> calculating from the Estimated Time of Accomplishment (ETA).
Tools used by cdw to do the burning display current value of writing 
speed. It shouldn't be hard to capture the value and display it in 
progress window. I'm adding this to my TODO list.


> Most of these are probably considered features.  I'm guessing #1 above is
> probably the only item needing any attention.
I'm going to address #1 and #3 in some way in 0.5.1 or in 0.6.0. Thank 
you for reporting these issues :)

Kind regards,
Kamil