--===============0764625932== Content-Type: multipart/signed; boundary="nextPart71449331.D78rN2exq5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart71449331.D78rN2exq5 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 27 June 2008 16:51:49 Thomas Zander wrote: > On Friday 27. June 2008 11:48:27 Stefan Nikolaus wrote: > > Hmm, you speak of making each table page derive from KoTextAnchor? This > > would result in a set of anchors and the user becomes able to insert te= xt > > between the table pages. This should be avoided. Or did I missed an > > important fact? > > You need one instance of the anchor and one instance of a table shape for > each page, yes. Otherwise it won't work (things like clicking and > repainting of dirty areas need a shape). =2E.. and the anchor to get the information about the text shape we are in,= I=20 see. The text shape is a KoShapeContainer, but it isn't, because of=20 representing a set of pages, is it? 'Just' because you can insert other sha= pes=20 and anchor them? The page (or frame) creation/deletion is managed by KWord? I want to use the table shape as another view mode in KSpread later. Just t= o=20 mention it; that does not prevent using kotext, but relying on KWord's=20 internals. :| > I'm afraid that indeed the user could insert a character in between, I'm > not sure how to fix that. This is indeed one of the reasons that I want = to > have tables that are part of the text instead of drawn on top of the text= =2E=20 > i.e. use QTextTable. > > But I don't think its a showstopper that a user can insert something in > between, do you? Well, it's a bit odd. Even more, if we support breaking the table inside a = =20 row, i.e. the row's cell contents are painted until the page edge is reache= d=20 and continued on the other page. But also with breaking at cell edges, it c= an=20 be quite confusing. And what happens on laying out the table pages on posit= ion=20 changes? I guess, any inserted text is moved behind the table. =2D-=20 Stefan Nikolaus --nextPart71449331.D78rN2exq5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkhlEM0ACgkQpfDn2DABIpfoDwCfblYXkp+OjQUjEFw4k0rMvZ/N GjAAoL2B0P1Z6UamqSqPlPvIHxXnNUsS =fDNh -----END PGP SIGNATURE----- --nextPart71449331.D78rN2exq5-- --===============0764625932== 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 --===============0764625932==--