Hi Thorsten,
for me it is not so importend why the app needs more memory as aviable
as that to less aviable memory can be a reason to crash the app. I think
not to crash on memory issues is an absolute basic for any app.
For me it isn't important if it is a defect or an enhancement. As I
know the development has to integrate a handling for actions which needs
more (too much) system memory. Therefore this issue is flagged as
enhancement.
It is the question of the aspect. For the app it is a defect, for the
developer to fix it maybe an enhancement is nessesary.
To change this issue to a defect will not fix this issue
earlier.
OK. I mixed up priority with issue type.
The action Ctrl+A, CTRL+C, CTRL+V isn't a real use case. We do not get
so much crash reports for it in the past years. So it wasn't decided
to fix it as a show stopper issue with a high priority.
(Clumsy) users can have the idea to fill all cells with the same
content, maybe only to get the same background color. Not every user
knows, that Ctrl+A means thousends of cells, because the user don't see
the end of the sheet. He has to scroll again and again. But anyway, the
user should can do what he want (importing a 4GB JPG) the app has not to
crash.
who would wish more quality (stability) instead of quantity (of new
features).
Do you have more issues with general instability? Currently the crash
reporter tooling doesn't show any bigger problems (often reported on
OOo 3.0 until now). A lot of issues were fixed before OOo 3.0 is/will
be released and also some more crashes are addressed for OOo3.0.1. So
as I could see, the general stability is high for general work.
OO 3.0 RC2 crashed 2 times in last 2 weeks working with calc. Once
without any user action. But no idea why, so I can't write an issue.
But I mean not only stability, also functions that don't work correct
for many years would not fixed, instead there comes new features.
I'm very happy with OO on Mac without X11, but I would rather work 6
month longer with NeoOffice for get then a OO 2.5 with less errors.
Kai
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
