[krita] [Bug 384283] New: Shift Alt Click on a Transform Handle doesn't work
https://bugs.kde.org/show_bug.cgi?id=384283 Bug ID: 384283 Summary: Shift Alt Click on a Transform Handle doesn't work Product: krita Version: 3.2.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: transform Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- In the Free transform mode, if you click on a handle with either Shift or Alt down, you respectively scale uniformly and scale around the pivot non-uniformly. If you keep both the Alt and Shift keys down before you click, however, to scale uniformly around the pivot, nothing happens. You must click and drag first, then press the 2 keys. Tested on Win 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384282] New: Adjustment still render inside of a hidden group
https://bugs.kde.org/show_bug.cgi?id=384282 Bug ID: 384282 Summary: Adjustment still render inside of a hidden group Product: krita Version: 3.2.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: adjustment layers Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- Adjustment layers still update with every drawing operation if they're inside a hidden group, but the individual layers are set to visible. They don't affect the document, but it hits the drawing performances pretty hard. And when you toggle the group's visibility back on, often the adjustment layer will show an old composite of the document. If you toggle the visibility off on the individual adjustment layers, they don't update, as expected. It's convenient to put all compositing-related layers inside a separate group, at the top of the document. If you need to change the underlying painting, all you need is 1 click/key press to hide the group, and get back to it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379466] New: Drag on selection outline to move the selection
https://bugs.kde.org/show_bug.cgi?id=379466 Bug ID: 379466 Summary: Drag on selection outline to move the selection Product: krita Version: 3.1.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- Following on a discussion with Dmitry on IRC Krita currently lacks an intuitive way to move selections. There's the global selection mask, but it can be slow and inconvenient on documents with a lot of layers (as it sits at the top of the layer stack). Aseprite 1.2 beta 8 introduced a solution to move the selection: with a selection tool, click and drag on the selection's outline. Demo: http://imgur.com/yFPZOwx It works that way, when the selection tool is active: 1. Drag inside the selection to transform it (there's no separate transform tool as in Krita that's aware of the selection) 2. If you drag on the selection's outline, you move the selection. 3. If you click outside of the selection it creates a new one. 4. If you use a modifier key, you can still move the selection but not transform its content. How it could work in Krita. With a selection tool active and selection in marching ants mode: - Change the icon when you hover the selection's outline or content. The user clicks and drags to move the selection. - If a modifier key is pressed, always draw a new selection. - If you click once, as it works now, deselect everything - if you draw outside the selection, create a new selection. These suggestions take the overlay selection display mode in account. As there's not always a clear outline, you could interact the same way with both modes. Anyway, it's up for discussion. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378733] New: Shape preset can't overlap with multibrush tool
https://bugs.kde.org/show_bug.cgi?id=378733 Bug ID: 378733 Summary: Shape preset can't overlap with multibrush tool Product: krita Version: 3.1.3-beta Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- Created attachment 105003 --> https://bugs.kde.org/attachment.cgi?id=105003=edit Video demo of the bug When you use the multibrush tool with a shape brush preset, when the strokes overlap, strokes and shapes randomly appear and flicker on the canvas. I'd expect the shapes to layer on top of one another in such a case. It'd be a super powerful tool for pattern creation. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378148] New: File layer position resets when opening the document
https://bugs.kde.org/show_bug.cgi?id=378148 Bug ID: 378148 Summary: File layer position resets when opening the document Product: krita Version: 3.1.2 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: transform Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- Steps: 1. Create a file layer 2. Move it with the transform tool 3. Save and close the file. 4. Reopen the document. The file layer's position has been reset. Also happens if the file layer is in a group and you move the group. The only way to save the file layer's transform is to use a transform mask right now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378147] New: File layer only updates once
https://bugs.kde.org/show_bug.cgi?id=378147 Bug ID: 378147 Summary: File layer only updates once Product: krita Version: 3.1.2 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- Created attachment 104754 --> https://bugs.kde.org/attachment.cgi?id=104754=edit File layer not updating after the file on the right was saved Steps: 1. Add a file layer 2. Modify the source of the file layer and save. The file layer updates. 3. Redo step 2. The file layer isn't updated anymore. I tried with different file types and the result is the same. It will only update if you close and reopen the document that contains the file layer. See the attached image. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377552] Pressing navigating layers in rename mode (F2) deselects the layer name
https://bugs.kde.org/show_bug.cgi?id=377552 --- Comment #7 from Nathan Lovato <nathan.lovato@gmail.com> --- That works for the full canvas mode. However the bug where the layer name gets deselected when you Tab from a group to its child remains. By the way I can confirm that this only happens when you tab from a group/layer to its first child (be it a paint layer, a mask...). (In reply to Boudewijn Rempt from comment #6) > Is that an acceptable workaround? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377552] Pressing navigating layers in rename mode (F2) deselects the layer name
https://bugs.kde.org/show_bug.cgi?id=377552 --- Comment #4 from Nathan Lovato <nathan.lovato@gmail.com> --- After running tests on new documents, it seems it only happens in some cases. When you jump from a group to its first child, it seems to always deselect the layer name. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377552] Pressing navigating layers in rename mode (F2) deselects the layer name
https://bugs.kde.org/show_bug.cgi?id=377552 --- Comment #3 from Nathan Lovato <nathan.lovato@gmail.com> --- Created attachment 104538 --> https://bugs.kde.org/attachment.cgi?id=104538=edit Layer name gets deselected when jumping to the first child in the group -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377552] Pressing navigating layers in rename mode (F2) deselects the layer name
https://bugs.kde.org/show_bug.cgi?id=377552 Nathan Lovato <nathan.lovato@gmail.com> changed: What|Removed |Added OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377552] New: Pressing navigating layers in rename mode (F2) deselects the layer name
https://bugs.kde.org/show_bug.cgi?id=377552 Bug ID: 377552 Summary: Pressing navigating layers in rename mode (F2) deselects the layer name Product: krita Version: 3.1.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- When you use F2 to rename multiple layers in a row (using tab or Pg down and F2 again), the layer name always gets deselected. The ability to rename layers with F2 is a great feature to export the individual layers that make up a Krita document, be it for Spriter, Blender or anything else. But in the current state, you always have to press Ctrl A or Ctrl Shift Left arrow to select the layer name, which isn't very convenient. Naming layers is part of a game artist's daily routine, and here's how I'd like to use the tool: 1. Enter isolate layer mode 2. Press F2 and rename the first layers 3. Press tab, name the layer, rinse and repeat Steps for the "bug": 1. In a document with multiple layers 2. Press F2 to rename the currently selected layer 3. Press Tab or Shift Tab to move to the next/previous layer 4. After a short delay, the layer name gets deselected and the typing cursor is placed at the end of the layer name -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377415] New: Random Animated brush always starts with the same frame
https://bugs.kde.org/show_bug.cgi?id=377415 Bug ID: 377415 Summary: Random Animated brush always starts with the same frame Product: krita Version: 3.1.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- Created attachment 104469 --> https://bugs.kde.org/attachment.cgi?id=104469=edit Example stamp vs brush stroke When used, any brushstroke made with an animated brush tip set to random mode will always start with the first frame of the brush tip. When you use the brush as a stamp, it makes it so you can't benefit from the randomness. Also, if your preset has a large spacing, even with multiple brushstrokes, the repetition soon becomes visible. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376613] Flatten doesn't affect file layers
https://bugs.kde.org/show_bug.cgi?id=376613 --- Comment #6 from Nathan Lovato <nathan.lovato@gmail.com> --- Ah yes, sorry for the lack of details. Sounds great :) (In reply to Dmitry Kazakov from comment #5) > Created attachment 104435 [details] > attachment-30403-0.html > > I just checked how PS works: > > 1) If there is a group layer with children, then Ctrl+E shortcut is > automatically **renamed** into "Merge group" and the action doesn't > merge down, but merges the group > 2) If there is a layer with masks, then Ctrl+E doesn't bake it, but > works as usual, merges the layer down. > > So I feel that Ctrl+E with should still flatten, but groups only. But > for other types of layers, Ctrl+E should work as usual. And flatten > would convert the layers into usual paint layers if applicable. What do > you think about such idea? > > On 07.03.2017 16:27, Nathan Lovato wrote: > > https://bugs.kde.org/show_bug.cgi?id=376613 > > > > --- Comment #3 from Nathan Lovato <nathan.lovato@gmail.com> --- > > (In reply to Dmitry Kazakov from comment #2) > >> Could you answer one question? Do you also want Ctrl+E (Merge Down) > >> shortcut to do flatten layer operation when possible? > >> > >> Basically, it would mean that you will have to press Ctrl+E multiple > >> times before merging down a layer with some masks/sublayers: > >> > >> Step 1) Ctrl+E -> Flatten Layer > >> Step 2) Ctrl+E -> Merge Down > > Would it be possible to merge the steps? I.e. Ctrl E -> merge and if > > necessary, > > auto flatten. Otherwise, if the merge operation can do 2 different things > > (flatten or merge) depending on where you use it, plus there's still the > > flatten option, you're going to lose some people. I don't know about Gimp, > > but > > at least Affinity and PS flatten things for you when you use the merge > > function. > > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376613] Flatten doesn't affect file layers
https://bugs.kde.org/show_bug.cgi?id=376613 --- Comment #4 from Nathan Lovato <nathan.lovato@gmail.com> --- (Hi, and thank you for the quick reply :) ) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376613] Flatten doesn't affect file layers
https://bugs.kde.org/show_bug.cgi?id=376613 --- Comment #3 from Nathan Lovato <nathan.lovato@gmail.com> --- (In reply to Dmitry Kazakov from comment #2) > Could you answer one question? Do you also want Ctrl+E (Merge Down) > shortcut to do flatten layer operation when possible? > > Basically, it would mean that you will have to press Ctrl+E multiple > times before merging down a layer with some masks/sublayers: > > Step 1) Ctrl+E -> Flatten Layer > Step 2) Ctrl+E -> Merge Down Would it be possible to merge the steps? I.e. Ctrl E -> merge and if necessary, auto flatten. Otherwise, if the merge operation can do 2 different things (flatten or merge) depending on where you use it, plus there's still the flatten option, you're going to lose some people. I don't know about Gimp, but at least Affinity and PS flatten things for you when you use the merge function. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376613] Flatten doesn't affect file layers
https://bugs.kde.org/show_bug.cgi?id=376613 --- Comment #1 from Nathan Lovato <nathan.lovato@gmail.com> --- (In reply to Nathan Lovato from comment #0) > The "flatten" option is available when you right click on a file layer, but > it doesn't modify it. If you add a transform mask or any type of mask to the layer, it flattens as expected. The behavior is the same on both file and clone layers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376946] JJ: Shortcuts for layer visibility, lock, alpha inherit and locked alpha
https://bugs.kde.org/show_bug.cgi?id=376946 --- Comment #5 from Nathan Lovato <nathan.lovato@gmail.com> --- Great to know then, you're making feel me more excited about Python every time :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376946] New: Shortcuts for layer visibility, lock, alpha inherit and locked alpha
https://bugs.kde.org/show_bug.cgi?id=376946 Bug ID: 376946 Summary: Shortcuts for layer visibility, lock, alpha inherit and locked alpha Product: krita Version: 3.1.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- To manage layers from the keyboard only, I'd like to suggest shortcut entries for: - Layer visibility - Layer lock - Layer preserve alpha - Layer alpha lock They're all available from the F3 menu, but it takes 3 or 4 keystrokes (F3, Alt + letter, sometimes spacebar, and finally enter). These are very common operations, so even if they don't have default shortcuts, I think it'd be useful to have them by default. It'd be ideal if they worked on all selected layers at the same time. It's powerful for both visibility and alpha lock when you have keyboard focus on the layers docker: you use the arrows to navigate the stack and Shift + arrows to select a range of layers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376613] New: Flatten doesn't affect file layers
https://bugs.kde.org/show_bug.cgi?id=376613 Bug ID: 376613 Summary: Flatten doesn't affect file layers Product: krita Version: 3.1.2 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- The "flatten" option is available when you right click on a file layer, but it doesn't modify it. I would expect it to convert the file layer into a regular paint layer (for flexibility, in case you embed a document in another and realize you don't need to keep the reference eventually) or the option to be unavailable/grayed out. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375155] New: Add option to texture each dab instead of stroke
https://bugs.kde.org/show_bug.cgi?id=375155 Bug ID: 375155 Summary: Add option to texture each dab instead of stroke Product: krita Version: 3.1.1 Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Target Milestone: --- Textures are always multiplied or subtracted from a brush stroke. It gives a stencil-like effect that's useful in some cases, but it makes it hard to give the brush a natural look. The main problem is that the texture gets applied evenly to the stroke, so the cutoff doesn't solve the problem, even though it helps to improve results. That's why I'd like to suggest an new option to apply the texture to the brush dab instead of the strokes. This would allow the user to enrich the brush tip in a sense, and to create powerful combinations. I expect it would also make it easier to use textures with the blending brushes, as it would make the stroke more opaque overall with the same spacing (with dabs stacking on top of one another). Currently, it's hard to get good results with textures and the blending engine. Here's a picture to compare the same texture applied to the stroke and to each dab, with the multiply mode: http://i.imgur.com/BxvoORz.png The most interesting part is how the texture shows through as you release the pressure and the flow gets lower. It's similar to how the grain of the paper appears as you finish strokes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374847] paintoppresets using internal patterns bug
https://bugs.kde.org/show_bug.cgi?id=374847 Nathan Lovato <nathan.lovato@gmail.com> changed: What|Removed |Added CC||nathan.lovato@gmail.com --- Comment #2 from Nathan Lovato <nathan.lovato@gmail.com> --- Can confirm the bug. On my config, both Bristle_frottis.kpp and Pastel_texture_thin.kpp use the same pattern: "3-mini-rock-soft.png" While, according to imagemagick, they should respectively use 3-mini-rock-soft.png and 3-rock-smooth.png -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369532] New: Can't "use color as mask" on newly created brush tips - Krita 3.0.1.1
https://bugs.kde.org/show_bug.cgi?id=369532 Bug ID: 369532 Summary: Can't "use color as mask" on newly created brush tips - Krita 3.0.1.1 Product: krita Version: 3.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com In Krita 3.0.1.1, with a newly stamped brush tip, Clicking the "use color as mask" checkbox has no effect. The checkbox gets ticked, but as soon as you leave the brush editing window, it gets unchecked. Also, the brush tip still draws as an opaque black and white image. I moved the .gbr files to another computer running Krita 3.0, and was able to properly change the parameter, save a preset, and move it back to my main workstation. So this seems to be specific to 3.0.1.1. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368274] New: Fuzzy stroke is not random with Color parameters in the pixel brush engine
https://bugs.kde.org/show_bug.cgi?id=368274 Bug ID: 368274 Summary: Fuzzy stroke is not random with Color parameters in the pixel brush engine Product: krita Version: 3.0.1 Beta Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com The value of a brush engine's parameter controlled by a fuzzy stroke sensor sometimes doesn't give random results. It slowly increments the value with each new stroke instead. When it gets to the top of the curve, the value falls back to 0% - it seems to be cycling: http://i66.tinypic.com/282dm5j.png Here's a test with the hue set to fuzzy stroke only, with a lot of strokes. It gives a slow color gradient: http://i66.tinypic.com/aaacr6.png Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368109] New: Document gets inserted 2 times inserting a .kra file on document
https://bugs.kde.org/show_bug.cgi?id=368109 Bug ID: 368109 Summary: Document gets inserted 2 times inserting a .kra file on document Product: krita Version: 3.0.1 Beta Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com When you drag and drop a document from Windows explorer on to an open krita document and pick "insert as a new layer", if it's a .kra file, it gets added twice. It only happens with .kra documents. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368101] New: Unsharp mask filter is too strong by default
https://bugs.kde.org/show_bug.cgi?id=368101 Bug ID: 368101 Summary: Unsharp mask filter is too strong by default Product: krita Version: 3.0.1 Beta Platform: Other URL: http://i.imgur.com/Lh0FWF5.jpg OS: other Status: UNCONFIRMED Severity: minor Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com By default, the Enhance->unsharp mask filter is set to an amount of 50, which produces harsh artifacts on the picture. A default amount of 2 would seem more appropriate. See the picture for a comparison: http://i.imgur.com/Lh0FWF5.jpg An amount set to 2 won't be too strong for large pictures, but it's pretty strong already for smaller images with tight edges. On a side-note: sliders would make it faster to set values for the filter. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366595] New: Wrap-around mode: cannot sample colors outside of the original document
https://bugs.kde.org/show_bug.cgi?id=366595 Bug ID: 366595 Summary: Wrap-around mode: cannot sample colors outside of the original document Product: krita Version: 3.0.1 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com In wrap-around mode, in Krita 3.0 and 3.0.1 alpha, you can't sample colors from the viewport anymore, aside from the source document. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363070] New: Spriter exporter crashes on Windows 10
https://bugs.kde.org/show_bug.cgi?id=363070 Bug ID: 363070 Summary: Spriter exporter crashes on Windows 10 Product: krita Version: 3.0 Beta Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com The export scml option exports the layers and groups to individual images and folders, and then krita crashes. The .SCML file doesn't get created. Here's the file I used last for testing: https://drive.google.com/open?id=0Byo8pGe81YJtVEtSaE05WXJRV2c Reproducible: Always Steps to Reproduce: 1. Export any file to SCML Actual Results: Krita crashes -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360414] New: Airbrush not working with Intuos 4 tablet on Windows
https://bugs.kde.org/show_bug.cgi?id=360414 Bug ID: 360414 Summary: Airbrush not working with Intuos 4 tablet on Windows Product: krita Version: 2.9.11 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com The pixel engine's airbrush parameter doesn't work with the Intuos 4 tablet on Windows 10. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356153] New: Tool Options Drop-Down locked into top left corner of the screen when detached on Windows 8.1
https://bugs.kde.org/show_bug.cgi?id=356153 Bug ID: 356153 Summary: Tool Options Drop-Down locked into top left corner of the screen when detached on Windows 8.1 Product: krita Version: 2.9.9 Platform: Windows CE OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com Here's a picture showing the problem: http://i.imgur.com/ItexHS5.png The panel can't be dragged back over the document. I've tried to switch and extend screens, To press Alt Space and move the panel - it always stays locked into place. Reproducible: Always Steps to Reproduce: 1. Right click on the tool options drop-down 2. Detach it 3. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356154] New: Changing the Tool Options Docker to a toolbar drop-down closes Krita on Windows 8.1
https://bugs.kde.org/show_bug.cgi?id=356154 Bug ID: 356154 Summary: Changing the Tool Options Docker to a toolbar drop-down closes Krita on Windows 8.1 Product: krita Version: 2.9.9 Platform: Windows CE OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: nathan.lovato@gmail.com This only happens if the Tool Options is a docker. I set it to go in the toolbar in Configure Krita. Upon pressing ok, Krita closes automatically/crashes? There is no save prompt, everything closes. Reproducible: Always Steps to Reproduce: 1. Go to configure Krita 2. Change the Tool options docker to go in the toolbar 3. Press ok -- You are receiving this mail because: You are watching all bug changes.
