On 10/31/06, Mathias Bauer <[EMAIL PROTECTED]> wrote:
This was an "enhancement", not a bugfix. If you read the issue you can see that it covered quite a lot of considerations. I don't know enough
There are 36 reported issues and over 120 votes for this problem. Users have hidden a number of cells and perform an action on the visible ones. Based on their experience the expectation is that the hidden cells stay unchanged. Instead their spreadsheet is botched. What if they save before they realize the damage and don't have a backup? Whatever we call the issue, it's pretty clear it hurts users. We all want to improve quality. The user is the one who judges quality. -Not- QA and certainly not us developers. Maybe this specification discussion is really about more fundamental priorities. This issue has been open for five years. Over those five years, how has the specification process improved the user experience? Are we writing software for the users or us developers? :-) Kai On 10/31/06, Jim Watson <[EMAIL PROTECTED]> wrote:
You have highlighted exactly the issue in this case - users see that this is clearly a bug or a defect, but the developer says the behaviour is intended.
-- Kai Backman, Software Engineer, [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
