From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH widget-toolkit v2 0/2] improve logpanel behaviour for fast tasks
Date: Wed, 24 Nov 2021 11:43:59 +0100 [thread overview]
Message-ID: <c2f05b83-422d-fd7d-3c31-93f1ce1178f0@proxmox.com> (raw)
In-Reply-To: <20211123120229.3606307-1-d.csapak@proxmox.com>
On 23.11.21 13:02, Dominik Csapak wrote:
> improves the handling of fast moving tasks
> * no glitching
> * catching up to the end of the task log
>
> changes from v1:
> * dropped 3/3 (different approach makes it obsolete)
> * set the length to total when we really need it
> * decouple updating the start parameter from the scrollevent
> * make the scrolling to bottom not rely on the scrollevent for updating
>
> Dominik Csapak (2):
> ui: logpanel: fix glitching fast task logs
> ui: logpanel: catch up to very fast task logs with api calls
>
> src/panel/LogView.js | 49 +++++++++++++++++++++++++++++++++-----------
> 1 file changed, 37 insertions(+), 12 deletions(-)
>
That one now works out very well on all my tests now.
applied, thanks!
prev parent reply other threads:[~2021-11-24 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 12:02 [pve-devel] " Dominik Csapak
2021-11-23 12:02 ` [pve-devel] [PATCH widget-toolkit v2 1/2] ui: logpanel: fix glitching fast task logs Dominik Csapak
2021-11-23 12:02 ` [pve-devel] [PATCH widget-toolkit v2 2/2] ui: logpanel: catch up to very fast task logs with api calls Dominik Csapak
2021-11-24 10:43 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2f05b83-422d-fd7d-3c31-93f1ce1178f0@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox