bug 5420

From: Dennis Heuer (dh@onclick.org)
Date: Sat Jul 19 2003 - 14:20:03 EDT

  • Next message: ericzen: "Re: Announce: LibOTS 0.3.0 released"

    Somebody ("sviles_abi@iinet.net.au") edited my bug message 5420 and pleased me to send in some screenshots. I send them in here because bugzilla told me "you did not append a file" four times though I appended a file four times. This took me one hour because I use a ppp connection. It takes me one hour to post a bugzilla bug, and it takes me a day to query for bugs because of 30 questions I can't answer... If you still expect me to use bugzilla instead of this mailinglist, I skip support completely and maybe abiword if it doesn't enhance without my support. This is meant serious . Bugzilla sucks! It sucks! It really sucks!

    So, here the comments to the screenshots. The first screenshot shows that the Print Preview corrupts the blockquoted paragraphs. This seems to happen if the word wrap decision results in something close to 50/50. The corruption is not a printing problem, it appears too if I reload a file (every time. It is a mess) or if I choose another zoom factor. Every re-calculation of blockquoted paragraphs seems to corrupt them. You seem to use another method for calculation while writing and for automated re-calculation. This is strange to me. (I encountered this same error in a normal "align left" letter yesterday. Maybe the error is not related to blockquote.)

    The second screenshot shows the artifacts on the screen after I corrected the paragraph layouts manually. Some lines are drawn over the right paragraph border. Another phenomenon is that if the last line of a blockquoted paragraph is deleted, the previous line that is now the last line keeps being blockquoted instead of turning to "aligned left" as it is normal for a last line.

    Your layout engine is crazy in many ways. For an example, I press the page-up and page-down keys to force the layout engine to redraw the page to get rid of artifacts. I found out that these keys are not able to show the first or the last page in full. It seems that the layout engine stops if the first or the last page is reached but not if it is displayed in whole. Another interesting thing is the ruler bar. It does not switch to the next page if the cursor enters it but if the next page is displayed on about the half of the displayed area (it must reach more visibility than the previous page (51/49 ?) ). Why the ruler bar switches at all? Why not a ruler bar for every page? This would be much easier to implement.

    Greetings

    Dennis Heuer



    This archive was generated by hypermail 2.1.4 : Sat Jul 19 2003 - 14:29:03 EDT