Bug 6454: Where Things Stand

So, in case anyone else wants to get in on this weird bug. The bug report contains some instructions about how to reproduce. Basically, take a longish document and put the cursor at the end of a word somewhere in the middle. Then scroll up or down for a while and click the mouse in the text.

Re: Bug 6454: Where Things Stand

Whoops, adding back the list (haven't done this for a while...!) On Thu, Mar 18, 2010 at 11:22 PM, Dov Feldstern d...@lyx.org wrote: On Thu, Mar 18, 2010 at 5:48 PM, rgheck rgh...@comcast.net wrote: . . I'm guessing that this is the cause of the problem. Where ought the position to have

Re: Bug 6454: Where Things Stand

And adding the list here, too On 03/18/2010 05:22 PM, Dov Feldstern wrote: On Thu, Mar 18, 2010 at 5:48 PM, rgheckrgh...@comcast.net wrote: . . I'm guessing that this is the cause of the problem. Where ought the position to have been set? I'm not sure I understand this question...

RE: Bug 6454: Where Things Stand

Yes, that's right. So does the attached make sense? It seems to solve it for me, but I have no idea what it does to the RTL stuff. The problems seems to be that we want to draw the cursor, even if it's not visible. To compute the height and place of the cursor, we retrieve what font the text has

Re: Bug 6454: Where Things Stand

On Thu, Mar 18, 2010 at 11:47 PM, rgheck rgh...@bobjweil.com wrote: And adding the list here, too On 03/18/2010 05:22 PM, Dov Feldstern wrote: On Thu, Mar 18, 2010 at 5:48 PM, rgheckrgh...@comcast.net  wrote: . . I'm guessing that this is the cause of the problem. Where ought the

RE: Bug 6454: Where Things Stand

I don't remember: is it correct that boundary only affect the cursor's display? No, probably not. If the cursor is displayed somewhere else, newly entered text will appear somewhere else. If so, and if we're correct that the metrics will not exist only when the cursor's paragraph is off the

Re: Bug 6454: Where Things Stand

On 03/18/2010 06:47 PM, Vincent van Ravesteijn - TNW wrote: Yes, that's right. So does the attached make sense? It seems to solve it for me, but I have no idea what it does to the RTL stuff. The problems seems to be that we want to draw the cursor, even if it's not visible. So what

Re: Bug 6454: Where Things Stand

On 03/18/2010 07:01 PM, Dov Feldstern wrote: So, in order to figure this out, I added the debug prints mentioned above, and then I noticed that only when we're at the end of a word, but not anywhere else, then a line is printed every time the cursor blinks --- whether or not the cursor is on

Re: Bug 6454: Where Things Stand

On Fri, Mar 19, 2010 at 1:22 AM, rgheck rgh...@bobjweil.com wrote: On 03/18/2010 07:01 PM, Dov Feldstern wrote: So, in order to figure this out, I added the debug prints mentioned above, and then I noticed that only when we're at the end of a word, but not anywhere else, then a line is

Re: Bug 6454: Where Things Stand

On Fri, Mar 19, 2010 at 1:25 AM, Dov Feldstern d...@lyx.org wrote: On Fri, Mar 19, 2010 at 1:22 AM, rgheck rgh...@bobjweil.com wrote: On 03/18/2010 07:01 PM, Dov Feldstern wrote: So, in order to figure this out, I added the debug prints mentioned above, and then I noticed that only when we're

Bug 6454: Where Things Stand

So, in case anyone else wants to get in on this weird bug. The bug report contains some instructions about how to reproduce. Basically, take a longish document and put the cursor at the end of a word somewhere in the middle. Then scroll up or down for a while and click the mouse in the text.

Re: Bug 6454: Where Things Stand

Whoops, adding back the list (haven't done this for a while...!) On Thu, Mar 18, 2010 at 11:22 PM, Dov Feldstern wrote: > On Thu, Mar 18, 2010 at 5:48 PM, rgheck wrote: > . > . >> I'm guessing that this is the cause of the problem. >> >> >> Where ought the

Re: Bug 6454: Where Things Stand

And adding the list here, too On 03/18/2010 05:22 PM, Dov Feldstern wrote: On Thu, Mar 18, 2010 at 5:48 PM, rgheck wrote: . . I'm guessing that this is the cause of the problem. Where ought the position to have been set? I'm not sure I understand this

RE: Bug 6454: Where Things Stand

>Yes, that's right. So does the attached make sense? It seems >to solve it for me, but I have no idea what it does to the RTL stuff. The problems seems to be that we want to draw the cursor, even if it's not visible. To compute the height and place of the cursor, we retrieve what font the text

Re: Bug 6454: Where Things Stand

On Thu, Mar 18, 2010 at 11:47 PM, rgheck wrote: > > And adding the list here, too > > On 03/18/2010 05:22 PM, Dov Feldstern wrote: >> >> On Thu, Mar 18, 2010 at 5:48 PM, rgheck  wrote: >> . >> . >> >>> I'm guessing that this is the cause of the

RE: Bug 6454: Where Things Stand

>I don't remember: is it correct that boundary only affect the cursor's display? No, probably not. If the cursor is displayed somewhere else, newly entered text will appear somewhere else. >If so, and if we're correct that the metrics will not exist only when the >cursor's paragraph is off the

Re: Bug 6454: Where Things Stand

On 03/18/2010 06:47 PM, Vincent van Ravesteijn - TNW wrote: Yes, that's right. So does the attached make sense? It seems to solve it for me, but I have no idea what it does to the RTL stuff. The problems seems to be that we want to draw the cursor, even if it's not visible. So what

Re: Bug 6454: Where Things Stand

On 03/18/2010 07:01 PM, Dov Feldstern wrote: So, in order to figure this out, I added the debug prints mentioned above, and then I noticed that only when we're at the end of a word, but not anywhere else, then a line is printed every time the cursor blinks --- whether or not the cursor is on

Re: Bug 6454: Where Things Stand

On Fri, Mar 19, 2010 at 1:22 AM, rgheck wrote: > On 03/18/2010 07:01 PM, Dov Feldstern wrote: >> >> So, in order to figure this out, I added the debug prints mentioned >> above, and then I noticed that only when we're at the end of a word, >> but not anywhere else, then a

Re: Bug 6454: Where Things Stand

On Fri, Mar 19, 2010 at 1:25 AM, Dov Feldstern wrote: > On Fri, Mar 19, 2010 at 1:22 AM, rgheck wrote: >> On 03/18/2010 07:01 PM, Dov Feldstern wrote: >>> >>> So, in order to figure this out, I added the debug prints mentioned >>> above, and then I noticed that