On 2/5/21 6:30 PM, V K wrote:
>> Do you also see this with other insets? E.g., footnotes? Does it matter if 
>> the top of the inset is still on screen? Or if the bottom is off? Does the 
>> inset need to be bigger than the screen for you to see this?
>> JMard will know better than I, but I think there may be something weird that 
>> happens once an inset spans the whole screen.
>> Riki
> Inset must be really huge to see big sluggishness. If it is bigger than 
> screan, let's say, is like 7 screens long), I hear spike of CPU and see some 
> sluggishness, if it is like three screens, I hear spike of CPU but see no 
> sluggish. 
> I created Lyx note, greyedout, comment, marginnote and footnote – the same 
> behaviour.

OK, that helps: It's a general problem with this kind of inset.

> Yes, inset mus be bigger, but it doesn't matter is the top or bottom of the 
> inset on screen. Text scrolls evenly until top or bottom of inset appears on 
> screen, then CPU spikes and text jumps – stops – jumps. After inset 
> disappears, text scrolls evenly. To be more precise, text scroll evenly and 
> then stops when I even don't see inset – as I understand, it stops when inset 
> should appear on screen if scroll would continue at the same speed. So I 
> don't see inset and some normal text before or after inset. The bigger is 
> speed of scroll, the bigger portion of normal text before or after inset I 
> don't see too. And the bigger jump after such freeze is.

One more question: Does it occur when the *only* thing on the screen is
the inset?

As I said, I suspect that something weird happens with the metrics
calculation here. Either that, or there is some reason we paint the
screen multiple times, and maybe that is slower on Wayland.

It is worse on Wayland?


lyx-users mailing list

Reply via email to