Re: commit: Make xft print properly (I think).

From: Rui Miguel Seabra (rms@1407.org)
Date: Sat Nov 09 2002 - 19:16:21 EST

Next message: Dom Lachowicz: "Commit: more XFT font work"

Previous message: Rui Miguel Seabra: "Re: commit: Make xft print properly (I think)."
In reply to: Rui Miguel Seabra: "Re: commit: Make xft print properly (I think)."
Next in thread: Martin Sevior: "Re: commit: Make xft print properly (I think)."
Reply: Martin Sevior: "Re: commit: Make xft print properly (I think)."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

On Sun, Nov 10, 2002 at 12:10:14AM +0000, Rui Miguel Seabra wrote:
> Date: Sun, 10 Nov 2002 00:10:14 +0000
> From: Rui Miguel Seabra <rms@1407.org>
> To: AbiWord-Dev <abiword-dev@abisource.com>
> Subject: Re: commit: Make xft print properly (I think).
>
> On Sun, Nov 10, 2002 at 10:46:46AM +1100, Martin Sevior wrote:
> > On 9 Nov 2002, Dom Lachowicz wrote:
> > > Seems to work just fine now on the 5 documents I threw at it. Thanks!
> > Great! Should we retag?
>
> Am I the only one experiencing 100% cpu usage and/or some, apparently, menu
> related bug besides crash on exit?

Note: I just build a cvs update that differs (I think) only of Martin's
ps fix, and built a DEBUG=1 build.

My problems did not happen. However, View->Toolbars->Table complained
the following assertions:

**** (1) Assert ****
**** (1) UT_SHOULD_NOT_HAPPEN at fl_DocLayout.cpp:563 ****
**** (1) Continue ? (y/n) [y] : y

**** (2) Assert ****
**** (2) pBL at fv_View_protected.cpp:1068 ****
**** (2) Continue ? (y/n) [y] : y

**** (3) Assert ****
**** (3) pBL at ap_TopRuler.cpp:1424 ****
**** (3) Continue ? (y/n) [y] : y

**** (4) Assert ****
**** (4) UT_SHOULD_NOT_HAPPEN at fl_DocLayout.cpp:563 ****
**** (4) Continue ? (y/n) [y] : y

**** (5) Assert ****
**** (5) pBL at fv_View_protected.cpp:1068 ****
**** (5) Continue ? (y/n) [y] : y

**** (6) Assert ****
**** (6) pBL at ap_TopRuler.cpp:1424 ****
**** (6) Continue ? (y/n) [y] : y
DEBUG: SEVIOR: frame view updater

**** (7) Assert ****
**** (7) UT_SHOULD_NOT_HAPPEN at fl_DocLayout.cpp:563 ****
**** (7) Continue ? (y/n) [y] : y

**** (8) Assert ****
**** (8) pBL at fv_View_protected.cpp:1068 ****
**** (8) Continue ? (y/n) [y] : y

**** (9) Assert ****
**** (9) pBL at ap_TopRuler.cpp:1424 ****
**** (9) Continue ? (y/n) [y] : y

**** (10) Assert ****
**** (10) UT_SHOULD_NOT_HAPPEN at fl_DocLayout.cpp:563 ****
**** (10) Continue ? (y/n) [y] : y

**** (11) Assert ****
**** (11) pBL at fv_View_protected.cpp:1068 ****
**** (11) Continue ? (y/n) [y] : y

**** (12) Assert ****
**** (12) pBL at ap_TopRuler.cpp:1424 ****
**** (12) Continue ? (y/n) [y] :

Toggling that toolbar back to off did not show any warning, and toggling
on again also did not show any warning (looks awfully like some non
initialized variables).

I might as well build DEBUG=1 rpms as some DEBUG=0

So it's up to what you'd rather.

Rui

Next message: Dom Lachowicz: "Commit: more XFT font work"
Previous message: Rui Miguel Seabra: "Re: commit: Make xft print properly (I think)."
In reply to: Rui Miguel Seabra: "Re: commit: Make xft print properly (I think)."
Next in thread: Martin Sevior: "Re: commit: Make xft print properly (I think)."
Reply: Martin Sevior: "Re: commit: Make xft print properly (I think)."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Sat Nov 09 2002 - 19:18:23 EST