Version: (using KDE KDE 3.5.7)
Installed from: Mandriva RPMs
When I insert a 4.7 GB (=really 4.4 GB) DVDR/DVDRW, and start a New Data DVD project, I see at the bottom the limit of 4.4GB.
When I add files I expect them to fill the 4.4 and see a warning that the size is exceeded.
But suddenly when the selected files for burning start to exceed a total of 4.4 GB, k3b shows at the bottom a new limit of 8.0 GB (as in dual layer media), and the indicator of total bytes selected retuns to about halfway full, and the total in the lower right hand corner shows 3.2 GB (or thereabouts) still available, and I can happily exceed the limit of the inserted disk.
IMHO k3b should stick to the previous limit of 4.4GB when it has already.
At the same type the "burn" subscreen detects the media inserted if you look before the 4.4 GB limit is reached, but when the size exceeds 4.4 GB. the burn subwindow shows as Burn Medium "Please insert an empty or appendable Double Layer DVD+_R medium.
Using k3b under GNOME 2.19, from packages:
in Mandriva Cooker.
s/has already/has already detected the medium.
This is a user interface problem:
insert single-sided DVD
select a 4.6gig file to burn in project
space-filled colored bar still shows green
hit burn button
confusing button text says insert dual-layer disk, even though it knows the drive has a single-layer disk in it.
You may say, "well its doing the right thing" and I agree. But from a user's POV the colored bar is a strong signal ( and quite helpful, most of the time ) and the italics in a button bar ( non-standard interface there) are a weak signal, especially as the text is hard to read, wordy, and the difference between single and dual layered does not pop out. Further I don't have a dual-layer capable drive, so it isn't an appropriate message.
So, what should you do? The burn-button error if you have no disk at all inserted in the drive is perfect, so copy that: Change the color bar to accurately turn red when there isn't enough space; give the burn button an error pop-up that says " not enough space on disk" or similar.
I tries to make K3b behave "intelligent" here. But I agree that in this case it is confusing. I will fix that.
SVN commit 817110 by trueg:
Allow a 10% margin when filling up the medium. This way, an inserted empty medium
can be fine-tuned. However, if a bigger medium is inserted, it will always be preferred.
(I will not backport this to 1.0.x as it uses some new stuff only available in trunk)
M +28 -18 k3bfillstatusdisplay.cpp
WebSVN link: http://websvn.kde.org/?view=rev&revision=817110