[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#564914: openoffice.org-base: cannot save relationship diagram changes



On Tue, 12 Jan 2010 19:02:26 +0100,
Rene Engelhard <rene@debian.org> wrote:

[...]

> Brilliant.  How should we then find out which differences cause it?
> Why can't people just report bugs when it happens? I mean, how many
> years went by since 2.0.0 which first introduced Base? (Hell, 2 Debian
> stable releases)

Many reasons come to mind, but in my experience: the user is expected to
study the bug in greatest detail, often beyond his(her) understanding of
the program, almost be able to fix the bug him(her)self and send a patch
before reporting it, or else the developer answers with an angry or
insulting response, as if the report was meant to be trash to annoy the
developer.  So many people probably wait to become nearly experts in the
program before they can communicate a bug report.

I understand your frustration, but with the distinction between
user/developer getting blurred as users become more and more savvy with
programming and software development, there needs to be more tolerance
and guidance to encourage users to report what they think is not working
as expected.  Sure, there are lazy users that don't do their homework,
but many intelligent and inquisitive users get turned off by the
response their reports get.


> Sure recipe to get a bug lingering around for infinity with no/no
> visible progress.

>> user's dba.openoffice.org mailing list (subject: saving relationship
>> diagram across sessions), where we found that the problem only exists
>> in the Debian package.

>> Briefly, any work done on the visual arrangement of the tables, size,
>> position, etc. is lost after closing the relation designer window.

> Please try OOo 3.2 rc1 (well, better rc2 but that's only building
> right now), too. Not much hope it'll work there but you never know and
> I concenreate on 3.2 right now anyway.

I'll wait for the release, I can live without this feature for now.


-- 
Seb



Reply to: