[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: Krita 4.4.3 alpha: Optimization for Krita's layer thumbnails
From:       Dmitry Kazakov <dimula73 () gmail ! com>
Date:       2020-11-26 8:50:11
Message-ID: CAEkBSfVidBuZAhh8+Sj9wEvUwTk_89znXm3LPYuyrPWWJYrrCw () mail ! gmail ! com
[Download RAW message or body]

Hi, Eddy!

Afair, layer thumbnail for the currently active layer is recalculated after
every change we do to the image (with 500ms compression/rate limit). What
do you propose to optimize? I don't fully understand :)

On Thu, Nov 26, 2020 at 10:21 AM Eddy Alvaross <eddyalva015@gmail.com>
wrote:

> Greetings. This is a suggestion for how Krita handles layers.
> I've noticed that when we erase void, or empty pixels with an Eraser
> brush, memory is still used to store the pixel data of the erased part.
> It's not a problem at all and is necessary to manage history states
> after each stroke or action in the app. Though the weird part is with the
> layer thumbnails. Because they register empty strokes
> on a layer and display the thumbnails based on them.
> This provoked some doubt in my mind and I was wondering if
> something was wrong.
> Maybe you're already aware of this I don't know.
> If you're aware, this is a reminder.
> If you're not, this is a suggestion.
>


-- 
Dmitry Kazakov

[Attachment #3 (text/html)]

<div dir="ltr"><div>Hi, Eddy!</div><div><br></div><div>Afair, layer thumbnail for the \
currently active layer is recalculated after every change we do to the image (with \
500ms compression/rate limit). What do you propose to optimize? I don&#39;t fully \
understand :)<br></div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Thu, Nov 26, 2020 at 10:21 AM Eddy Alvaross &lt;<a \
href="mailto:eddyalva015@gmail.com">eddyalva015@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div \
dir="ltr">Greetings. This is a suggestion for how Krita handles layers.<br>I&#39;ve \
noticed that when we erase void, or empty pixels with an Eraser<br>brush, memory is \
still used to store the pixel data of the erased part.<br>It&#39;s not a problem at \
all and is necessary to manage history states<br>after each stroke or action in the \
app. Though the weird part is with the layer thumbnails. Because they register  empty \
strokes <br>on a layer and display the thumbnails based on them.<br>This provoked \
some doubt in my mind and I was wondering if<br>something was wrong.  <br>Maybe \
you&#39;re already aware of this I don&#39;t know.<br>If you&#39;re aware, this is a \
reminder.  <br>If you&#39;re not, this is a suggestion.</div> </blockquote></div><br \
clear="all"><br>-- <br><div dir="ltr" class="gmail_signature">Dmitry Kazakov</div>



[prev in list] [next in list] [prev in thread] [next in thread]