[krita] [Bug 428321] New: Selection Tools Have Unexpected Subtractive Behaviour
https://bugs.kde.org/show_bug.cgi?id=428321 Bug ID: 428321 Summary: Selection Tools Have Unexpected Subtractive Behaviour Product: krita Version: 4.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: 3rto...@gmail.com Target Milestone: --- SUMMARY The selection tools in Krita (4.3. 4.4. nightly 12 Oct) have inconsistent/unexpected behaviour in subtractive mode. When one has no pre-existing custom selection on the canvas (i.e the whole canvas is selected hence paintable) invoking a selection in subtractive mode unintuitively selects whatever shape is being draw, rather than selection everything else on the canvas. This behaviour is unexpected for two key reasons 1) It has no distinctive behaviour compared to 'Replace' or 'Add' modes even thought it is a distinct mode. 2) The logical conclusion user makes "I'm SUBTRACTING this area from my paint-able area hence masking it off" results in unexpected result since what the tool actually does is the opposite of this expectation (When there is no pre-existing selection) Though, considering this seems to be how it has always worked I'm assuming this is more of a design thing than a bug. Still I think it would be something worth altering eventually since it would make more sense that way. STEPS TO REPRODUCE 1. Select lasso tool 2. Press S to enter subtractive mode 3. Draw around an object with the intention of removing its surroundings 4. Press delete OBSERVED RESULT You have deleted your object that you were trying to subtract from your selection EXPECTED RESULT You have deleted everything around your object. SOFTWARE/OS VERSIONS 4.3 4.4 Windows: Win10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408669] New: Animation Curves Docker Frame Scrubbing Doesn't Update Visual Indicator
https://bugs.kde.org/show_bug.cgi?id=408669 Bug ID: 408669 Summary: Animation Curves Docker Frame Scrubbing Doesn't Update Visual Indicator Product: krita Version: 4.2.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: 3rto...@gmail.com Target Milestone: --- Created attachment 120853 --> https://bugs.kde.org/attachment.cgi?id=120853=edit As you can see here the frame number keeps changing while scrubbing while the indicator doesnt move SUMMARY In animation curves docker when you drag the top bar frame slider the current frame will change, however, the visual indicator does not get dragged but rather updates when editor is changed. STEPS TO REPRODUCE 1. Open 'Animation' and 'Animation Curves' dockers 2. In 'Animation Curves' scrub the timeline above the curves 3. Change frame in 'Animation' docker OBSERVED RESULT In 'Animation' docker we can see our frame change, however, in 'Animation Curves' docker our frame indicator does not change until frame is updated from other dockers. EXPECTED RESULT In 'Animation Curves' docker visual indicator scrubs with the frame number SOFTWARE/OS VERSIONS Windows: 10 PRO Ver 1803 Build 17134.829 Krita 4.2.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383640] Unable to change the size of the Smart Patch Tool
https://bugs.kde.org/show_bug.cgi?id=383640 Ricardo Nunes <3rto...@gmail.com> changed: What|Removed |Added CC||3rto...@gmail.com --- Comment #3 from Ricardo Nunes <3rto...@gmail.com> --- Can confirm still present in v4.0.0.51-350 on Windows 10 x64 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378147] File layer only updates once
https://bugs.kde.org/show_bug.cgi?id=378147 Ricardo Nunes <3rto...@gmail.com> changed: What|Removed |Added CC||3rto...@gmail.com --- Comment #2 from Ricardo Nunes <3rto...@gmail.com> --- Can confirm still happens on Windows 10 on ver.3.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368360] Krita does not remember shortcut save location.
https://bugs.kde.org/show_bug.cgi?id=368360 --- Comment #2 from Ricardo Nunes <3rto...@gmail.com> --- Ah uh Windows 10 64-bit installation version. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368455] New: Make the Settings - Manage resources - Open resource folder customized
https://bugs.kde.org/show_bug.cgi?id=368455 Bug ID: 368455 Summary: Make the Settings - Manage resources - Open resource folder customized Product: krita Version: 3.0.1 Beta Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: 3rto...@gmail.com Currently it is not possible to define custom route for additional resources (the aforementioned folder) and as such many people who are not computer savvy are stuck with memory expensive resources being stuck in potentially small OS hard drives. Reproducible: Always Expected Results: Being able to easily define folder for custom resource storage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368360] New: Krita does not remember shortcut save location.
https://bugs.kde.org/show_bug.cgi?id=368360 Bug ID: 368360 Summary: Krita does not remember shortcut save location. Product: krita Version: 3.0.1 Beta Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: 3rto...@gmail.com Krita save/load shortcuts always defaults to Krita root folder which is inconvenient for those who use custom locations for their customization files. As such it would be good if shortcut import export save and load would all default to last used folder instead of hard coded one. Reproducible: Always Steps to Reproduce: 1. Open Krita and save a shortcut file in custom location. 2. Try to save again 3. Krita has defaulted back to different location. Actual Results: - Expected Results: - -- You are receiving this mail because: You are watching all bug changes.
