[Marknote] [Bug 487354] New: [Feature Request] Markdown mode
https://bugs.kde.org/show_bug.cgi?id=487354 Bug ID: 487354 Summary: [Feature Request] Markdown mode Classification: Applications Product: Marknote Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: m...@kaidan.im Reporter: vitamorus@gmail.com CC: c...@carlschwan.eu, m...@kaidan.im Target Milestone: --- Hello! I would like to make a request for a markdown/raw text edit mode. This is beneficial for changing around formatting with just the keyboard. For example, the auto-formatting will hide away any '#'-characters when declaring any sort of title (which btw seems to cause a bug if you wanted to make a note about different #include statements in C/C++). But if you wanted to turn that text back into "basic text" you have to use the drop down at the bottom. It's also useful for copy-pasting between applications. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432184] Properties buttons in Layers docker aren't greyed/hidden for layers that don't have properties dialogs
https://bugs.kde.org/show_bug.cgi?id=432184 Vitamorus changed: What|Removed |Added Version|4.4.2 |git master (please specify ||the git hash!) Latest Commit||git 6207a6f (5.3 pre-alpha) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 493436] Layer style + transformed clones + large canvas = extremely long file loading times.
https://bugs.kde.org/show_bug.cgi?id=493436 Vitamorus changed: What|Removed |Added Component|* Unknown |Layer Stack Version|5.2.3 |5.2.6 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Vitamorus --- I can confirm this bug in 5.2.6. I believe it's known that the combination of clone and transform masks isn't very performant (a couple of threads on Krita-Artists and this report https://bugs.kde.org/show_bug.cgi?id=388545) and I would guess this is related. Perhaps the non-destructive properties of the nodes sends Krita into a long recursive chain when generating the image? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429871] Bad initial numbers when entering Pallete color RGB values
https://bugs.kde.org/show_bug.cgi?id=429871 --- Comment #3 from Vitamorus --- I wasn't able to reproduce it at first in either 5.2.6 or the 5.3 pre-alpha. After verifying that I can indeed reproduce it in 4.4.1, however, the faulty initial values showed up in the later Krita versions as well. I think someone from the development team will have to confirm whether it can be marked as resolved or not. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 493436] Layer style + transformed clones + large canvas = extremely long file loading times.
https://bugs.kde.org/show_bug.cgi?id=493436 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428140] Advanced Color Selector looks ugly in horizontal layout
https://bugs.kde.org/show_bug.cgi?id=428140 --- Comment #3 from Vitamorus --- I can confirm this bug persists in the 5.3 pre-alpha on KDE neon. Docker layout breaks and the issue persist after hiding the shade selector. I did find a mention by raghukamath that the Advanced Color Selector is intended to be phased out in favor of the Wide Game Color Selector so perhaps it's relevant to fix. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428140] Advanced Color Selector looks ugly in horizontal layout
https://bugs.kde.org/show_bug.cgi?id=428140 Vitamorus changed: What|Removed |Added Component|Usability |Color Selectors CC||vitamorus@gmail.com Latest Commit||git 6207a6f Version|4.4.0 |git master (please specify ||the git hash!) --- Comment #2 from Vitamorus --- I can confirm this bug persists in the 5.3 pre-alpha on KDE neon. Docker layout breaks and the issue persist after hiding the shade selector. I did find a mention by raghukamath that the Advanced Color Selector is intended to be phased out in favor of the Wide Game Color Selector so perhaps it's relevant to fix. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376101] No 'icon only' option in toolbar customization screen.
https://bugs.kde.org/show_bug.cgi?id=376101 Vitamorus changed: What|Removed |Added Version|3.1.2 |git master (please specify ||the git hash!) Latest Commit||git 6207a6f (5.3 pre-alpha) Keywords||regression Component|Dockers |Usability -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433278] "Bounds" of the panning area seem to only exist visually, but not functionally
https://bugs.kde.org/show_bug.cgi?id=433278 Vitamorus changed: What|Removed |Added Version|4.4.2 |5.2.6 CC||vitamorus@gmail.com --- Comment #2 from Vitamorus --- Re-confirmed for 5.2.6. Indeed it seems like some coordinates aren't properly re-adjusted when panning outside the boundaries using Canvas Inputs (space bar). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375974] canvas does not scroll up when moving cursor too slow
https://bugs.kde.org/show_bug.cgi?id=375974 Vitamorus changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||vitamorus@gmail.com --- Comment #5 from Vitamorus --- Reproduced in 3.1.1, not present in 5.2.6. Marking as fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425318] Strange artifacting when using Copy paint layers and also when using Copy brushes of certain engines
https://bugs.kde.org/show_bug.cgi?id=425318 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|4.3.0 |5.2.6 --- Comment #5 from Vitamorus --- Re-confirmed for 5.2.6. As mentioned, seemingly resolved for the layer stack but still causing artifacts when brush is set to "Copy" blending mode. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408440] Landing page defaults eraser brush to 'off'
https://bugs.kde.org/show_bug.cgi?id=408440 Vitamorus changed: What|Removed |Added Version|4.2.1 |5.2.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358530] Layer Style: Bevel in Wrap Around Mode
https://bugs.kde.org/show_bug.cgi?id=358530 Vitamorus changed: What|Removed |Added Version|2.9.10 |5.2.6 CC||vitamorus@gmail.com --- Comment #6 from Vitamorus --- Re-confirmed for 5.2.6. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447445] appimage extension should be AppImage for desktop integrations
https://bugs.kde.org/show_bug.cgi?id=447445 Vitamorus changed: What|Removed |Added Version|5.0.0 |5.2.6 CC||vitamorus@gmail.com --- Comment #6 from Vitamorus --- Re-confirmed. From a quick search online, using '.AppImage' seems to be the norm out there on the internet (including official appimages by QTractor, Kate, and Kdenlive). Chatted with dmitryK about it as well and it seems reverting back to .AppImage is in order. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408440] Landing page defaults eraser brush to 'off'
https://bugs.kde.org/show_bug.cgi?id=408440 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com --- Comment #4 from Vitamorus --- Re-confirming for 5.2.6. I can reproduce the bug as described in 4.2.1, but the situation has improved somewhat in 5.2.6. The toggle in the Toolbar seems to be set correctly between opening and closing documents without quitting Krita. If you quit Krita with an eraser brush selected, however, it will not be set correctly the next time you open Krita. I could not get eraser brush to paint a colour in either version, however. Jimbo or someone else needs to provide more info whether they can reproduce that issue in a newer version or not. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426010] Clicking on guide outside of canvas boundary deletes it.
https://bugs.kde.org/show_bug.cgi?id=426010 Vitamorus changed: What|Removed |Added Version|4.3.0 |5.2.6 CC||vitamorus@gmail.com --- Comment #2 from Vitamorus --- Re-confirmed. I also noticed that the guide is only visible over the canvas. It's a bit unhelpful IMO since when you first drag a guide out from one of the rulers it doesn't seem like it's working. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434003] Color Selector Settings restore to defaults when pressed when other section is active i.e. Tablet settings
https://bugs.kde.org/show_bug.cgi?id=434003 Vitamorus changed: What|Removed |Added Version|4.4.3-beta1 |5.2.6 --- Comment #6 from Vitamorus --- Reconfirmed for 5.2.6. It does seem like the 'Restore Defaults' respects which section the user is in except in the case of the Colour Selector Settings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442957] Document tab isn't renamed when switching tabs during save operation
https://bugs.kde.org/show_bug.cgi?id=442957 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Vitamorus --- Reproduced in 5.0.0-beta1, resolved in 5.2.6! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422750] On canvas HUD color picker (square type) or color history swatches are hard to use due to no buffer area on edges
https://bugs.kde.org/show_bug.cgi?id=422750 Vitamorus changed: What|Removed |Added Version|4.2.9 |5.2.6 CC||vitamorus@gmail.com --- Comment #4 from Vitamorus --- Re-confirming for 5.2.6. Technically not a bug, but definitely a UX-problem. Tiar's idea sounds good to me, having a transparent margin around the widget where you can move the cursor without the widget closing. Clicking the margin would close the widget and immediately draw on the canvas (if a drawing tool is selected), on top of also just moving the cursor further off to close the widget. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441900] Color history on pop-up palette is out of order
https://bugs.kde.org/show_bug.cgi?id=441900 Vitamorus changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |vitamorus@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441900] Color history on pop-up palette is out of order
https://bugs.kde.org/show_bug.cgi?id=441900 Vitamorus changed: What|Removed |Added Version|5.0.0-beta1 |5.2.6 --- Comment #4 from Vitamorus --- Confirming this is still the case. I agree that it would make sense for a color history to be ordered chronologically but perhaps it needs further discussion. Since it's technically not a bug I would argue it should be labelled as 'wishlist' but I can't change the importance/severity myself. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441900] Color history on pop-up palette is out of order
https://bugs.kde.org/show_bug.cgi?id=441900 Vitamorus changed: What|Removed |Added Assignee|vitamorus@gmail.com |krita-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447514] New gradient smoothing is not applied to mesh gradients / Mesh gradients looking really blocky
https://bugs.kde.org/show_bug.cgi?id=447514 Vitamorus changed: What|Removed |Added Version|5.0.0 |nightly build (please ||specify the git hash!) CC||vitamorus@gmail.com Latest Commit||git 021e347 --- Comment #4 from Vitamorus --- Re-confirming this for 5.3 pre-alpha. Also lead to the discovery of a new bug 496519. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 496519] New: Editing handles of mesh gradient raises safe assert
https://bugs.kde.org/show_bug.cgi?id=496519 Bug ID: 496519 Summary: Editing handles of mesh gradient raises safe assert Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: vitamorus@gmail.com Target Milestone: --- Created attachment 175992 --> https://bugs.kde.org/attachment.cgi?id=175992&action=edit Rendering errors in the "frame" A safe assert is raised when editing the handles of a mesh gradient. I am unable to reproduce it in 5.2.6, meaning it's new for 5.3. Probably related is some rendering errors of the "frame" around the vector shape in question. Steps to reproduce: 1. Create a new document 2. Add a vector layer and draw a shape (like a rectangle) 3. Set the fill to Mesh Gradient and try moving some of the handles around. 4. A warning dialog will appear: Krita has encountered an internal error: SAFE ASSERT (krita): "!m_sanityIsStarting" in file /builds/graphics/krita/libs/global/kis_signal_compressor.cpp, line 210 5. Clicking "Ignore" results in a second dialog with: SAFE ASSERT (krita): "m_timer->isActive()" in file /builds/graphics/krita/libs/global/kis_signal_compressor.cpp, line 148 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437365] Numbered value scale in artistic color selector does not show numbers
https://bugs.kde.org/show_bug.cgi?id=437365 --- Comment #5 from Vitamorus --- Created attachment 176009 --> https://bugs.kde.org/attachment.cgi?id=176009&action=edit The value strip without text -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437365] Numbered value scale in artistic color selector does not show numbers
https://bugs.kde.org/show_bug.cgi?id=437365 --- Comment #4 from Vitamorus --- Created attachment 176008 --> https://bugs.kde.org/attachment.cgi?id=176008&action=edit The value strip with text, just above the disappearing threshold -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 496519] Editing handles of mesh gradient raises safe assert
https://bugs.kde.org/show_bug.cgi?id=496519 Vitamorus changed: What|Removed |Added Latest Commit||git 021e347 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442531] Menus on 'Brushes and Stuff' toolbar are sticky.
https://bugs.kde.org/show_bug.cgi?id=442531 Vitamorus changed: What|Removed |Added Platform|unspecified |Microsoft Windows Version|5.0.0-beta1 |5.2.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359858] Round pixel brush jagged when size is between 9 and 4.
https://bugs.kde.org/show_bug.cgi?id=359858 Vitamorus changed: What|Removed |Added Latest Commit||23882dc CC||vitamorus@gmail.com Version|3.0 Alpha |git master (please specify ||the git hash!) --- Comment #14 from Vitamorus --- Re-confirming this for 5.3 pre-alpha. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419976] c)_Pencil-3_Large_4B brush glitches on second picture
https://bugs.kde.org/show_bug.cgi?id=419976 Vitamorus changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||vitamorus@gmail.com --- Comment #5 from Vitamorus --- Reproduced in 4.2.9, resolved in 5.3 pre-alpha! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447891] In the Comic Manager, when edit Exportation Parameters, cannot select a color for the layers to be removed
https://bugs.kde.org/show_bug.cgi?id=447891 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com --- Comment #2 from Vitamorus --- Re-confirming this for 5.2.6. Checkboxes for the colour labels (though the checkboxes are a bit large) has appeared since 5.0.2. It helps clarify which coloured layers you want to exclude in the export. Checking the comicConfig.json file confirms that the settings are exported as intended. However if you close the export settings and re-open it again the checkboxes will all be unticked again. In other words, the checkboxes don't reflect the comicConfig.json. That's pretty frustrating because it means having to tick and untick a label if you want to go from excluding to including layers of that label. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408443] Input field on sliders don't lose focus when clicking outside of the input field
https://bugs.kde.org/show_bug.cgi?id=408443 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|4.2.1 |5.2.6 --- Comment #2 from Vitamorus --- Re-confirmed for 5.2.6. Based solely on Wolthera's comment it might be a limitation with Qt (resolved in Qt 6?). Reimplementing some mouse event possible/sensible? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442531] Menus on 'Brushes and Stuff' toolbar are sticky.
https://bugs.kde.org/show_bug.cgi?id=442531 Vitamorus changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||vitamorus@gmail.com --- Comment #2 from Vitamorus --- I cannot reproduce this on either version on Linux (elementary 7.1) so this could possibly be Windows-specific. If Jehu, Ahab or someone else with a Windows machine could re-confirm this bug for 5.2.6 that would be appreciated! I'll somewhat reluctantly (because it's so recent) label this as NEEDSINFO for now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 347799] The color sampler rotates with the canvas
https://bugs.kde.org/show_bug.cgi?id=347799 Vitamorus changed: What|Removed |Added Version|2.9.4 |5.2.6 CC||vitamorus@gmail.com --- Comment #4 from Vitamorus --- Re-confirmed for 5.2.6. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425525] Brush Settings options (size, ratio, etc.) don't remember which sensor you were looking at in certain cases
https://bugs.kde.org/show_bug.cgi?id=425525 Vitamorus changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||vitamorus@gmail.com --- Comment #3 from Vitamorus --- Was able to reproduce this bug in 4.2.0 but not in 5.2.6, marking as resolved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419715] Ctrl (and main tool) colour selectors (pickers) have incorrect icons.
https://bugs.kde.org/show_bug.cgi?id=419715 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|4.2.9 |5.2.6 --- Comment #6 from Vitamorus --- Re-confirming this for 5.2.6. Though this seems to have strayed a bit from it's original intent as a bug report: - This could potentially be considered a wishlist item to rework the Color Sampler invocation (i.e. Canvas Input) to more accurately reflect the Color Sampler Tool and its user configuration - The documentation of the Color Sampler Tool should be updated to be more accurate: right now Ctrl doesn't actually active the real Color Sampler Tool. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419715] Ctrl (and main tool) colour selectors (pickers) have incorrect icons.
https://bugs.kde.org/show_bug.cgi?id=419715 --- Comment #7 from Vitamorus --- Though this seems to have strayed a bit from it's original intent as a bug report: - This could potentially be considered a wishlist item to rework the Color Sampler invocation (i.e. Canvas Input) to more accurately reflect the Color Sampler Tool and its user configuration - The documentation of the Color Sampler Tool should be updated to be more accurate: right now Ctrl doesn't actually active the real Color Sampler Tool. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381343] Application fails to close on scripting bug if main window closed first
https://bugs.kde.org/show_bug.cgi?id=381343 Vitamorus changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||vitamorus@gmail.com Status|CONFIRMED |NEEDSINFO --- Comment #1 from Vitamorus --- Hello Brendan I'm trying to re-confirm whether this bug is still present in Krita. I'm actually unable to open the scripter in the 4.0 pre-alpha (some of the 4.0 versions (pre-alpha, beta, release) of Krita don't open at all, actually). I've tested this in Krita 4.0.1 and cannot reproduce the bug. I'm also not sure what the supposed bug is, if there is one? It sounds like you want Krita to re-open after closing the scripter dialog, but it's not supposed to if you deliberately closed Krita. Could you please provide a bit more details about the bug? can you clarify what the bug is and/or what the expected functionality is? can you reproduce the bug in the latest version of Krita? if you can reproduce it, please provide a video recording of the issue if possible other helpful information to the developers: System info from “Help->Show system information for bug reports” Krita log from “Help->Show Krita log for bug reports” Thanks in advance! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412333] Cursor disappears after selecting color in another image.
https://bugs.kde.org/show_bug.cgi?id=412333 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Latest Commit||5.3.0-prealpha (git ||021e347) Version|4.2.7-beta1 |git master (please specify ||the git hash!) Component|Color Selectors |General --- Comment #12 from Vitamorus --- Re-confirmed with 5.3 pre-alpha. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413763] 'Clear' feature doesn't work if some tool is selected.
https://bugs.kde.org/show_bug.cgi?id=413763 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|4.2.7 |5.2.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410734] Brush with orientation tied to direction acts jumpy.
https://bugs.kde.org/show_bug.cgi?id=410734 Vitamorus changed: What|Removed |Added Version|4.2.5 |5.2.6 CC||vitamorus@gmail.com --- Comment #5 from Vitamorus --- Re-confirmed for 5.2.6. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433288] Calligraphy tool does not correctly follow a transformed vector object/shape
https://bugs.kde.org/show_bug.cgi?id=433288 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|4.4.2 |5.2.6 --- Comment #2 from Vitamorus --- Re-confirmed for 5.2.6. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429503] Ambiguous keyboard shortcut shown in the help message that appears in the status bar while edit shapes tool is active
https://bugs.kde.org/show_bug.cgi?id=429503 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|4.4.1 |5.2.6 --- Comment #5 from Vitamorus --- Re-confirmed for 5.2.6. As Ahab pointed out, this requires some discussion about the course of action. First off, it's probably not a good idea to have descriptions with "hard coded" shortcuts (e.g. "Press B to break path at selected segments"), which isn't even the default shortcut in Krita because it collides with the shortcut for the Freehand Brush tool. Second, either the default shortcut scheme needs to be rethought (relatively easy) and/or the way Krita handles shortcuts needs to be reworked to allowed for different tools/layers/"modes" to have separate shortcut schemes (bigger project, perhaps limited by Qt?). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408369] Tool Glitch with selection
https://bugs.kde.org/show_bug.cgi?id=408369 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com --- Comment #4 from Vitamorus --- Created attachment 175806 --> https://bugs.kde.org/attachment.cgi?id=175806&action=edit Selection with missing outline and 0 px wide sections Re-confirming this for 5.2.6. So, to clarify: If you open/create a new document, click on any of the selection tools, set it to 'Subtract' and make a new selection, Krita will automatically generate a selection of the entire canvas and subtract from it. If you're zoomed in and unaware of this feature, it looks like subtract is adding a selection. This seems to be intentional and not a bug. I don't know if it's preferable from a UX perspective though. I think some would argue that that all selections should be explicit and making a subtraction selection from nothing should just do nothing. However, as Ahab discovered, the 'Intersect' mode can sometimes produce some visual glitches. I've attached an image showing a possible result; missing selection outlines and sections that are 0 px wide. Note that this is only a visual bug with the outline, and that drawing over the selection shows what the real selection is. If I add/subtract a couple of additional selections elsewhere on the canvas the outline will "refresh" and correct itself. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408369] Tool Glitch with selection
https://bugs.kde.org/show_bug.cgi?id=408369 Vitamorus changed: What|Removed |Added Version|4.2.0 |5.2.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445935] Wrong/Zero selection. Less then 1 px
https://bugs.kde.org/show_bug.cgi?id=445935 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com --- Comment #2 from Vitamorus --- I can reproduce this in 5.2.6. It seems the original report was about how making a 0x0 px selection while in 'Replace'-mode will effectively act as deselecting. I assume this is intentional behaviour, but I understand if it's annoying on the occasions you misclick and you remove your selection. This is just a matter of hitting Undo (Ctrl + Z) to restore the selection, though. As Ahab pointed out, though, vector selection allows you to make valid selections with 0 px in width or height as long as the other length is >0. I think it'd better if, when making a selection, the selection should only be valid (i.e. generate an outline) if both the length and width are greater than 0. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445935] Wrong/Zero selection. Less then 1 px
https://bugs.kde.org/show_bug.cgi?id=445935 Vitamorus changed: What|Removed |Added Version|5.0.0-beta2 |5.2.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418317] Copying a selection from a vector layer creates a normal layer
https://bugs.kde.org/show_bug.cgi?id=418317 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|4.2.8 |5.2.6 --- Comment #2 from Vitamorus --- Re-confirmed for 5.2.6. This is technically not a bug, I think, but it is a flaw in the UX. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430774] Gradient filling over Text objects can only makes them red.
https://bugs.kde.org/show_bug.cgi?id=430774 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Vitamorus --- Reproduced in 4.4.5, not in 5.2.6. Marking as resolved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 329663] Do not allow conflicting shortcuts in "Configure Shortcuts" and "Custom Input Settings"
https://bugs.kde.org/show_bug.cgi?id=329663 Vitamorus changed: What|Removed |Added Version|2.8 Beta|5.2.6 CC||vitamorus@gmail.com --- Comment #13 from Vitamorus --- Just going ahead and setting this to Krita 5.2.6 (from 2.8) as part of the Bughunt Month. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447891] In the Comic Manager, when edit Exportation Parameters, cannot select a color for the layers to be removed
https://bugs.kde.org/show_bug.cgi?id=447891 Vitamorus changed: What|Removed |Added Version|5.0.2 |5.2.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448240] The window is too high for the Android tablet to see the buttons.
https://bugs.kde.org/show_bug.cgi?id=448240 Vitamorus changed: What|Removed |Added OS|Other |Unspecified CC||vitamorus@gmail.com Platform|Other |Android -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 496262] Resize canvas dialogue initially set to px and has decimal places
https://bugs.kde.org/show_bug.cgi?id=496262 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Vitamorus --- Verifying that this is happening to me as well, thank you for the report Paul! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433288] Calligraphy tool does not correctly follow a transformed vector object/shape
https://bugs.kde.org/show_bug.cgi?id=433288 --- Comment #3 from Vitamorus --- Additionally, 'Follow selected path' breaks and becomes misaligned if you use the Move tool to move the shape instead of the Select Shapes tool. That doesn't seem like a desirable effect. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 351263] Stabilizer causes jagged line endings without "stabilizer sensors" also enabled
https://bugs.kde.org/show_bug.cgi?id=351263 Vitamorus changed: What|Removed |Added Version|2.9.4 |5.2.6 CC||vitamorus@gmail.com --- Comment #8 from Vitamorus --- Re-confirming this for 5.2.6. As Halla pointed out, though, the "Stabilize sensors" check box is there to solve this issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402791] Color changes when selecting layers
https://bugs.kde.org/show_bug.cgi?id=402791 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com --- Comment #12 from Vitamorus --- Re-confirmed for 5.2.6. I couldn't get the Advanced Colour Selector to make as dramatic leaps as in the gif recordings, but the circle moves around nonetheless. This minor visual bug isn't present in the Wide Gamut Colour Selector though, so it comes back to a question of whether it's worth trying to fix when the ACS is set to be replaced by the WGCS. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396929] Tools stop working after using Color Picker with "Sample Current Layer" on a hidden layer
https://bugs.kde.org/show_bug.cgi?id=396929 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Vitamorus --- Appears to no longer be present in 5.2.6. The message box no longer appears, instead the color picker simply doesn't pick up any color. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380116] Brushes with hsv settings and low opacity
https://bugs.kde.org/show_bug.cgi?id=380116 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|3.1.3 |5.2.6 --- Comment #2 from Vitamorus --- re-confirmed for 5.2.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 497371] New: Have the Close button of the Session Manager terminate all Krita processes
https://bugs.kde.org/show_bug.cgi?id=497371 Bug ID: 497371 Summary: Have the Close button of the Session Manager terminate all Krita processes Classification: Applications Product: krita Version: 5.2.6 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: vitamorus@gmail.com Target Milestone: --- SUMMARY When setting Krita to start with the Session Manager, pressing the close button will continue to launch the main window. This was a workaround for Bug 431755. After a quick exchange on the IRC it seems unclear if this is the desired functionality of the Close button on the Session Manager, though. While this definitely is preferable to having a useless background process (that keeps Krita from launching at a later point) I would make the case that the Close button should really abort the launch and terminate all processes related to Krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431755] Krita continues running in the background after closing session manager
https://bugs.kde.org/show_bug.cgi?id=431755 Vitamorus changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||vitamorus@gmail.com --- Comment #9 from Vitamorus --- Alvin's patch solves the main issue of this bug report so I'll mark it as resolved. It's arguably a bit weird in terms of UX, though, so I've filed a wishlist report (Bug 497371) for further discussion. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427104] 'Gradient Map' texturing mode interprets a pattern's alpha channel as the leftmost colour
https://bugs.kde.org/show_bug.cgi?id=427104 Vitamorus changed: What|Removed |Added Version|4.4.0-beta1 |5.2.6 CC||vitamorus@gmail.com --- Comment #4 from Vitamorus --- Re-confirmed for 5.2.6, kinda. Krita no longer interprets transparency as black, so binary black and white patterns no longer turn completely solid. Instead there's a bit of an question regarding transparency being mapped to white or not. Like Wolthera said, either transparency needs to be more clearly communicated or transparency should be mapped to white to be more consistent with the preview/thumbnails in the pattern picker. But I would argue that there's use for transparency being kept separate from either black or white. For example, you have a pattern of a chain link fence that goes from black to white in terms of colour and then utilizes transparency between the wires of the fence. So there's need for a better way to communicate transparency in the pattern picker (checkerboard/no background for the larger preview? a badge on the thumbnails that indicates an alpha channel?). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402791] Color changes when selecting layers
https://bugs.kde.org/show_bug.cgi?id=402791 Vitamorus changed: What|Removed |Added Version|4.1.7 |5.2.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411868] Setting font/size of highlighted text doesn't work if text under cursor has same font/size
https://bugs.kde.org/show_bug.cgi?id=411868 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|4.2.6 |5.2.6 --- Comment #3 from Vitamorus --- Re-confirming this bug for 5.2.6. Hopefully this won't be an issue after Wolthera's rework of the text tool :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421289] Broken Channels management
https://bugs.kde.org/show_bug.cgi?id=421289 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Vitamorus --- Recreated in 4.2.9 but resolved in 5.2.6! - channels() function correctly retrieved each colour channel - No weird artifacts - "Extract[ing] every 4th byte" is no longer necessary to do manually -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432620] Copy and pasting filter mask HSV/HSL Adjustment and Levels makes white pixels black
https://bugs.kde.org/show_bug.cgi?id=432620 Vitamorus changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||vitamorus@gmail.com --- Comment #4 from Vitamorus --- Reproduced in 4.4.1 but resolved in 5.2.6! Seems to have been an issue with bounds not being properly set. When there was something drawn on the mask the copy would have trimmed the bounds to contain only was on there. Presumably a blank/white mask resulted in a copy with zero size bounds. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446223] Can't Paste a Clone Layer
https://bugs.kde.org/show_bug.cgi?id=446223 Vitamorus changed: What|Removed |Added Version|4.4.8 |5.2.6 CC||vitamorus@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431431] Merging to hidden layer discards hidden layer
https://bugs.kde.org/show_bug.cgi?id=431431 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|4.4.1 |5.2.6 --- Comment #8 from Vitamorus --- Re-confirming for 5.2.6. Personally I think I would prefer it if, when trying to merge layers and at least one of them are hidden, there would be a dialog prompting the user what to do (discard hidden layers, unhide and merge, or skip hidden layers). Second best option IMO would be to treat hidden layers as locked by default and leave them untouched in the layer stack. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448240] The window is too high for the Android tablet to see the buttons.
https://bugs.kde.org/show_bug.cgi?id=448240 Vitamorus changed: What|Removed |Added CC|vitamorus@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 497389] New: Unlocking undone merged hidden locked layer raises safe assert
https://bugs.kde.org/show_bug.cgi?id=497389 Bug ID: 497389 Summary: Unlocking undone merged hidden locked layer raises safe assert Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: vitamorus@gmail.com Target Milestone: --- That title is a mess, but I'll explain. While testing Bug 431431 I was playing around with merging hidden layers and managed to raise a safe assert. To reproduce: 1. Open Krita and create a new document 2. Create 3 layers 3. Hide layer 2 and then lock it (in that order!) 4. Select all 3 layers and merge them 5. Undo the merge (Ctrl + Z) 6. Unlock layer 2 7. A dialog with a safe assert should appear reading: "SAFE ASSERT (krita): "m_newPropertyList == other->m_oldPropertyList" in file /builds/graphics/krita/libs/image/commands/kis_node_property_list_command.cpp, line 113" Log output: SESSION: 12 Dec 2024 21:25:21 +0100. Executing /tmp/.mount_krita-wmWfjj/usr/bin/krita Krita Version: 5.3.0-prealpha (git 021e347), Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 15704 -- -- -- -- -- -- -- -- 12 Dec 2024 21:25:21 +0100: Style: fusion. Available styles: Windows, Fusion 12 Dec 2024 21:25:22 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.2.2, at Wed Feb 28 22:46:18 2024 12 Dec 2024 21:25:25 +0100: KisAppimageUpdater: update check finished. Result: 1 Exit status: 0 path: /.../krita-5.3.0-prealpha-021e347922-x86_64.AppImage output: 12 Dec 2024 21:25:27 +0100: Created image "Unnamed", 3200 * 2000 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 1 12 Dec 2024 21:25:38 +0100: SAFE ASSERT (krita): "root->visible()" in file /builds/graphics/krita/libs/image/kis_layer_utils.cpp, line 1118 12 Dec 2024 21:25:40 +0100: SAFE ASSERT (krita): "m_newPropertyList == other->m_oldPropertyList" in file /builds/graphics/krita/libs/image/commands/kis_node_property_list_command.cpp, line 113 KRITA DID NOT CLOSE CORRECTLY -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 497389] Unlocking undone merged hidden locked layer raises safe assert
https://bugs.kde.org/show_bug.cgi?id=497389 Vitamorus changed: What|Removed |Added Latest Commit||git 021e347 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407901] Standard filter blur brush doesn't respond to Pressure/opacity slider
https://bugs.kde.org/show_bug.cgi?id=407901 Vitamorus changed: What|Removed |Added Version|4.2.0-alpha |5.2.6 CC||vitamorus@gmail.com --- Comment #8 from Vitamorus --- Re-confirmed for 5.2.6. Fingers crossed it was an easy fix all along (making filter brushes respond to pen pressure for opacity). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372906] Brush color changes after color picking with a noticeable delay
https://bugs.kde.org/show_bug.cgi?id=372906
Vitamorus changed:
What|Removed |Added
Version|3.0.1.1 |5.2.6
CC||vitamorus@gmail.com
--- Comment #9 from Vitamorus ---
Re-confirmed for 5.2.6.
Like Dmitry said, this is an unfortunate artifact of Krita prioritizing
finishing a heavy ("laggy") brush stroke completely before really processing
any other type of input. Color sampling and beginning a new brush stroke BEFORE
the first one has completely will cause Krita to (partially) skip the color
sampling action.
Thankfully this isn't as problematic anymore since Krita's painting a lot
faster these days than back in 3.0.1.1, but it's still around.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 410675] Artistic color selector gets out of sync in HSV/HSL mode
https://bugs.kde.org/show_bug.cgi?id=410675 Vitamorus changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||vitamorus@gmail.com --- Comment #5 from Vitamorus --- Reproduced in 4.2.5 and resolved in 5.2.6 (has been for some time it seems)! As for the supposed bug tomtomtom mentioned, that seems to be an intentional feature. Per the manual: "The blip shows the position of current foreground color on the wheel (black&white circle) and on the value scale (black&white line). Last selected swatches are outlined" When you use the artistic color selector, the current and last selections will be the same. When you use another color picker or sampler, the outlines of the segments stay where you last put them (for when you want to get back to them) while the circle on the wheel and the line in the value scale represent the current active color. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464447] The first stroke immediately after swapping layers always looks as if drawn with maximum pressure
https://bugs.kde.org/show_bug.cgi?id=464447 Vitamorus changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||vitamorus@gmail.com Version|5.1.5 |5.2.6 --- Comment #1 from Vitamorus --- I can confirm this using 5.2.6 AppImage on Neon (how have I not noticed this until now?). It also happens when moving colors in the Palette docker around, so the hiccup might be related to drag-and-drop actions in general? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362930] bevel and Emboss layer style makes the inside of the shape lighter
https://bugs.kde.org/show_bug.cgi?id=362930 Vitamorus changed: What|Removed |Added CC||vitamorus@gmail.com Version|2.9 |5.2.6 --- Comment #9 from Vitamorus --- Re-confirmed for 5.2.6. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431431] Merging to hidden layer discards hidden layer
https://bugs.kde.org/show_bug.cgi?id=431431 --- Comment #9 from Vitamorus --- Started discussion + poll on KA: https://krita-artists.org/t/poll-what-should-happen-when-merging-hidden-layers/109426 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 496519] Editing handles of mesh gradient raises safe assert
https://bugs.kde.org/show_bug.cgi?id=496519 --- Comment #1 from Vitamorus --- Double checking, the rendering error show up in 5.2.6 but not the safe asserts. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437365] Numbered value scale in artistic color selector does not show numbers
https://bugs.kde.org/show_bug.cgi?id=437365 Vitamorus changed: What|Removed |Added Status|RESOLVED|REPORTED CC||vitamorus@gmail.com Ever confirmed|1 |0 Resolution|FIXED |--- --- Comment #3 from Vitamorus --- Reinold, did you check this on Android (the platform this was reported for)? I just had a friend confirm that this happens on her Android tablet on Krita version 5.2.8. However, this seems to happen at a threshold where the text is too small to read anyway so maybe it's not something to be concerned about. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437365] Numbered value scale in artistic color selector does not show numbers
https://bugs.kde.org/show_bug.cgi?id=437365 Vitamorus changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 496519] Editing handles of mesh gradient raises safe assert
https://bugs.kde.org/show_bug.cgi?id=496519 --- Comment #2 from Vitamorus --- Had a friend test this on 5.2.8 (Android only) and couldn't reproduce the safe assert. It does happen in Krita Plus 5.2.9 pre-alpha. -- You are receiving this mail because: You are watching all bug changes.
