commit -- better fix for #703


Subject: commit -- better fix for #703
From: Aaron Lehmann (aaronl@vitelus.com)
Date: Tue Jun 20 2000 - 01:15:50 CDT


Fixed both problems:
______________________________________________________________________

Better fix for #703. Paul, just TRY fooling this one (I actually tested it
for once :)).
CVS:
----------------------------------------------------------------------
CVS: Enter Log. Lines beginning with `CVS:' are removed automatically
CVS:
CVS: Committing in .
CVS:
CVS: Modified Files:
CVS: src/wp/ap/xp/ap_TopRuler.cpp
CVS:
----------------------------------------------------------------------

> >I was just looking at the bug activity log for #703. On the 12th of June,
> >I checked in a fix after getting this message from you. The next day, you
> >reopened the bug. Are you still able to reproduce this bug?
> >
>
> Yes, I can still reproduce bug #703 in both Linux and Windows. I thought
> that it was quite easy to reproduce, but looking at it again, it seems that
> in order to insert another tab where one already exists, you have to click
> above the existing tab at a certain vertical position, specifically, the
> two pixels below the vertical center of the ruler (I was experimenting with
> the vertical position in Windows; I'm not sure if it is exactly the same in
> Linux, but I was able to insert multiple tabs at one location in Linux as
> well).
>
> A separate bug that I found while inspecting this problem was that dragging
> tabs around can cause AbiWord to crash. One way to reproduce this is to do
> something like this:
> (1) Create new AbiWord document.
> (2) Put in 3 tabs in about the middle of the page as close to each other as
> possible.
> (3) Now make them play leap-frog. Put the tab on the left just after the
> one on the right. Then repeat that process until it crashes on about the
> 1st-15th leap.
>
> -Paul Egli
>



This archive was generated by hypermail 2b25 : Tue Jun 20 2000 - 01:15:56 CDT