--8GpibOaaTibBMecb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 23, 2001 at 08:17:29PM +1100, Clarence Dang wrote: > On Tue, 18 Dec 2001 22:27, David Faure wrote: > > On Tuesday 18 December 2001 12:18, Clarence Dang wrote: > > > E.g. For the Header, I can easily specify the 'left", "right" and "to= p" > > > attributes but how does the import filter know what the "bottom" will= be > > > (maybe the user had a long header)? Since the attribute is "#REQUIRE= D", > > > I don't know what to do :( > > > > Did you try setting a random value to it ? E.g. make the header 10 pixe= ls > > high, and with a policy of "auto-resize", and KWord will recalculate the > > header size when opening the document. > > > > > The "bottom" of the Header would obviously affect the "top" of "Text > > > Frameset 1", just as the "top" of the Footer would obviously affect t= he > > > "bottom" of "Text Frameset 1". > > > > All of this is calculated together by KWord. I don't think you need to = do > > it. >=20 > Thanks for the info. It worked very nicely and I especially like the > "automagical" resizing :) >=20 > However, I think there may be a little bug with KWord (I'm basing my > comments > on the 1.1 code at the moment because I can't use the CVS properly until > January because of a - currently - limited internet connection so I may be > wrong about this): >=20 > It seems that if I depend on the auto-resize feature, "Text Frameset 1" > _has_ > to be the first frameset in the file else KWord renders it incorrectly > (header > is hidden behind Text Frameset 1) and seems to cause flicker (see > attachment). > Moving "Text Frameset 1" back up to the top of the XML solves the problem. > But shouldn't the ordering of framesets not matter? >=20 You are right that the first frameset always is the main frameset (when in = WP mode). This never posed a problem since KWord creates the framesets most of= the time; and the filter writers never said anything about this either. Hmm. Maybe I should order the framesets so headers etc are positioned later= =20 then the main text frameset.. Don't know if that is what is needed though.. --=20 Thomas Zander zander@earthling.n= et The only thing worse than failure is the fear of trying something new --8GpibOaaTibBMecb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8JeSxCojCW6H2z/QRAmR+AJ9fNLzSLftFdxFfy5kC5EorpOdQVQCdEoGf u//E3+bf8Wpj2ujwc+ZypiY= =m1f8 -----END PGP SIGNATURE----- --8GpibOaaTibBMecb-- _______________________________________________ koffice-devel mailing list koffice-devel@mail.kde.org http://mail.kde.org/mailman/listinfo/koffice-devel