https://bugs.kde.org/show_bug.cgi?id=419281
--- Comment #7 from keyth_qcfx2 <keyth2363...@gmail.com> --- That does not WORK at all!......How do you set this is as "RESOLVED NOT A BUG"? the ad.waitForDone() does nothing that I can see to solve this issue. I think it might give the time to rest and do something but there is no LAYER SWAP just the same. Considering your advice I tried to place wait where you told me and also too on every step of the process in case i was placing it on the wrong spot. I should mention I have tested asynchronization before making this Report, I tryed again and not to my surprise it does not work also *sighs* Because it is NOT asynchronization for I can tell, it feels more like a LAYER LOCK. """ EXPECTED RESULT Ability to change layer after a paste command. """ I don't know what else more to explain this: -I made a sample script that "Does NOT" work -An addon with the same EXACT code that "Does" work I know the rest is working because you did not look at the end result of the code. You even had the addon to compared it too. place a layer above and below and note their names and see the end result, the merge will eat the layer below and not the new layer it created because it thinks it is still on the layer below. the wait of the 2 buttons method gives allows for the selected layer to be in fact be the one that is HIGHLIGHTED and NOT keep python acting from the ORIGINAL layer below it where it started using its original commands. because there is disparity from where the actions act and where they show to be acting according to the layer stack, by the end of a simply copy paste procedure. I talked about the "activateNextLayer" command too that was not used because the 2 button setup literally ignored it and had no need for it. But I had it marked on the code (addon) and spoke how useless it was too. Because if you use that command isolated it will work but NOT if you surround it with other commands. it will be locked and not change regardless. Also making a action does not allow you to create a layer and input names to be saved in variables to be used later so you can use it's name to change its layer because that works. As an Alternative you could say, "why not create a node manually and use the name it so you can swap instead of using actions to copy paste?" Also a bug there but instead on the Paste process, the information is correct on the clipboard but does not lay it on the layer correctly, that I have reported, I even made video demonstrating how it did not work. Also no one gives a shit on that one it seems. ...I am Sorry to say but everything Python in Krita is especially aggravating. I made a damn Color Picker in Krita and I felt like I should punch myself because of even having stupid ideas. But this Copy Paste Thing? it is even worse seriously... If you guys don't believe me, I am okays, I think I did what I could do. I reported both. I had my responses that both are not bugs. I am just gonna use my stupid work around call it a day and not bother anymore. -- You are receiving this mail because: You are watching all bug changes.
