[krita] [Bug 437822] Importing workspaces doesn't seem to work, and can't open resources folder
https://bugs.kde.org/show_bug.cgi?id=437822 --- Comment #2 from Dorian Zambo --- (In reply to Ahab Greybeard from comment #1) > Normally, when importing Workspace resources, the imported workspace is not > available until after a krita restart and then should be shown in the > 'Choose workspace' dropdown, via the icon at the far right of the Toolbar, > available for manual selection. > The workspace will be listed by the internal name declaration of the .kws > file, not the filename of the .kws file. > > What do you see after you restart krita, in the 'Choose workspace' selection > dropdown? > > > Further, I believe that on Android (and a Chromebook), it is not possible to > access the resources folder (and other krita files) because of the Android > security features. (This situation may have changed recently.) > > Please go to https:krita-artists.org and sign up and post about your problem > in a new topic there. > In that forum there are quite a few Chromebook and Android users who may be > able to give further advice. Thanks for the swift reply! For the workspace fix you mentioned, I restarted Krita several times over and still didn't see any new workspaces in the dropdown you mentioned (though granted I actually didn't know where to look for them afore reading your reply, so thank you for that), and I ended up reinstalling the entire app. That ended up working somehow as now when I import the workspaces they do show up in the dropdown, so that issue is now resolved. Seems reinstalling was the fix for me, thank you so much for the help on that one! But for the resources folder I had a feeling something like that was the case, I'll take your advice and make a post on it, I'm just hoping I don't need to root my tablet to get access to that area though it may be likely, for rooting is... a process. Once more thank you for your reply and time! Nari -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437822] New: Importing workspaces doesn't seem to work, and can't open resources folder
https://bugs.kde.org/show_bug.cgi?id=437822 Bug ID: 437822 Summary: Importing workspaces doesn't seem to work, and can't open resources folder Product: krita Version: 4.4.3 Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: nario...@gmail.com Target Milestone: --- SUMMARY I had downloaded a workspace and color theme from a github created by another Krita user (who granted was using linux). Whenever I try to import the workspace .kws file nothing happens at all, and when I try to do it manually, by attempting to click the open resources folder nothing happens there as well. STEPS TO REPRODUCE 1. Have a workspace file ready, and go to settings -> manage resources -> import workspaces 2. find your workspace and try to import it. 1. Have a workspace file ready, and go to settings -> manage resources -> import workspaces 2. Try touching the "open resource folder" button. OBSERVED RESULT The screen briefly turns black very briefly, returns to the manage resources menu having nothing changed. Nothing happens. EXPECTED RESULT Dockers would reconfigure as specified by the workspace. The resource folder would open. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Using the 4.4.3 apk version as installed from here: https://krita.org/en/item/krita-4-4-3-released/ ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431681] Unable to use bluetooth keyboard shortcuts after accidentally tapping pagezoom textbox
https://bugs.kde.org/show_bug.cgi?id=431681 --- Comment #8 from Dorian Zambo --- Update to this bug, I've learned that you don't need to restart Krita to get everything working again, you just need to go to the the three dots -> settings-> configure Krita menu. Once you've opened the menu, closing it by pressing cancel will render all 1 button hotkeys usable again. I really don't know how this works but I hope this helps! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431681] Unable to use bluetooth keyboard shortcuts after accidentally tapping pagezoom textbox
https://bugs.kde.org/show_bug.cgi?id=431681 --- Comment #6 from Dorian Zambo --- (In reply to Sharaf from comment #5) > (In reply to Dorian Zambo from comment #4) > > (In reply to Sharaf from comment #2) > > > Hi! > > > > > > From what you describe it seems like a rather serious issue. However I > > > haven't been able to reproduce it. Could you share a recording of this > > > buggy > > > action? > > > > > > Though nothing specific to Input Method changed in Krita 4.4.3 there were > > > few changes which handled focus properly. Could you try the newer release, > > > maybe that fixed it? > > > > I've attached a video of me explaining the error, apologies for the > > incorrect terminologies I'm hoping my point still gets accross. The app is > > still usable just very very annoying when this happens > > > > https://drive.google.com/file/d/1q4t2QfwvhAF5nM5qQb8wzrYzKNQOhccZ/ > > view?usp=drivesdk > > > > Hopefully this helps I was wondering when this bug would be addressed! > > I can't reproduce the exact issue but I do see some problems with using > physical keyboard. So, I'll set this to confirmed. > > Also what soft-keyboard is that? Is it the default one from Samsung? > > PS: Seems somewhat related to https://bugs.kde.org/show_bug.cgi?id=432455 The keyboard I was using in the video is just a regular USB keyboard I connected to my tablet using an adapter. This also happens with my bluetooth keyboard as well, and even if I'm not using a keyboard at all, and enter a textbox the same issue occurs. Due to this, I doubt the keyboard used is a factor here. Also for the issue linked, I tried the fix mentioned and it didn't seem to work at all for my issue. I may be doing something wrong but I believe they may be different issues. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431681] Unable to use bluetooth keyboard shortcuts after accidentally tapping pagezoom textbox
https://bugs.kde.org/show_bug.cgi?id=431681 --- Comment #4 from Dorian Zambo --- (In reply to Sharaf from comment #2) > Hi! > > From what you describe it seems like a rather serious issue. However I > haven't been able to reproduce it. Could you share a recording of this buggy > action? > > Though nothing specific to Input Method changed in Krita 4.4.3 there were > few changes which handled focus properly. Could you try the newer release, > maybe that fixed it? I've attached a video of me explaining the error, apologies for the incorrect terminologies I'm hoping my point still gets accross. The app is still usable just very very annoying when this happens https://drive.google.com/file/d/1q4t2QfwvhAF5nM5qQb8wzrYzKNQOhccZ/view?usp=drivesdk Hopefully this helps I was wondering when this bug would be addressed! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431681] Unable to use bluetooth keyboard shortcuts after accidentally tapping pagezoom textbox
https://bugs.kde.org/show_bug.cgi?id=431681 --- Comment #3 from Dorian Zambo --- (In reply to Sharaf from comment #2) > Hi! > > From what you describe it seems like a rather serious issue. However I > haven't been able to reproduce it. Could you share a recording of this buggy > action? > > Though nothing specific to Input Method changed in Krita 4.4.3 there were > few changes which handled focus properly. Could you try the newer release, > maybe that fixed it? I've attached a video of me explaining the error, apologies for the incorrect terminologies I'm hoping my point still gets accross. The app is still usable just very very annoying when this happens https://drive.google.com/file/d/1q4t2QfwvhAF5nM5qQb8wzrYzKNQOhccZ/view?usp=drivesdk Hopefully this helps I was wondering when this bug would be addressed! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432177] Colorize Mask colors entire layer regardless of where you place strokes
https://bugs.kde.org/show_bug.cgi?id=432177 Dorian Zambo changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from Dorian Zambo --- (In reply to Tiar from comment #1) > Why are you suing 4.2.2? If you're on Android, it's important to update > often because there are new fixes in new versions. The latest one is 4.4.2. > > Remember that you need to place at least two kinds of strokes, not just one. > If you want a circle colored, then you need one stroke indicating the inside > and one stroke indicating the outside (you can mark it as "transparent" in > Tool Options). Does it fix your issue? It seems I made an error in the version number of my report, I'm using 4.4.2, i had to keep looking up the version of the program since I'm using the android version. Also yes, your fix did help my issue. I completely forgot about the "transparent" color that was required when reading the documentation. Thanks for looking this over though, I appreciate your time! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432177] New: Colorize Mask colors entire layer regardless of where you place strokes
https://bugs.kde.org/show_bug.cgi?id=432177 Bug ID: 432177 Summary: Colorize Mask colors entire layer regardless of where you place strokes Product: krita Version: 4.4.2 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: Tools/Colorize Assignee: krita-bugs-n...@kde.org Reporter: nario...@gmail.com Target Milestone: --- SUMMARY I'm trying to use the colorize mask to color my line art when I started noticing that no matter where i place my strokes, the entire layer would be colored after updating. The settings I used didn't matter, adjusting the gap close hint even to 700px didn't help, nor did playing with any of the clean up and edge detection sliders. I thought maybe my line art was full of unclosed holes, so I decided to test out the mask using the procedure I will describe below. This bug renders the colorize mask unusable on Android STEPS TO REPRODUCE 1. Open a new krita document, and draw a circle, either using the tool, or your own hands. The shape doesnt matter, just make sure its closed. 2. add a colorize mask to the layer, and try placing a stroke of a different color directly in the dead center of your shape. 3. Click update. OBSERVED RESULT The entire layer will be colored regardless of where you placed the stroke. EXPECTED RESULT The inside of your shape would be the only thing colored SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Using the -4 bit version of 4.2.2 downloaded from here: https://krita.org/en/item/krita-4-2-2-released/ I am using a Samsung Galaxy Tab S6 Lite, on Android 10.x ADDITIONAL INFORMATION I have also noticed that when you place strokes outside of layer bounds after updating once, and update again, there seems to be a thick black box encompassing the layer that was previously colored. I don't know if this is is important for the issue, but its just something i noticed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431681] Unable to use bluetooth keyboard shortcuts after accidentally tapping pagezoom textbox
https://bugs.kde.org/show_bug.cgi?id=431681 --- Comment #1 from Dorian Zambo --- A quick update, this bug seems to occur with ALL textbox inputs. Whether youre manually entering the size of a your brush or changing the name of a layer, entering the text box will render you unable to use hotkeys from there on out. The only fix is to save your work and completely restart krita, praying that you don't accidentally touch a textbox that session. Hope this helps! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431611] Transform tool sticks to stylus when attempting to resize
https://bugs.kde.org/show_bug.cgi?id=431611 --- Comment #11 from Dorian Zambo --- Hi again, I can confirm the apk you sent does have the bug fixed! After what must be cumulative hours of messing around with the buggy transform tool having work so perfectly smoothly is quite surreal. Many thanks for the signed apk, and I'll be using this version for my arting needs for now. I look forward to the next official release! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431611] Transform tool sticks to stylus when attempting to resize
https://bugs.kde.org/show_bug.cgi?id=431611 --- Comment #9 from Dorian Zambo --- (In reply to Sharaf from comment #8) > :) > > This bug has been fixed, however sadly it didn't make it to our 4.4.2 > release, perhaps I was too slow. Though, I could share an APK if you'd like > to test it. OH I thought the fix made it in due to one of the bug fixes under Android being: *Handle mouse buttons state and touch events properly That seemed very similar to the merge requests on this bug reports' comment section, apologies for my misunderstanding. But yes I would love to test out the apk if it doesn't bother you. Once again sorry if the reopenong caused any further issues! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431611] Transform tool sticks to stylus when attempting to resize
https://bugs.kde.org/show_bug.cgi?id=431611 Dorian Zambo changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #7 from Dorian Zambo --- Apologies if its not within my powers to re-open this but I thought it might be better than making another report on a known bug. The bug has been reduced, the effects of the teleporting seem to reset a bit more often without the need to undo after the 4.4.2 update but it definitely still happens quite a bit. When the teleporting or "sticking" happens, the undo fix still seems to work and "reset" the transform box, but the sticking still happens. I've done a bit more testing and it seems to also occur with the other types of transform too. Warp transform and perspective transform seem to have the same issue as well. It's definitely a manageable bug with the undo fix bit it would be great if it was fixed too! -- You are receiving this mail because: You are watching all bug changes.
