[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    kspread error reporting
From:       John Dailey <dailey () vt ! edu>
Date:       2002-05-19 21:58:42
[Download RAW message or body]

While we're thinking about usability, I've commited a framework for better 
error reporting in KSpread cells.  Instead of having a generic 'error' 
condition, we can specify exactly what the error was.  Errors I've 
implemented so far are:

Parse Error
Couldn't calculate a dependancy
Circular dependancies

For now they all still give the '####' output, but I think that ought to 
change.  The question is what we should output for these, and what other 
specific errors should we capture?

-John
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]