--===============1066931101==
Content-Type: multipart/signed;
  boundary="nextPart1229069.N46gxyrte4";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1229069.N46gxyrte4
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

currently the entering of formulas, whose results are matrices, is a bit od=
d.=20
We try to mimic the Excel, Calc, Gnumeric behaviour *), i.e. you need to ma=
rk=20
the range the matrix values should be put in _before_  you begin to enter t=
he=20
formula. Then, you have to finish entering the formula by Ctrl-Alt-Return=20
instead of just Return. If the selected range is smaller or greater as the=
=20
resulting matrix, the elements are cut off or #REF! errors are put in,=20
respectively.

The reason for this behavior is, that you can store such a result in a sing=
le=20
cell or just in a specified (smaller) range and to prevent accidentally=20
overwriting of data (it'd not always be obvious, which range has been=20
overwritten).

I'd like to change this complicated matrix formula entering. My plan is to =
use=20
the necessary cell range, if just one cell is selected and you hit the=20
Alt-Ctrl-Return combination. If you just hit Return, the result is stored i=
n=20
the single cell (no change here). If more cells were selected before and yo=
u=20
use the key combination, the result uses this range, but not more than=20
necessary.

To prevent accidental overwritings, I'd like to set the selection to the=20
region, that has been altered. And eventually, if this is not enough, a=20
passive popup, that barks: "Wuff, wuff!" (the message string is open for=20
discussion ;-) ).

Another topic is the current implementation of setting the matrix elements:=
=20
The top left cell carries the resulting matrix as value. The other cells in=
=20
the selected range get an INDEX() formula refering to the corresponding=20
element in the top left cell.
I'd like to introduce a new (rectangular) storage instead, which stores the=
=20
occupied region - similar to the merging info. Altering any other than the=
=20
top left value/formula of such regions should be forbidden, while the=20
(conditional) styles, comments, validitations should be still allowed. The=
=20
INDEX() formulas will get replaced by the plain matrix elements.

Any objections or comments regarding this proposal?

Regards,
Stefan


*) Actually, I don't know, wether you need to define the range before enter=
ing=20
the formula in Excel or wether it does what I'm proposing here. :|

=2D-=20
Stefan Nikolaus
humba, humba, t=E4t=E4r=E4=E4, t=E4t=E4r=E4=E4, t=E4t=E4r=E4=E4=E4 ;-)

--nextPart1229069.N46gxyrte4
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBFzd4epfDn2DABIpcRAuGWAJwKq6XBM7VsFPHiZHx2wxWoWGGf/QCgm+lr
4ouRIHTj3mWIbq4NwYf+xQY=
=3l+f
-----END PGP SIGNATURE-----

--nextPart1229069.N46gxyrte4--

--===============1066931101==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

--===============1066931101==--