SUMMARY The title says it all. The versions don't seem relevant. It seems that Krita shows the result of moving the layers in the layers docker after the related calculations are done. It'd be far better to make it look changed instantly, and then do the aftermath. It's a cosmetical change but it would actually help a lot. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
It's not a cosmetical change but technical issue. We call this Ergonomics or UI/UX Design. The layer operations, I agree with you, should happen in an instant. I also have a similar problem in Krita 4.3.0. Now, your bug report lacks information. You must include in your details the git hash for the version of Krita you're using, but also your System information fot the bug. You do this by going to "Help > Show system information for bug reports" from the menu bar on the top.
(In reply to stephen from comment #1) > It's not a cosmetical change but technical issue. We call this Ergonomics or > UI/UX Design. > The layer operations, I agree with you, should happen in an instant. > I also have a similar problem in Krita 4.3.0. > Now, your bug report lacks information. You must include in your details the > git hash for the version of Krita you're using, but also your System > information fot the bug. You do this by going to "Help > Show system > information for bug reports" from the menu bar on the top. Thanks for replying. But why is it needed in this case? It happens across all the versions and the OS anyway and this is a whishlist, not actually a bug report.
> It seems that Krita shows the result of moving the layers in the layers docker after the related calculations are done. It'd be far better to make it look changed instantly, and then do the aftermath. This is not the case at all, the calculations and the UI update are in different threads so the visual UI update is not waiting for the layer operations to finish to update itself. The delay on your end could be related to a configuration problem. I get instant feedback on layer reordering in all but macos versions (known issue). Please make sure you have canvas accceletarion set to ANGLE, specially if you are using Intel graphic card, and you have logging turned off for the options that warn about performance penalties (Settings -> Configure Krita -> Performance, and Settings -> Configure Krita -> Canvas Acceleration). Marking as RESOLVED WORKSFORME.
(In reply to vanyossi from comment #3) > > It seems that Krita shows the result of moving the layers in the layers docker after the related calculations are done. It'd be far better to make it look changed instantly, and then do the aftermath. > > This is not the case at all, the calculations and the UI update are in > different threads so the visual UI update is not waiting for the layer > operations to finish to update itself. > > The delay on your end could be related to a configuration problem. I get > instant feedback on layer reordering in all but macos versions (known > issue). Please make sure you have canvas accceletarion set to ANGLE, > specially if you are using Intel graphic card, and you have logging turned > off for the options that warn about performance penalties (Settings -> > Configure Krita -> Performance, and Settings -> Configure Krita -> Canvas > Acceleration). > > Marking as RESOLVED WORKSFORME. I've tried the settings you said and it didn't make any difference. Since another person mentioned that there's a similar problem in Krita 4.3.0, I can cautiously say it's not just me having configuration issues. (And in any case, it SHOULDN'T be affected by the configuration.) Often, the cursor gets laggy too for a short moment of the delay, so this might be not just about how visual update works but how Krita handles the layer performance in general. And it happens even from when I start dragging any layer. I'll post more as I get more informations.
As stated before the change is instant and the UI update is done separatedly from the operations thread. So we do not wait for the layer operation to finish to show the UI update on layer move operations. Im going to suggest you first move this issue to https://krita-artists.org/ a user-space oriented support as im guessing there is something in configuration/drivers/software combination that is messing with the system. The forum is much more suitable for investigating, discussing misterious occurences like this that might be related to things outside Krita's source code. Im going to close this report, but if during the discussion in the forums you find out the specific reason this is happening, you can come and reopen this bug with the findings, as currently there is nothing I can do to even come close to replicate the behaviour you are getting.
(In reply to vanyossi from comment #5) > As stated before the change is instant and the UI update is done separatedly > from the operations thread. So we do not wait for the layer operation to > finish to show the UI update on layer move operations. > > Im going to suggest you first move this issue to https://krita-artists.org/ > a user-space oriented support as im guessing there is something in > configuration/drivers/software combination that is messing with the system. > The forum is much more suitable for investigating, discussing misterious > occurences like this that might be related to things outside Krita's source > code. > > Im going to close this report, but if during the discussion in the forums > you find out the specific reason this is happening, you can come and reopen > this bug with the findings, as currently there is nothing I can do to even > come close to replicate the behaviour you are getting. Ok. Thanks for replying again. ;)