Vincent van Ravesteijn - TNW wrote:
When you try to scroll past a long inset, LyX can't position the
cursor properly. It doesn't try to put it into the inset. As a result
the cursor will be placed after the inset. After the inset, means
immediately right of the upper-right corner of the inset.
I
>> When you try to scroll past a long inset, LyX can't position the
>> cursor properly. It doesn't try to put it into the inset. As a result
>> the cursor will be placed after the inset. After the inset, means
>> immediately right of the upper-right corner of the inset.
>
>I always wondered why t
Vincent van Ravesteijn - TNW wrote:
When you try to scroll past a long inset, LyX can't position the cursor properly. It doesn't try to put it into the inset. As a result the cursor will be
placed after the inset. After the inset, means immediately right of the
upper-right corner of the inset.
Vincent van Ravesteijn - TNW wrote:
> Until now, everything is fine, but if you now want to scroll down further
> with PgDown, LyX instead first scrolls up to show the cursor. After
> scrolling up, it will again scroll down and try to position the cursor. The
> cursor will again end up after the in
>> The reason is that the cursor cannot be accomodated on a certain row,
>> when the inset spreads over the full width. A very simple fix is to
>> remove the following lines:
>>
>> bufferview@1402--1406:
>> if (p.y_ < 0 || p.y_ > height_) {
>> // The cursor is off-screen so re
Vincent van Ravesteijn wrote:
> The reason is that the cursor cannot be accomodated on a certain row,
> when the inset spreads over the full width. A very simple fix is to
> remove the following lines:
>
> bufferview@1402--1406:
> if (p.y_ < 0 || p.y_ > height_) {
> // The curso
Vincent van Ravesteijn wrote:
The very annoying bug 5465 prevents one from scrolling down when you
come across a large inset. For example, a figure float with a few
subfloats in it, or a very long ERT, or a long table.
The reason is that the cursor cannot be accomodated on a certain row,
when
