More specific KIO Error Strings
Aaron J. Seigo
aseigo at kde.org
Mon Mar 31 20:46:16 BST 2008
On Monday 31 March 2008, nf2 wrote:
> Aaron J. Seigo wrote:
> > assuming the errors are ones that matter to percolate up to the user
> > (there seem to be a few there), new error codes can be added to the
> > KIO::Error enum. there's lots of room remaining.
> > which error codes would you like to see added?
> Not sure yet - there are a lot that can be mapped, but not all of them...
ok ... well, let's start with the some you already know of.
> > NOT_MOUNTED, ALREADY_MOUNTED? those are specializations of
> > KIO::ERR_COULD_NOT_MOUNT or KIO::ERR_COULD_NOT_UNMOUNT, no? couldn't that
> > information be provided in the error message?
> That's actually a good example what i'm trying to fix. The predefined
> text for KIO::ERR_COULD_NOT_MOUNT is:
> "Could not mount device.\nThe reported error was:\n%1".
> This is quite limiting. What if it's a network or FUSE mount?
what text would you like to show the user? (please, specifics ... it'll make
the conversation go faster to solution if you provide complete proposals so i
don't have to keep asking for more details =))
> Of course it makes sense to have a set of standard messages, but picking
> the right one could still be done in the backend, and there might be
> more than one message per error code to choose from.
that's the point and purpose of "The reported error was:"
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Trolltech
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 194 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel