Subject: Re: Superscript (run?) bug
From: Martin Sevior (msevior@mccubbin.ph.unimelb.edu.au)
Date: Thu Jun 01 2000 - 01:10:14 CDT
On Wed, 31 May 2000 montgome@montgomerie.net wrote:
> Quoting Martin Sevior
> <msevior@mccubbin.ph.unimelb.edu.au>:
> > I noticed something like this when developing the
> improved underlining
> > code but I couldn't reproduce it. I'll try to fix it
> since it might be my
> > fault. Thanks for the detailed bug report and
> document. The lack of
> > underlining is a good clue as to what is going on.
> >
>
> I may be misunderstanding what you're saying, but there
> is no 'lack of underlining', as far as I can see
> (though, with the second example, the underlining is in
> the wrong place).
>
I meant that the underlining is wrong too. This indicates that the
method "isSuperscript()" is returning the wrong result for part of the
run. I suspect that the line breaking code is not setting text attributes
correctly for its new run after breaking a long run. Another reason why
getPoint()->isSuperscript() would be a good thing.
Anyway I'll check this now.
Cheers
Martin.
PS. For those top ruler fans, holding down the space bar allows one to go
right past the margin edge. Is this known behaviour?
This archive was generated by hypermail 2b25 : Thu Jun 01 2000 - 01:10:25 CDT