Rishi Khan wrote: > The problem with this error box from a GUI perspective is that > there is WAY too much information. For a technical person, this is > fine because he can read all of this and it somewhat makes sense. > However, someone not familiar with the XML -> FO -> PDF internals > will have almost no understanding of the bottom box. "Permission > denied" is buried at the end of the 6th line. How is a lay user to > know THAT is the problem and the problem isn't "Cannot copy" or > "Command execution failed" (well, these are higher level problems. > > Suggestion 1: Put the error reason up front like this: > Error: Permission Denied > Cannot copy ... to ... > > Suggestion 2: Have the "Details" box as an optional drop down with a > little ">" that you can click on to turn to "V" (like OSX when > copying many files). Or have a "Details" button like Windows GPF's. > This way the technical person can see the data, but the non-technical > person doesn't get inundated. > > The second problem is that although "permission denied" tells the > user the problem, but it doesn't tell the user how to SOLVE the > problem. I would add, in the case of "Permission Denied", "Check if > this file isn't open in another application". (Permission denied can > happen for other reasons, but on a windows machine, this is the main > reason you can't write to a file). The other option is to have a > "Help" button. When the user clicks on that, it brings up a box that > suggests how to fix the problem. >
Thank you for your suggestions. We'll try to improve this.
