[krita] [Bug 412849] Crash after deleting layers, resizing image and cropping on relatively large file
https://bugs.kde.org/show_bug.cgi?id=412849 Larpon changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Larpon --- Yes, sorry I couldn't provide any more details or crash logs at the time. I'm on Kubuntu 20.04 these days and happily using 5.0 now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406763] Add similar concept to GIMP's "parasites"
https://bugs.kde.org/show_bug.cgi?id=406763 --- Comment #9 from Larpon --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412846] Expose ways to select/deselect nodes in the Layer docker
https://bugs.kde.org/show_bug.cgi?id=412846 --- Comment #4 from Larpon --- I'll try and see, thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412846] Expose ways to select/deselect nodes in the Layer docker
https://bugs.kde.org/show_bug.cgi?id=412846 --- Comment #5 from Larpon --- A function setActiveNodes would also be good -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413088] Changing visibility on multiple layers + calling refreshProjection() is a very slow operation.
https://bugs.kde.org/show_bug.cgi?id=413088 --- Comment #7 from Larpon --- I *think* it's been resolved. I haven't encountered anything since updating to 4.3.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401446] Crash using multiple transform masks with multiple clone layers
https://bugs.kde.org/show_bug.cgi?id=401446 Larpon changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 from Larpon --- I haven't encountered this with 4.3.0 yet. I think this can be closed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399095] Make it possible to add an entry to the palette class directly without constructing a kocolorsetentry
https://bugs.kde.org/show_bug.cgi?id=399095 --- Comment #5 from Larpon --- I remember it was not possible to add colors to palettes from python scripts - and this was part of that problem. So do you happen to know if colors can be added to palettes now somehow? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408236] New: "Select opaque (replace)" is disabled for group layers
https://bugs.kde.org/show_bug.cgi?id=408236 Bug ID: 408236 Summary: "Select opaque (replace)" is disabled for group layers Product: krita Version: 4.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- Created attachment 120515 --> https://bugs.kde.org/attachment.cgi?id=120515&action=edit Diabled menu option example SUMMARY After selection masks has been reworked the "Select opaque" menu entries are now disabled on Group Layers - these where enabled in Krita 4.1.x STEPS TO REPRODUCE (Layers) 1. Select a group layer 2. Right-click 3. See disabled option "Select opaque (replace)" STEPS TO REPRODUCE (Select menu in top bar) 1. Select a group layer 2. Go to "Select" -> "Select opaque" 3. See disabled items in sub-menu OBSERVED RESULT Disabled select opaque functionality EXPECTED RESULT Enabled select opaque functionality SOFTWARE/OS VERSIONS Linux/KDE Plasma: 18.04 ADDITIONAL INFORMATION WORKAROUND Use Ctrl+click on Layer thumbnail in Layers docker -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408256] New: Missing closest color indication in new color palette docker
https://bugs.kde.org/show_bug.cgi?id=408256 Bug ID: 408256 Summary: Missing closest color indication in new color palette docker Product: krita Version: 4.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- SUMMARY In at least Krita version 4.1.x the color palette indicated what color was "closest" match to the current foreground color. This feature seem to be let out in the new Color palette implementation? The indication was done with a border around the color in the palette docker. STEPS TO REPRODUCE 1. Use color selector tool on any layer 2. No color in the palette are raised/highlighted/marked OBSERVED RESULT No highlighting of colors when changing foreground color EXPECTED RESULT Highlight or marking of the color closest to the foreground color (like in Krita 4.1.x) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 18.04 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408256] Missing closest color indication in new color palette docker
https://bugs.kde.org/show_bug.cgi?id=408256 --- Comment #3 from Larpon --- Hi Anna and Boud, Thanks for the workaround - I've completely missed that option. Right now the color gets highlighted as I was missing - but as Boud mentioned in *2 - there was a feature where the fg wouldn't be set - but the highlight would still show around the color in the palette. Thanks both of you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412846] New: Expose ways to select/deselect nodes in the Layer docker
https://bugs.kde.org/show_bug.cgi?id=412846 Bug ID: 412846 Summary: Expose ways to select/deselect nodes in the Layer docker Product: krita Version: 4.2.7 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- SUMMARY I'm working on a python plugin (https://github.com/Larpon/krita-bulk-actions) that can trigger actions/functions on multiple nodes at once based on layer name matching. I'd like to include a way to select and deselect nodes. The reason for this is to have a way to quickly select a group of layers I want to export (currently using "Batch Exporter" from GDQuest but it's useful for all types of operations done on selected layers). Now, I can't find any calls in the API to toggle the selection state of a Node. I've found this with help from @tiar-dg on IRC: https://code.woboq.org/kde/calligra/krita/ui/kis_node_manager.h.html#_ZN14KisNodeManager16setSelectedNodesE5QListI12KisSharedPtrI7KisNodeEE My guess is that we'd also need a setDeselectedNodes or setDeselectedAll() function as well - if not already there somewhere. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412849] New: Crash after deleting layers, resizing image and cropping on relatively large file
https://bugs.kde.org/show_bug.cgi?id=412849 Bug ID: 412849 Summary: Crash after deleting layers, resizing image and cropping on relatively large file Product: krita Version: 4.2.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- SUMMARY 1. Window --- Krita has encountered an internal error: SAFE ASSERT (krita): "!notifier.isInRecursion()" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 294 Please report a bug to developers! Press Ignore to try to continue. Press Abort to see developers information (all unsaved data will be lost) --- 2. Window --- Krita has encountered an internal error: SAFE ASSERT (krita): "m_d->runningShortcut" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 662 Please report a bug to developers! Press Ignore to try to continue. Press Abort to see developers information (all unsaved data will be lost) --- 3. (goes back to 1. and so on ... until you click "abort" instead of "ignore") STEPS TO REPRODUCE 1. Load image of size 3500x2000 2. Removed 10 layers 3. Resized image via menu to twice the size (3500*2) keep aspect 4. Cropped the image to a smaller size 5. Added new layer 6. Started drawing 7. BOOM OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION I have the 20 megabyte file it happened with - but I can't attach it here -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412849] Crash after deleting layers, resizing image and cropping on relatively large file
https://bugs.kde.org/show_bug.cgi?id=412849 Larpon changed: What|Removed |Added Platform|Ubuntu Packages |Appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412849] Crash after deleting layers, resizing image and cropping on relatively large file
https://bugs.kde.org/show_bug.cgi?id=412849 Larpon changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412850] New: Crash when using the Contigous Selection Tool
https://bugs.kde.org/show_bug.cgi?id=412850 Bug ID: 412850 Summary: Crash when using the Contigous Selection Tool Product: krita Version: 4.2.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- SUMMARY 1. Window --- Krita has encountered an internal error: SAFE ASSERT (krita): "boundsRect != KisDefaultBounds().bounds()" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/image/kis_convolution_painter.cc, line 154 Please report a bug to developers! Press Ignore to try to continue. Press Abort to see developers information (all unsaved data will be lost) --- STEPS TO REPRODUCE 1. Load image 2. Added layer 3. Draw outline in solid color 4. Use "contigous selection tool" in middle of drawing 5. CRASH OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION I have the 9 megabyte file it happened with - but I can't attach it here -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412849] Crash after deleting layers, resizing image and cropping on relatively large file
https://bugs.kde.org/show_bug.cgi?id=412849 Larpon changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #1 from Larpon --- Reopened as I thought is was the same bug as https://bugs.kde.org/show_bug.cgi?id=412850 - but the messages aren't the same - so I reopened this as well. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412850] Crash when using the Contigous Selection Tool
https://bugs.kde.org/show_bug.cgi?id=412850 Larpon changed: What|Removed |Added Platform|Other |Appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412850] Crash when using the Contigous Selection Tool
https://bugs.kde.org/show_bug.cgi?id=412850 --- Comment #1 from Larpon --- This doesn't happen in 4.2.6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412849] Crash after deleting layers, resizing image and cropping on relatively large file
https://bugs.kde.org/show_bug.cgi?id=412849 --- Comment #3 from Larpon --- Hi Dmitry! I was using a Wacom Cintiq Companion (1st gen) - so it's using the system installed wacom driver (whatever Kubuntu 18.04 supplies). I haven't had any driver specific problems that I know of with those drivers. It's often happened that strange things occur when working with "big" files or layers in Krita. I've tried forced shutdowns with similar workflows where "big" files with relatively many layers are manipulated, cropped, resized or moved around - after a short while (after slow operations where Krita, I'm guessing, reorganizes stuff) - it's become normal that a crash occurs. So my workflow is usually to just save after a "big" operation and restart Krita (I know, it shouldn't be like that :) ). I keep the word big in quotes because it's relatively slow operations on my machine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413030] New: Filename missing in window title
https://bugs.kde.org/show_bug.cgi?id=413030 Bug ID: 413030 Summary: Filename missing in window title Product: krita Version: 4.2.7-beta1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- SUMMARY The filename of the open/focused document is missing from the window title (on X11 at least) STEPS TO REPRODUCE 1. Open any .kra file 2. See that version number and exe-name in the window title - but no filename OBSERVED RESULT "4.2.7-beta1 (git e9b2584) : — Krita" EXPECTED RESULT "4.2.7-beta1 (git e9b2584) : — Krita" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 / backports KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413088] New: Changing visibility on multiple layers + calling refreshProjection() is a very slow operation.
https://bugs.kde.org/show_bug.cgi?id=413088 Bug ID: 413088 Summary: Changing visibility on multiple layers + calling refreshProjection() is a very slow operation. Product: krita Version: 4.2.7-beta1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- SUMMARY Changing visibility on multiple layers + calling refreshProjection() in a script is a very slow operation. The more layers that are changed the more time the operation takes. It comes to a point where Krita can hang for several seconds. This might/probably also affect other "visual" operations in the API. STEPS TO REPRODUCE 1. Run a script that changes visibility on e.g. 6 layers in a 3000x3000 document 2. Watch the UI hang 3. Layer states are updated OBSERVED RESULT CPU is sweating EXPECTED RESULT CPU not sweating SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413088] Changing visibility on multiple layers + calling refreshProjection() is a very slow operation.
https://bugs.kde.org/show_bug.cgi?id=413088 --- Comment #2 from Larpon --- Created attachment 123375 --> https://bugs.kde.org/attachment.cgi?id=123375&action=edit Can be run in "Scipter" to illustrate the bug -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413088] Changing visibility on multiple layers + calling refreshProjection() is a very slow operation.
https://bugs.kde.org/show_bug.cgi?id=413088 --- Comment #3 from Larpon --- I'm running it via "Scripter" plugin with the ".notes" layer selected in this file: http://1499.dk/tmp/BUG-413088.kra -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406763] New: Add similar concept to GIMP's "parasites"
https://bugs.kde.org/show_bug.cgi?id=406763 Bug ID: 406763 Summary: Add similar concept to GIMP's "parasites" Product: krita Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- The GIMP has a concept called "parasites" in it's scripting API's. Parasites are simple key / value pairs you can attach to many (if not all?) objects accessible via the different scripting API's. This allows for a plugin author to get and set state data on e.g. global, layers, colors, transforms etc. throughout the API. Parasites are then stored and re-loaded with each document (.kra file). So a plugin can load and save data/state between sessions. I've contributed COA Tools support to this plugin https://github.com/GDquest/GDquest-art-tools and thus noticed that the project uses layer names for a similar way to store data/state/meta-data between sessions. I think it's about time to air the idea and to add some kind of key/value system that can follow a documents life-cycle, accessible from the scripting API - before we end up contaminating e.g. Layer names etc. (On a side note I'm also going to suggest adding user facing tag support to layers - giving plugins the opportunity to act on user specified tags) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406764] New: Add tag support to layers
https://bugs.kde.org/show_bug.cgi?id=406764
Bug ID: 406764
Summary: Add tag support to layers
Product: krita
Version: unspecified
Platform: Other
OS: All
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Layer Stack
Assignee: krita-bugs-n...@kde.org
Reporter: dev.lar...@gmail.com
Target Milestone: ---
Created attachment 119555
--> https://bugs.kde.org/attachment.cgi?id=119555&action=edit
Illustrated wish
I'd be fantastic if layers could be tagged (similar to the tags on brushes).
This way we could allow for plugins to act (i.e. do stuff) on specific layers
with specific tags assigned to them.
Tags should be user-facing (maybe via the "Layer Properties" dialog) - giving
both users and plugins the opportunity to assign, read and delete tags).
My specific use-case would be to be able to assign, via tags, what layers
should be switched between visible/invisible when I click a button in my
plugin.
E.g. "All layers with tag: 'alien' should be hidden when I click this button"
This will enable artists to work more efficient on objects that overlap.
I've tried to illustrate in the attachment.
I'd really like a plugin to be able to identify all layers with "{alien}" in
the name and for example switch it's visibility or turn an effect on/off etc.
I hope this could be done without contaminating the layer names.
(also see my suggestion in https://bugs.kde.org/show_bug.cgi?id=406763
regarding layer name contamination)
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 406763] Add similar concept to GIMP's "parasites"
https://bugs.kde.org/show_bug.cgi?id=406763 --- Comment #2 from Larpon --- It's a thing I've used a lot in The GIMP - and are missing in Krita's API. I'm of the understanding that many GIMP plugin authors also use parasites to store state among other things - so I think it will be useful to many other future plugin authors than just me. So to answer your question: It's a specific thing I'm missing :) It only becomes 'architectural' because this concept (parasites) touches, or could touch, many object types. I'm not enough into the codebase to know how big of a change it would be to give all/many/dominant objects this feature. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406763] Add similar concept to GIMP's "parasites"
https://bugs.kde.org/show_bug.cgi?id=406763 --- Comment #3 from Larpon --- ... and don't let the word "parasites" scare you off - it's basically just the ability to store key/value data globally and on prominent object types (e.g. layers, colors, brushes, patterns) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406764] Add tag support to layers
https://bugs.kde.org/show_bug.cgi?id=406764 --- Comment #2 from Larpon --- I believe it does work with using colors. But in the versions I've tried scripting from (4.0 - 4.1.x) There's a few shortcomings of using colors for "tags": 1. They mess with layer organisation (I currently use colors for fast recognizing/pin pointing/navigation or as an indicator of special export) 2. No use or hard to use if you're colorblind (if I understand color blindness correctly) 3. Limited pallette == limited "tags" (can I choose my own colors + add them?) 4. Words make more sense to humans as categories, I believe 5. The colors could change values for some reason between versions - rendering previous color "tags" unusable So yes, layer colors could be used - but has some drawbacks as I see it. Also if special syntax in the layer names become popular we could end up with some plugins that dictates how you name your layers etc. so also preventing bad habits. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406763] Add similar concept to GIMP's "parasites"
https://bugs.kde.org/show_bug.cgi?id=406763 --- Comment #5 from Larpon --- Ouch. So no base objects to implement this on? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411981] New: Node::setCollapsed doesn't collapse group layers visibly
https://bugs.kde.org/show_bug.cgi?id=411981 Bug ID: 411981 Summary: Node::setCollapsed doesn't collapse group layers visibly Product: krita Version: 4.2.6 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- SUMMARY When using the method "setCollapsed()" on the Node type it's not reflected visibly in the Layer tree docker. https://api.kde.org/extragear-api/graphics-apidocs/krita/libs/libkis/html/classNode.html#a0ec780c17a196114303fdce2367fea15 STEPS TO REPRODUCE 1. Find a groupLayer node in the document via the python scripting API 2. call setCollapsed on it OBSERVED RESULT (Group) Layer doesn't change state EXPECTED RESULT (Group) Layer should visibly collapse or open in the layer tree SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 / backports KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406764] Add tag support to layers
https://bugs.kde.org/show_bug.cgi?id=406764 --- Comment #4 from Larpon --- I've made a user land plugin to simulate the behaviour via search strings in layer names: https://github.com/Larpon/krita-bulk-actions -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406764] Add tag support to layers
https://bugs.kde.org/show_bug.cgi?id=406764 --- Comment #6 from Larpon --- Well, maybe the IDs are good enough - but I'm looking for way to identify layers between file loads. Are the layer IDs unique across reloads? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386986] Merge animation capabilities from AnimeEffects
https://bugs.kde.org/show_bug.cgi?id=386986 --- Comment #2 from Larpon --- Agreed. Close it 🙂 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406764] Add tag support to layers
https://bugs.kde.org/show_bug.cgi?id=406764 --- Comment #8 from Larpon --- @Tymond yes of course. I guess this could be implemented as a plugin easily if we had functionality similar to GIMP's parasites. So via parasites on layers we could indeed have tag data stored in these parasites. Parasites is probably a bad name. It should probably be called meta- or simply, user data. But the concept is to allow plugin authors to store and retrieve (at least string) data on each layer which is saved with the project file. It would allow for plugins to store and operate on data across krita sessions, which a layer tagging solution would require. Right now I am personally resorting to base64 encoding in group layer names to store my data along with the document (krita-bulk-actions). Now if there was an official layer tag functionality in krita, plugins could adhere to that API and base functionality off of that. Thus operating on tags already available or sat by the user. If an official layer tagging API was available it could be used by other krita functionality to let the user target specific (tagged) layers to run operations on instead of having to manually select the same X layers everytime you need to apply a filter, color adjust, select from, copy from etc. I'm sure it could be used for much more. Right now I'm using my own plugin to switch multiple layers visibility and also to set opacity for multiple layers. I'm also using it to set the document in different "states" one state is often "export" where one button push allows me to set all the layer values and filters I want on before exporting. I have a similar "working" state set I can switch on and off, and also a "sketch/note" state that shows indications, notes or specific selections for certain areas. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406764] Add tag support to layers
https://bugs.kde.org/show_bug.cgi?id=406764 --- Comment #9 from Larpon --- The common thing all this functionality ( I speak of in the above ) relies on, is tags I right now have to put in special characters in the layer names and store settings for in group layer names. You can see how in my krita-bulk-action plugin on github. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386986] New: [Feature idea] Merge animation capabilities from AnimeEffects
https://bugs.kde.org/show_bug.cgi?id=386986 Bug ID: 386986 Summary: [Feature idea] Merge animation capabilities from AnimeEffects Product: krita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- I stumbled upon AnimeEffects (https://github.com/hidefuku/AnimeEffects) and was really impressed with the animation capabilities. Especially the stable and working Mesh and Bone deformation tools are a rare find in FOSS projects. It's based on Qt5 and C++ so it seem like a good fit. I do know this is not a simple task and might be a complete Kickstarter worth itself - but I thought it'd be worth mentioning as the project seem stable and somewhat active. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401446] New: Crash using multiple transform masks with multiple clone layers
https://bugs.kde.org/show_bug.cgi?id=401446 Bug ID: 401446 Summary: Crash using multiple transform masks with multiple clone layers Product: krita Version: 4.1.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- Crash message: --- Krita has encountered an internal error: SAFE ASSERT (krita): "!m_d->staticCacheValid" in file /home/appimage/workspace/Krita_Stable_Appimage_Build/krita/libs/image/kis_transform_mask.cpp, line 431 Please report a bug to developers! Press Ignore to try to continue. Press Abort to see developers information (all unsaved data will be lost) --- STEPS TO REPRODUCE 1. Cloned ~10 layers of one source layer (no clones of clones) 2. Wrapped them in different groups 3. Applied transform masks to those groups 4. Did a "select opaque" 5. Painted a few strokes OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION git hash: 15583ef -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399095] New: Make it possible to add an entry to the palette class directly without constructing a kocolorsetentry
https://bugs.kde.org/show_bug.cgi?id=399095 Bug ID: 399095 Summary: Make it possible to add an entry to the palette class directly without constructing a kocolorsetentry Product: krita Version: 4.1.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- As in title. Make it possible to add an entry to the palette class directly without constructing a kocolorsetentry -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399100] New: Make it possible to install packages via pip
https://bugs.kde.org/show_bug.cgi?id=399100
Bug ID: 399100
Summary: Make it possible to install packages via pip
Product: krita
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: dev.lar...@gmail.com
Target Milestone: ---
I'd be nice with a way to install packages on-demand from with-in scripts.
Like this
import pip
def install(package):
if hasattr(pip, 'main'):
pip.main(['install', package])
else:
pip._internal.main(['install', package])
...
install('pillow')
Running this code via scripter fails with:
**
locale.Error: unsupported locale setting
In file: /tmp/.mount_krita-ymDKuy/usr/lib/python3.5/locale.py
In function: setlocale at line: 594. Line with error:
return _setlocale(category, locale)
**
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 399100] Make it possible to install packages via pip
https://bugs.kde.org/show_bug.cgi?id=399100 --- Comment #2 from Larpon --- You are right, I completely overlooked that - sorry. As you know I found a way to patch appimages by re-packing them on Linux instead. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399133] New: Python Palette Docker script doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=399133 Bug ID: 399133 Summary: Python Palette Docker script doesn't work anymore Product: krita Version: 4.1.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- Created attachment 115259 --> https://bugs.kde.org/attachment.cgi?id=115259&action=edit Capture of error message The plugin doesn't load anymore. I *think* it was working in earlier versions 4.0.x - but I'm not sure STEPS TO REPRODUCE 1. Enable the "Palette Docker" in Settings -> Configure Krita -> Python Plugin Manager -> [v] Palette Docker 2. See error message (attached) on mouse over -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384587] New: Unable to load .kra file (file was seemingly saved normally)
https://bugs.kde.org/show_bug.cgi?id=384587 Bug ID: 384587 Summary: Unable to load .kra file (file was seemingly saved normally) Product: krita Version: 3.2.1 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com Target Milestone: --- Created attachment 107795 --> https://bugs.kde.org/attachment.cgi?id=107795&action=edit Troublesome file - makes Krita spin up CPU and takes forever to load Attached file makes Krita load forever. The file was saved normally - but Krita crashed between sessions. Same symptoms on these versions: 3.2.1 3.1.4 4.0.0 pre-alpha -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384587] Unable to load .kra file (file was seemingly saved normally)
https://bugs.kde.org/show_bug.cgi?id=384587 --- Comment #2 from Larpon --- Your suspicion about a clonelayer creating a dead-lock seem to be correct. I've tried unzipping the .kra and editing the maindoc.xml. Removing the "pose export" layer block starting on line 270 - and zipping it back up - will let Krita load it again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384587] Unable to load .kra file (file was seemingly saved normally)
https://bugs.kde.org/show_bug.cgi?id=384587 --- Comment #3 from Larpon --- The following "leg r" clone layer block from the attached file seems to be the culprit: -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479
--- Comment #82 from Larpon ---
On my system it seem to be whenever theres "movement" on the screen;
animated icons, youtube playback in chrome makes CPUs sweat, animated fades
between two images in the Picture frame plasmoid, drawing in Krita etc. the
CPU is up 20 - 40%. I've developed a game in Qt which uses a lot of QML
animations but it doesn't do anything to the CPU so it must be a plasma
thing of some sort :/
On 11:57, Sun, 2 Oct 2016 Fabian Vogt via KDE Bugzilla, <
bugzilla_nore...@kde.org> wrote:
> https://bugs.kde.org/show_bug.cgi?id=356479
>
> --- Comment #81 from Fabian Vogt ---
> (In reply to Simone Gaiarin from comment #78)
> > My workaround for the spinning file transfer is to modify the qml code
> and
> > make it not spin. What other "animated task manager (?) icons" are
> causing
> > the problem beside the file transfer spinner?
>
> I don't know, I haven't hit that bug, only the tray icon one with skype.
>
> > I still haven't tried your patch for the system tray icon. Can I just
> > recompile the system tray or does it require to recompile the whole
> plasma?
>
> You only need to rebuild
> %{_libdir}/qt5/plugins/plasma/applets/org.kde.plasma.private.systemtray.so
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #84 from Larpon --- Well video plays fine - at good framerates - but the CPU cores are working absurdly - which makes it feels like plasma is part of it. I'll have a look at top the next time On 15:22, Sun, 2 Oct 2016 Simone Gaiarin via KDE Bugzilla, < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=356479 > > --- Comment #83 from Simone Gaiarin --- > The video lag on chrome may be related to other causes. I had the problem > as > well. > See this: > > https://forum.manjaro.org/t/chrome-chromium-and-html5-video-lags-low-fps/2257/30 > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369666] New: Random crashes when using 'Transform Mask' layer
https://bugs.kde.org/show_bug.cgi?id=369666 Bug ID: 369666 Summary: Random crashes when using 'Transform Mask' layer Product: krita Version: 3.0.1 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: adjustment layers Assignee: krita-bugs-n...@kde.org Reporter: dev.lar...@gmail.com I get crashes when using the 'Transform Mask' layer. It's been in 3.0.1 and 3.0.1.1. Whenever I've applied a few 'Transform Mask' layers to a group layer or paint layer - I then draw a bit - and then come back to either remove the 'Transform Mask' layer or adjust it and then Krita crashes Reproducible: Always Steps to Reproduce: I haven't found precise reproduction steps - I only know it's when using one or more 'Transform Mask' layer. An example: 1. New document in large size e.g.: 3400x2040 2. Make 2 group layers - and paint something on a paint layer in each group 3. Apply the 'Transform Mask' layer to both groups 4. Make paint layer in the root of the document 5. Paint some more on all paint layers 6. Remove one of the 'Transform Mask' layers. 7. Paint some more 8. Adjust one of the 'Transform Mask' layers 9. If Krita is still alive - try applying another 'Transform Mask' layer Doing the above steps or similar crashes Krita after a few times on my setup Actual Results: crash Expected Results: Expected no crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #86 from Larpon --- Popping by again just to say that I haven't got Skype or Spotify on my system -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369666] Random crashes when using 'Transform Mask' layer
https://bugs.kde.org/show_bug.cgi?id=369666 --- Comment #2 from Larpon --- Hmm... I've tried again - this time I could get it to crash the same way two times in a row. I've caputured a video and attached the file from the video: http://dropcanvas.com/5reqx I'm fiddling around with the Transform Mask layer and then switch to the Move tool rather quick. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362881] Crash when applying transform
https://bugs.kde.org/show_bug.cgi?id=362881 Larpon changed: What|Removed |Added CC||dev.lar...@gmail.com --- Comment #8 from Larpon --- I'm getting crashes almost every time I use the 'Transform Mask' layer type with lastest 3.0.1 (stable) on Kubuntu 16.04 using the appimage. Might be related? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 Larpon changed: What|Removed |Added CC||dev.lar...@gmail.com --- Comment #67 from Larpon --- I dont' think it necessarily have anything to do with animated icons in the tray. While I was working on the new Picture frame plasmoid I've seen the exact same symptoms when using long running QML animations (I used one for showing a count down in the widget which animated all the time) - so I had to remove it. I think it's related to Plasma in some layer just above Qt (maybe Plasma controls screen update timing?) - I have a multi monitor setup BTW -- You are receiving this mail because: You are watching all bug changes.
