--===============0206362888==
Content-Type: multipart/alternative; boundary=00151750e618c6dd170481ee5373

--00151750e618c6dd170481ee5373
Content-Type: text/plain; charset=UTF-8

>
> >
> > Why do you think data manager should know anything?
> I think you missed my point :)
>
> Lets say I open an image, I then select an area (non necessarily
> rectangular),
> then I go to the edit menu and choose cut or clear, it will replace my
> selection by transparent pixels in function of selectedness on my image.
> And
> neither KisDataManager::fill/KisDataManager::clear apply in this case,
> since
> they take a rectangle as argument.
>

Ok. Then we need this KisTileHashTable::purge() method. But i still don't
think we should do this during save. E.g. in my emacs workflow i save my
work every ~40sec. If i did the same with Krita, then this full scanning of
tiles would make some troubles.

Btw, AutoCAD has the purge() method too. It removes unused references and
blocks. And it is revealed to the user into File->Drawing
Utilities->Purge... Maybe it could work for Krita too...

Actually, we could do this on opening the image. It happens not so often and
do not disturb the user much. But it would mean that the image becomes
altered (internally) right after opening.


-- 
Dmitry Kazakov

--00151750e618c6dd170481ee5373
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"borde=
r-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-le=
ft: 1ex;"><div class=3D"im">&gt;<br>
&gt; Why do you think data manager should know anything?<br>
</div>I think you missed my point :)<br>
<br>
Lets say I open an image, I then select an area (non necessarily rectangula=
r),<br>
then I go to the edit menu and choose cut or clear, it will replace my<br>
selection by transparent pixels in function of selectedness on my image. An=
d<br>
neither KisDataManager::fill/KisDataManager::clear apply in this case, sinc=
e<br>
they take a rectangle as argument.<br></blockquote></div><br>Ok. Then we ne=
ed this KisTileHashTable::purge() method. But i still don&#39;t think we sh=
ould do this during save. E.g. in my emacs workflow i save my work every ~4=
0sec. If i did the same with Krita, then this full scanning of tiles would =
make some troubles.<br>
<br>Btw, AutoCAD has the purge() method too. It removes unused references a=
nd blocks. And it is revealed to the user into File-&gt;Drawing Utilities-&=
gt;Purge... Maybe it could work for Krita too...<br><br>Actually, we could =
do this on opening the image. It happens not so often and do not disturb th=
e user much. But it would mean that the image becomes altered (internally) =
right after opening.<br>
<br clear=3D"all"><br>-- <br>Dmitry Kazakov<br>

--00151750e618c6dd170481ee5373--

--===============0206362888==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop

--===============0206362888==--