[krita] [Bug 445657] Loading 250 Frames is slow

Tiar bugzilla_noreply at kde.org
Fri Nov 19 04:04:43 GMT 2021


https://bugs.kde.org/show_bug.cgi?id=445657

Tiar <tamtamy.tymona at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Loading 250 Frames          |Loading 250 Frames is slow
                   |performance problem and     |
                   |jump back/forward buttons   |
                   |doesn't seem to do ANYTHING |
                 CC|                            |tamtamy.tymona at gmail.com
         Resolution|WORKSFORME                  |FIXED

--- Comment #7 from Tiar <tamtamy.tymona at gmail.com> ---
> Just a suggestion for the implementation. If I was doing the coding, that's what I would have done in this situation, to speed up the display.

If you have a patch for that, it would be very welcome as a merge request here:
https://invent.kde.org/graphics/krita/-/merge_requests . For now, since it's
very understandable that Krita takes quite a long time for such a big amount of
data to load,  (note that it doesn't need to just show it but allow you to edit
it - I don't think you can edit pixels for every frame in Blender... though I
might be wrong. In any case Blender has much more programmers than us, it's a
much bigger project, so it's uderstandable that it's also more performant).

-------
Also, a note for the next time: one bug report should be about one issue.
Otherwise there are multiple conversations going on about different topics and
it's more difficult for a programmer to see what the issue is/are or when to
close the report (bug reports are very development-oriented, it's our place to
organize work on Krita, so it's important to us to keep it in order). It's
completely fine (even strongly encouraged) to create a three bug reports at the
same time, if you have three issues to report. Bug reports are more like a
register of all issues instead of a forum thread, it's for example very common
for a bug report to wait undefined amount of time without any interaction until
finally someone gets to work on it and makes another comment or closes the
report with a commit hash.

-- 
You are receiving this mail because:
You are watching all bug changes.



More information about the kde-mac mailing list