https://bugs.kde.org/show_bug.cgi?id=441956
Bug ID: 441956
Summary: Qthread with Python broken in Krita 5
Product: krita
Version: unspecified
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: keyth2363...@gmail.com
Target Milestone: ---
SUMMARY
I made a plugin called Tela (https://github.com/EyeOdin/Tela) that worked
perfectly up until Krita 4.4.5 after that everything up too krita 5 it has
become buggy. The issue to my testing was the QThread not working inside Krita
as expected. since the Qt version did not change i can only assume something
that allows QThreads has changed or something like that.
Because the same code runs but it is not actually in a thread to run
independent and not lag the interface. This is the same issue when trying to
run a function inside a thread with Python instead of PyQt5. I assume that now
neither methods work.
STEPS TO REPRODUCE
1. use this plugin in krita 4.4.5 and in krita 5
2. when it tries to update the display by creating a thumbnail(created inside a
QThread) by doing anything (like resizing the docker) the interface will lag.
3. Press the ON button to become DIS to see the difference to when it is not
updating the thumbnail.
OBSERVED RESULT
you will notice that the plugin in 4.4.5 will not lag while in krita 5 it will
be lagging.
EXPECTED RESULT
Running the Qthread and have it work as expected, without lag on the UI.
SOFTWARE/OS VERSIONS
Windows: 10
Qt Version: 5.12
ADDITIONAL INFORMATION
On the Tela Plugin if you press the ON button it will change into DIS mode
where it will run without trying to update the thumbnail. This literally
isolates the QThread operation and you are able to see the plugin not lagging
on either versions of Krita.
Excluding the Option of using a thread as a viable option, I have been trying
find another way to update without lagging but without some help either way
there seems to be a loosing battle as there is not enough information about the
user is doing available in Python to make a update with a good timming.
--
You are receiving this mail because:
You are watching all bug changes.
