I am a user like you and not one of the package maintainers. I am subscribed to this list to track the updates.
I tried to give my opinion on what could have been a possible cause of the problem.
Your response to Point 3 of mine is valid, clarity in displaying the error will only help more :)
-Punit
"A. Costa" <[EMAIL PROTECTED]> wrote:
On Wed, 8 Feb 2006 21:01:53 -0800 (PST)
Punit Rathodwrote:
> 1 - Try making a fresh new DVD project and then see if the same
> problem persists.
Thanks for the prompt reply and what is probably an accurate diagnosis.
A 2nd test might have to wait a bit -- it's an IDE drive that
was in a USB case at the time of my report. I've since moved it to an
IDE bay and cannot move it back immediately.
> 2 - Also if the problem persists, then it seems
> that K3B is not able to detect that its a DVD that you want to burn
> and keeps assuming that you want to burn a CD. 3 - Assuming the above
> point (2) is true _OR_ its a CD that you are trying to burn, then the
> error shown by K3B is valid. In the context of K3B trying to burn a
> CD and finding a DVD-R in the drive, the error shown is perfect. Its
> "waiting for disk", expecting a "CD-R(W) medium", while it has "DVD-R
> in drive". -Punit
Contradiction please -- even if it's perfectly correct that the
errors displayed were intentional, they'd certainly be bugs of
ambiguity. That is, if there's two ways to say something:
1) "Creosus, if you attack Greece you will destroy a great kingdom."
2) "Creosus, if you attack Greece you will destroy Lydia."
Method #1 is useful for oracles and sly folks, but bad for Creosus, King
of Lydia. While #2, substituting a proper noun, is best for user
friendly computer programs and plain folks.
Let's walk through taking a naive user's perspective.
The title bar says:
Waiting for disk
Given the usage you pointed out, it could mean three things:
1) There's no disk, so K3B is waiting for one.
2) There's no CD, so K3B is waiting.
3) There's no DVD, so K3b is waiting.
...and even more if we allow for all the various incompatible media
formats and drives. It never occured to me that "disk" in that context
was intended to mean a particular type of disk.
If K3B was expecting a different disk, the title bar ought to say:
Wrong disk type
...and follow with a complete explanation like:
The drive contains a 'foo' disk,
but your current K3B Project is set up for a 'bar' disk.
To continue remove the 'foo' disk and insert
the correct 'bar' disk.
...that way the user knows, and also knows that K3B knows:
1) There is a disk in the drive.
2) It's the wrong kind.
3) The kind needed is 'bar'.
4) How to fix it.
Any high level front-end for inconsistant hardware and software, like
K3B, needs more precise wording than simpler programs. The media can be
bad, or the hardware, the firmware may have bugs, or the drivers and
command line utils. All problems that might be wrongly blamed on K3B,
if a user becomes confused.
Hope this helps...
PS: Aside from that, K3B is swell; thanks for keeping it going!
Yahoo! Mail - Helps protect you from nasty viruses.
