[krita] [Bug 484029] The display of the krita.org sitemap in the browser is just a list of text
https://bugs.kde.org/show_bug.cgi?id=484029 Scott Petrovic changed: What|Removed |Added Resolution|WAITINGFORINFO |INTENTIONAL Status|NEEDSINFO |RESOLVED --- Comment #2 from Scott Petrovic --- We can leave it for now. Since our URL format changed with all of our historical posts for the new site, this XML file helps web crawlers like google pick up all of the new pages. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482427] Clicking Donate Banner on Open opens/redirects to "404 Not Found"
https://bugs.kde.org/show_bug.cgi?id=482427 Scott Petrovic changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Scott Petrovic --- Closing ticket. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482427] Clicking Donate Banner on Open opens/redirects to "404 Not Found"
https://bugs.kde.org/show_bug.cgi?id=482427 --- Comment #2 from Scott Petrovic --- Just added a redirect until we can update the welcome screen URLs to the new location -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481548] After switching to new Hugo based website, Welcome Page News section is not fetching non-English news properly
https://bugs.kde.org/show_bug.cgi?id=481548 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481548] After switching to new Hugo based website, Welcome Page News section is not fetching non-English news properly
https://bugs.kde.org/show_bug.cgi?id=481548 --- Comment #4 from Scott Petrovic --- Yes. I think they way it works now is because of how the new website logic is showing posts - and that is carrying through to the application. 1. English - Always just shows English of course 2. Chinese - Tries to get chinese news, but will show English post if it is not translated Now if you are in the Krita application and select both English and Chinese, There will be a lot of duplicate English posts as the Chinese language also shows English...in addition to the English posts. Chinese does not just show Chinese news with the new system. That was a recent change that was requested. We might not need to have multiple languages selected in the Krita application now as it shows all the posts. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481548] After switching to new Hugo based website, Welcome Page News section is not fetching non-English news properly
https://bugs.kde.org/show_bug.cgi?id=481548 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- I think we will need some more discussion on this. This was specifically requested for me to change how krita.org shows news post. The English news posts should show in the case that there is no translated language. The idea was that Krita is still doing active things...even if there is no translated news post. The original discussion was around krita.org, but we didn't think about how this would affect how the news would appear on the Krita application. Once we decide what to do, we can make whatever changes. -- 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 --- Comment #4 from Scott Petrovic --- The original poster was having some weird error updating this ticket. This was the info I grabbed from the krita-artists.org post Device: HUAWEI MatePad 11 (DBY-W09) Display Information Number of screens: 1 Screen: 0 Name: Depth: 32 Scale: 2.9134 Resolution in pixels: 879x549 Manufacturer: Model: Refresh Rate: 60 Notice: “Resolution in pixels” error is displayed after enabling “Enable Hi-DPI support”. The real “Resolution in pixels” is 1920x1200. -- 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 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 CC||scottpetro...@gmail.com Status|REPORTED|CONFIRMED --- Comment #3 from Scott Petrovic --- What screen size is this tablet so we know what we are dealing with. The "Create new" window is pretty small by my screenshot (644 x 567). Is this tablet. The asian characters are a bit larger than roman characters, so their dialog size might be a bit bigger. Whatever we do, we need to figure out a minimum screen size we want to support. Then we can figure out how to modify the UI to be able to handle smaller screen sizes better. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446783] Transform Options Panel not sizing correctly; 5.0.0-beta5 (git 783e051)
https://bugs.kde.org/show_bug.cgi?id=446783 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #7 from Scott Petrovic --- I think we are going to have to look at the UI for the transform tool options. There are a TON of tool options that exist for transforming The UI just isn't handing all these options well when the width is reduced. We might need a bit of a discussion on prioritizing and condensing the various options to fit the space better. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442700] New: Feature request: Add more formats for vector library
https://bugs.kde.org/show_bug.cgi?id=442700 Bug ID: 442700 Summary: Feature request: Add more formats for vector library Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: scottpetro...@gmail.com Target Milestone: --- I was watching a Youtuber and one of the ideas they had was to add the ability to have an image library where they can drag items onto the canvas. https://youtu.be/DbfCOJCl5QM?t=399 You can currently do this with the vector library in general, but their use case revolved around animation which vector files do not support. The use case that was presented was having a bunch of mouth shapes that they can drag on to the canvas as they need them. Solution #1: One idea would be to expand the vector library to include more image formats than SVG. It would be neat if something like PNGs could also be supported. This would obviously take some planning as right now the vector library docker reads an SVG file to get all the elements in the collection. Solution #2 Maybe we don't need to worry about this feature...and direct people to the Photobash plugin where they can drag and drop images on their canvas that is being added to Krita 5.0. If we do this approach, we probably could update our documentation to direct people to use that if they want to use image libraries with JPG, PNG, etc. https://www.youtube.com/watch?v=QX9jwhfpB_8 - new plugin https://docs.krita.org/en/reference_manual/dockers/vector_library.html?highlight=vector%20library - documentation page to update -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397203] Gradients don't save or update
https://bugs.kde.org/show_bug.cgi?id=397203 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- I am having a different issues with gradients when doing any updates. If there is any change done, the gradient saves. The problem is that it creates a new "version" of the gradient which isn't managed correctly. For example if I edit the same gradient 3 times, I will have 3 new gradients appear at the bottom of the gradient chooser. There must be something not being managed correctly with what gradient appears when it has multiple versions. tested on krita master build with commit 46f87d1e088b2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432027] [Request] Better distinction between selected and unselected document tabs
https://bugs.kde.org/show_bug.cgi?id=432027 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Scott Petrovic --- Re-opening this. We had to revert the fix. There were quite a few problems that were created with the previous approach. We will need to rethink how the solution is done. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432027] [Request] Better distinction between selected and unselected document tabs
https://bugs.kde.org/show_bug.cgi?id=432027 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #3 from Scott Petrovic --- Created attachment 136267 --> https://bugs.kde.org/attachment.cgi?id=136267=edit new tab display idea I attached a potential way this could look. Not sure if this display is closer to what you were thinking. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417363] Show the brush preset buttons in the toolbar as inactive when the current tool doesn't support editing brush presets.
https://bugs.kde.org/show_bug.cgi?id=417363 --- Comment #7 from Scott Petrovic --- I think we need to figure out a solution before any work could potentially be done. By assigning it to me I am guessing your goal is we are going to have a discussion in the ticket about what to do. This is a brush preset editor that isn't limited to a currently selected brush. You can change brushes and edit any brush from this window. Are we wanting to disable the editor completely depending on what is the active tool? I think just making it not flat again is not a good solution. There needs to be something. Is this really a problem that needs to be solved? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427689] Add high resolution logo on krita.org
https://bugs.kde.org/show_bug.cgi?id=427689 Scott Petrovic changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Scott Petrovic --- I just update the logo. It is 2x the size with what it was before. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397172] Export size during export
https://bugs.kde.org/show_bug.cgi?id=397172 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #2 from Scott Petrovic --- *** Bug 390343 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390343] Wishlist: Warning when saving a file that has its file size reduced by 50% or more
https://bugs.kde.org/show_bug.cgi?id=390343 Scott Petrovic changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Scott Petrovic --- Yes. I think that would take care of it for this use case. I will just close this ticket. I think I can do that since I created it. *** This bug has been marked as a duplicate of bug 397172 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425910] tiltablle symetry
https://bugs.kde.org/show_bug.cgi?id=425910 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Scott Petrovic --- The multi-brush tool is currently the way if you wan to add additional functionality to the symmetry mode. You can change the rotation axis with that tool. There are a number of options on the multi-brush tool, so I don't know where we draw the line between what that tool does...and what the symmetry mode does. -- 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 #6 from Scott Petrovic --- You can add entries to palettes this way https://api.kde.org/appscomplete-api/krita-apidocs/libs/libkis/html/classPalette.html The GUI version to see the palette is here https://api.kde.org/appscomplete-api/krita-apidocs/libs/libkis/html/classPaletteView.html -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425066] Python Document.modified() flag is NOT set in edit operations.
https://bugs.kde.org/show_bug.cgi?id=425066 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||scottpetro...@gmail.com Severity|normal |minor --- Comment #1 from Scott Petrovic --- I think the work here is going to be adding a few more areas that mark the document as modified. It looks like these areas do not change the "isModified" status. This is python code, but we probably can update the C++ code to set the isModified flag when these things happen... doc.setDocumentInfo(doc.documentInfo() + "\n") doc.setFramesPerSecond(int(doc.framesPerSecond() + 1)) doc.setFullClipRangeStartTime(doc.fullClipRangeStartTime() + 1) doc.setFullClipRangeEndTime(doc.fullClipRangeEndTime() + 1) doc.setFileName(doc.fileName() + ".ILBM") doc.setName(doc.name()[::-1]) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425060] Chronological error in Documents section of Krita scripting school
https://bugs.kde.org/show_bug.cgi?id=425060 Scott Petrovic changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #1 from Scott Petrovic --- Thanks for the report. I just updated that page a bit with updated instructions. I had a feeling there were going to be things like this that came up. I originally combined the layers and document explanation in one lesson. Then separated them out into their own topics as wrote more. Thanks for the feedback. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425060] Chronological error in Documents section of Krita scripting school
https://bugs.kde.org/show_bug.cgi?id=425060 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 CC||scottpetro...@gmail.com Assignee|krita-bugs-n...@kde.org |scottpetro...@gmail.com Status|REPORTED|ASSIGNED -- 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 Scott Petrovic changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from Scott Petrovic --- This might have been fixed, or this might not be the case any more since you do not need a kocolorsetentry to add things to a palette. If there is still any issues, please open up another ticket and we can discuss. -- 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 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #2 from Scott Petrovic --- Is this still valid? With the palette class, it seems you only need to provide a Swatch object and a group string. https://api.kde.org/appscomplete-api/krita-apidocs/libs/libkis/html/classPalette.html#aef8a606c04b86c08ec7f0583a9c9ffea Maybe I just don't understand this -- or maybe it was fixed at some point. I am not seeing kocolorset much when adding entries. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419207] Document Krita actions for Python plugins
https://bugs.kde.org/show_bug.cgi?id=419207 Scott Petrovic changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Scott Petrovic --- I am going to close this for now. You can see all the actions and search them from the scripting site now ... https://scripting.krita.org/action-dictionary If anything else comes up we can make a new ticket. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419093] call to Node.mergeDown() exits krita
https://bugs.kde.org/show_bug.cgi?id=419093 Scott Petrovic 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 421844] setResolution, setXRes, setYRes, scaleImage not working
https://bugs.kde.org/show_bug.cgi?id=421844 Scott Petrovic changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Scott Petrovic --- Alright. We can close this for now. If something else pops up we can make a new ticket. There has been quite a few fixes happening in the past couple months, so maybe it got fixed with something else. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419093] call to Node.mergeDown() exits krita
https://bugs.kde.org/show_bug.cgi?id=419093 --- Comment #5 from Scott Petrovic --- The point I was trying to make is there is something going on with "children[1]" in your script that is giving it issues. The mergeDown() is working in my script, so there must be some difference with how your script is set up that is giving it issues. There could also be something with the "setChildNodes" that is not being set correctly that is causing the mergeDown to fail. We just need to figure out what causes the situation where it fails. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424192] Cannot pass a filter configuration to a python Filter
https://bugs.kde.org/show_bug.cgi?id=424192 --- Comment #4 from Scott Petrovic --- We can probably still close this ticket, but I would be interested to know how to set values in the config that are CDATA. For example the halftone filter XML looks like this. true 8 false 45 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424192] Cannot pass a filter configuration to a python Filter
https://bugs.kde.org/show_bug.cgi?id=424192
Scott Petrovic changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #3 from Scott Petrovic ---
After looking at another script...I think this does actually work and this bug
might be invalid. Changing the properties and running it again changes the
effect of the filter. This seems to work for me in scripter...
from krita import *
#create document to work with
newDocument = Krita.instance().createDocument(500, 500, "Document name",
"RGBA", "U8", "", 300.0)
Krita.instance().activeWindow().addView(newDocument) # shows it in the
application
# make active node layer opacity 100%
activeNode = newDocument.activeNode()
activeNode.setOpacity(255)
# fill with foreground color that has saturation
Krita.instance().action("fill_selection_foreground_color").trigger();
newDocument.refreshProjection()
# see all available filters
# print(Krita.instance().filters())
randomNoiseFilter = Krita.instance().filter("noise")
config = randomNoiseFilter.configuration()
config.setProperty("level", 100)
config.setProperty("opacity", 99)
randomNoiseFilter.setConfiguration(config)
randomNoiseFilter.apply(activeNode, 0, 0, newDocument.width(),
newDocument.height())
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 405194] Python-Plugin Palette Docker doesn't load: KisSwatch not supported
https://bugs.kde.org/show_bug.cgi?id=405194 Scott Petrovic changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO CC||scottpetro...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from Scott Petrovic --- I am going to motion that we close this. The gsoc palette docker is pretty good, and this plugin has not been fixed in over a year. If we need to bring it back for some reason we can make a new ticket. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419207] Document Krita actions for Python plugins
https://bugs.kde.org/show_bug.cgi?id=419207 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||scottpetro...@gmail.com Ever confirmed|0 |1 --- Comment #3 from Scott Petrovic --- There is a new Krita scripting site in the works that is almost launched. There is an action dictionary where you can search all the actions that are available. I think once that site goes live we can close this ticket. -- 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 Scott Petrovic changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |NEEDSINFO CC||scottpetro...@gmail.com --- Comment #5 from Scott Petrovic --- Can someone check this out again with the master branch? I made a document at 3000x3000. I made 6 layers and filled them with content. I ran the script above. It took a fraction of a second to toggle the visibility. Maybe something with the node generation was fixed since this was filed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416921] python copy paste selection - Paste issue (not paste action)
https://bugs.kde.org/show_bug.cgi?id=416921 Scott Petrovic changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||scottpetro...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #6 from Scott Petrovic --- This was written a little while ago, but I looked at it briefly. The way the paste() works right now, it requires a selection. When you do the deselect action in your code snippet, you are making it so the paste operation doesn't work. See this code. https://api.kde.org/appscomplete-api/krita-apidocs/libs/libkis/html/Selection_8cpp_source.html#l00177 If there is no selection, the paste isn't going to work. The way it works otherwise is that it will truncate some of your copied content depending on what you put fot he x and y position. My recommendation is probably just not to use the paste(). It is probably better to just use the paste action. You can move it around as needed, then merge down to a below layer if it needs to be on another layer. If there are coding questions like this, we also have a new krita-artists website that you can post questions to (https://krita-artists.org/). There is a good community of developers on there to help with scripting questions like this too. I am going to close this for now. If there is something else that comes up we can make a new ticket. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421844] setResolution, setXRes, setYRes, scaleImage not working
https://bugs.kde.org/show_bug.cgi?id=421844 Scott Petrovic changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||scottpetro...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Scott Petrovic --- I just tried the setResolution(), which seems to work for me. Maybe it is a specific issue for Macs. See if this works. For Python stuff, we can probably use Krita artists to start off any issues. That will probably get to the root of the issue, or if it is just related to how it is scripted. from krita import * # create document and show in view doc = Krita.instance().createDocument(1280, 1024, "Document name", "RGBA", "U8", "", 300.0) view = Krita.instance().activeWindow().addView(doc) # shows it in the application window = Application.activeWindow() doc.setResolution(123) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419093] call to Node.mergeDown() exits krita
https://bugs.kde.org/show_bug.cgi?id=419093
Scott Petrovic changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
CC||scottpetro...@gmail.com
Resolution|--- |WAITINGFORINFO
--- Comment #3 from Scott Petrovic ---
There might need to be some more digging with this. There are a lot of
different things going on with the script. I don't know if it is the
mergeDown() that is giving issues. I am running this script that merges a layer
down and it seems to work ok...
from krita import *
# create document and show in view
doc = Krita.instance().createDocument(1280, 1024, "Document name", "RGBA",
"U8", "", 300.0)
view = Krita.instance().activeWindow().addView(doc) # shows it in the
application
window = Application.activeWindow()
# create nodes and add it to the layers stack
paintLayer = doc.createNode("Background1", "paintlayer")
paintLayerTwo = doc.createNode("Background2", "paintlayer")
root = doc.rootNode()
root.addChildNode(paintLayer, None)
root.addChildNode(paintLayerTwo, None)
# merge the top layer down
paintLayerTwo.mergeDown()
--
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 Scott Petrovic changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||scottpetro...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from Scott Petrovic --- The only way I see right now to select nodes is through the document class see "setActiveNode" https://api.kde.org/appscomplete-api/krita-apidocs/libs/libkis/html/classDocument.html It doesn't look like there is a way to select multiple nodes at once. Right now you have to iterate over the nodes to do things with all of them. de-selecting might be a bit tricky since you must have at least one layer selection. For now it might be better to just set your active selection again if there are changes. We might be able to add a function like this... setActiveNodes(QList) where you could change the active selection to multiple nodes at one time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393464] [API] Add api for closing view and for setting a view document.
https://bugs.kde.org/show_bug.cgi?id=393464
Scott Petrovic changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED|NEEDSINFO
--- Comment #2 from Scott Petrovic ---
This ticket was written a while ago, so apologies for this taking a while to
respond to. We might need a bit more information. This is currently how you set
a view document. Maybe this didn't exist when this bug was created.
newDocument = Krita.instance().createDocument(1280, 1024, "Document name",
"RGBA", "U8", "", 300.0)
Krita.instance().activeWindow().addView(newDocument) # shows it in the
application
The only way I know how to close the view is by closing the file from an
action...
Krita.instance().action('file_close').trigger()
Here is the current API that might help a little
https://api.kde.org/appscomplete-api/krita-apidocs/libs/libkis/html/classWindow.html
For now I going to set to Needs Info and we can figure out what to do next.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 424192] Cannot pass a filter configuration to a python Filter
https://bugs.kde.org/show_bug.cgi?id=424192 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #2 from Scott Petrovic --- The filter configuration seems to want a QDomElement (which is XML). We can either make someone create a QDomElement in Python and send that in to set the filter configuration. Or add an internal conversion helper function to InfoObject that converts it to XML. I would personally pick QDomElement since that is already available in PyQt. Also less code we might have to maintain with an InfoObject converter. where the filter configuration is being set in Python https://invent.kde.org/graphics/krita/-/blob/master/libs/libkis/Filter.cpp#L105 filter configuration seems to store settings in XML format https://invent.kde.org/graphics/krita/-/blob/master/libs/image/filter/kis_filter_configuration.cc#L117 A couple filter configurations Oil Paint filter XML example - 1 30 Edge Detection Sobel XML example -- 1.85 true false 1.85 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422949] master: python resources() function is broken
https://bugs.kde.org/show_bug.cgi?id=422949 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- "preset" is not a valid resource type which is why it is returning empty. It is a bit tricky to figure out what is available. I am working on a scripting site and have a page that show the current state of using resourcesin Krita 5.0. the site isn't live yet, but you can see the code here... https://invent.kde.org/scottpetrovic/krita-scripting-pro-website/-/blob/master/src/lessons/LessonResources.jsx#L8 You can see what is working. There are still some resource types though that are not done yet...but the resources are being done built yet either. We can close this once 5.0 is ready to test more and all the resource types are implemented. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424515] Notifier windowIsBeingCreated signal not wrapped correctly for Python
https://bugs.kde.org/show_bug.cgi?id=424515 Scott Petrovic changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424515] Notifier windowIsBeingCreated signal not wrapped correctly for Python
https://bugs.kde.org/show_bug.cgi?id=424515 --- Comment #3 from Scott Petrovic --- https://invent.kde.org/graphics/krita/-/merge_requests/437 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424515] Notifier windowIsBeingCreated signal not wrapped correctly for Python
https://bugs.kde.org/show_bug.cgi?id=424515 --- Comment #2 from Scott Petrovic --- I have a PR out to fix this. I also added a new Notifier to tell us when the main window can actually be referenced. You can see the sample extension I wrote to test this out in the PR. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424515] Notifier windowIsBeingCreated signal not wrapped correctly for Python
https://bugs.kde.org/show_bug.cgi?id=424515 Scott Petrovic changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424515] Notifier windowIsBeingCreated signal not wrapped correctly for Python
https://bugs.kde.org/show_bug.cgi?id=424515 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- Yes. I can verify. I started looking at this a bit ago with adding a new python API and noticed the SIP was not named right. I imagine it was renamed while it was being developed and the SIP file was just not updated. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423341] Add menu manipulation to Python API
https://bugs.kde.org/show_bug.cgi?id=423341 Scott Petrovic changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #7 from Scott Petrovic --- Alright. I am going to mark this as closed since this ticket was about manipulating the menu. Outside of this ticket I can look into the Extensions API and what is going on with that. I don't know exactly how that setup() call is working, so there might not be something wrong with it -- or it just isn't clear what it is actually doing. Adding a signal when the window is created might be a solution that is more general. I can look into adding that. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423341] Add menu manipulation to Python API
https://bugs.kde.org/show_bug.cgi?id=423341 Scott Petrovic changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from Scott Petrovic --- Is this still an issue, or did that last code snippet help to do whatever you were trying to do? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423717] Feature request : Introduce a Blend Modes Context Menu for the paintbrush tool
https://bugs.kde.org/show_bug.cgi?id=423717 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- We would have to discuss this more. The blending mode for the brush is already visible on the toolbar and can be changed at any time. Since it is always there, you don't even have to remember a shortcut like Shift + Right click. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423341] Add menu manipulation to Python API
https://bugs.kde.org/show_bug.cgi?id=423341
Scott Petrovic changed:
What|Removed |Added
CC||scottpetro...@gmail.com
--- Comment #3 from Scott Petrovic ---
I am not sure if this helps, but adding actions to menus to do something. This
seems to work for something very simple.
from PyQt5.QtWidgets import (QWidget, QAction)
import krita
# connection methods
def close_application():
print("whoo so custom!!!")
#create an action that does stuff
extractAction = QAction(" TO THE CHOPPAH!!!")
extractAction.setShortcut("Ctrl+Q")
extractAction.setStatusTip('Leave The App')
extractAction.triggered.connect(close_application)
# Create menu off main menu and add a new action to it
main_menu = Krita.instance().activeWindow().qwindow().menuBar()
custom_menu = main_menu.addMenu("Special Actions Menu")
custom_menu.addAction(extractAction) # how to get items/actions in a menu
You are right thought that each new window in Krita is isolated...so the menu
isn't on new windows. If you look in the pykrita folder at some of the
pre-installed Python scripts, they have a "canvasChanged" method that signals
when the document changes. You might be able to do something with that.
I made a little docker plugin that handles these document changed events if
that helps at all for reference...
https://invent.kde.org/scottpetrovic/krita-scratchpad-docker/-/blob/master/scratchpad/scratchpad.py#L201
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 421111] Every time i load it up it gives me a blank screen, just pure black. I started to randomly click around and manage to find report the bug.
https://bugs.kde.org/show_bug.cgi?id=42 Scott Petrovic changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Scott Petrovic --- Can you provide some more system information or a screenshot. Can you see menu items. Have you ever loaded Krita before. It is hard to tell if your issue is either a bad configuration file, or something odd with your graphics card -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421111] Every time i load it up it gives me a blank screen, just pure black. I started to randomly click around and manage to find report the bug.
https://bugs.kde.org/show_bug.cgi?id=42 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- Created attachment 128234 --> https://bugs.kde.org/attachment.cgi?id=128234=edit Where system information is -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421142] Gamut Mask not resizing
https://bugs.kde.org/show_bug.cgi?id=421142 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||scottpetro...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Scott Petrovic --- I am confirming. There is something definitely going on with the gamut masks and how they are applied with similar to the screenshot supplied. I am on the Windows nightly from April 29 (git 8ef9e6f) The issue is also affecting the advanced color selector and how gamut masks are applied to it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421084] t variable is reasigned in kis_color_selector.cpp
https://bugs.kde.org/show_bug.cgi?id=421084 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- Usually for code changes, there are not done in bugzilla. We have a different process for changing code through our GitLab instance. Usually for bugzilla, the important thing is having reprodicible steps to get a bug. These seem more like code refactorings. https://invent.kde.org/kde/krita It looks like you have already created a fork. Could you just make the fixes and do Pull requests for these fixes? https://invent.kde.org/qarmin/krita That would help us out a lot. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419321] Search box on docs.krita.org does not work with Chinese search terms
https://bugs.kde.org/show_bug.cgi?id=419321 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||scottpetro...@gmail.com --- Comment #3 from Scott Petrovic --- I wonder what version we are building the docs site with. It does seem like in late 2017 there was a fix to Sphinx that would get this working? https://github.com/sphinx-doc/sphinx/pull/4171/commits/44489029776b587ac1494df31d382cf8e595f2fa Maybe we just need to use a newer version of Sphinx for the build -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415669] Vanishing Point assistant, angle density slider has not-working up/down controls.
https://bugs.kde.org/show_bug.cgi?id=415669 Scott Petrovic changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/db1cc49ba2f4d4 ||f7287e852a6c4ec3d5922d5d4c --- Comment #3 from Scott Petrovic --- Git commit db1cc49ba2f4d4f7287e852a6c4ec3d5922d5d4c by Scott Petrovic. Committed on 26/03/2020 at 15:28. Pushed by scottpetrovic into branch 'master'. Change cursor to pointer on up and down arrow for sliderbox input Also fixed a couple sliders that had non-working up and down arrows M +13 -1libs/widgetutils/kis_slider_spin_box.cpp M +1-1plugins/assistants/Assistants/kis_assistant_tool.cc M +1-1plugins/tools/basictools/kis_tool_multihand.cpp https://invent.kde.org/kde/krita/commit/db1cc49ba2f4d4f7287e852a6c4ec3d5922d5d4c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374543] Replace docker titles with icons
https://bugs.kde.org/show_bug.cgi?id=374543 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #5 from Scott Petrovic --- I am not sure what problem this is even solving. It seems this is just going to make the user interface take up more space for no gain. Maybe this is more about when you have multiple tabs in a docker area? If you had an icon for a tab instead of text, you could put more tabs in a section. They quickly get hard to read if you have 3 or more tab sections in a docker area -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409941] The docker listing is not sorted alphabetically, this makes it hard to search
https://bugs.kde.org/show_bug.cgi?id=409941 Scott Petrovic changed: What|Removed |Added Assignee|scottpetro...@gmail.com |krita-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409941] The docker listing is not sorted alphabetically, this makes it hard to search
https://bugs.kde.org/show_bug.cgi?id=409941 --- Comment #6 from Scott Petrovic --- Starting to look at this a bit more...I don't know if we even want to be showing the dockers all here. We already have another way to see all the dockers that is only an extra click away (which is already alphabetized. This right click area probably should be used for something better than just showing the docker list again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409941] The docker listing is not sorted alphabetically, this makes it hard to search
https://bugs.kde.org/show_bug.cgi?id=409941 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com Assignee|krita-bugs-n...@kde.org |scottpetro...@gmail.com --- Comment #5 from Scott Petrovic --- I am going to take a look at this...and see if I can come up with a patch. Just taking a quick peek at the code...I think might be pretty simple. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376889] "Show in Timeline" : layers should inherit their parents for this option
https://bugs.kde.org/show_bug.cgi?id=376889 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #2 from Scott Petrovic --- It sounds like the feature request is to have a "toggle all". Maybe if we do this for group layers, we need a better name for it like "Show all in timeline" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413726] 'Show Painting Assistants', 'Show Assistant Previews', 'Show Reference Images' are not disabled after re-opening krita or document again.
https://bugs.kde.org/show_bug.cgi?id=413726 --- Comment #8 from Scott Petrovic --- Alright. I am going to confirm this then and change the title of this report so it is a bit more clear for a developer to know what to do. Thanks for the report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413726] 'Show Painting Assistants', 'Show Assistant Previews', 'Show Reference Images' state are not saved to KRA file
https://bugs.kde.org/show_bug.cgi?id=413726 Scott Petrovic changed: What|Removed |Added Summary|'Show Painting Assistants', |'Show Painting Assistants', |'Show Assistant Previews', |'Show Assistant Previews', |'Show Reference Images' are |'Show Reference Images' |not disabled after |state are not saved to KRA |re-opening krita or |file |document again. | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413601] Assert/crash with Magnetic Selection tool
https://bugs.kde.org/show_bug.cgi?id=413601
--- Comment #2 from Scott Petrovic ---
Here is a separate crash that is happening with a back trace...
Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
QVector::operator= (other=..., this=0x6175dfe0)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:78
78 { QVector moved(std::move(other)); swap(moved); return *this; }
(gdb) bt
#0 0x7fffe4155981 in QVector::operator=(QVector&&)
(other=..., this=0x6175dfe0)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:78
#1 0x7fffe4155981 in KisToolSelectMagnetic::updateSelectedAnchor()
(this=0x574d3a60)
at
/home/scott/git/krita/src/plugins/tools/selectiontools/KisToolSelectMagnetic.cc:416
#2 0x7fffe41599fd in
KisToolSelectMagnetic::endPrimaryAction(KoPointerEvent*)
(this=0x574d3a60, event=0x7fffcd40)
at
/home/scott/git/krita/src/plugins/tools/selectiontools/KisToolSelectMagnetic.cc:321
#3 0x76d25f84 in
KisToolProxy::forwardToTool(KisToolProxy::ActionState, KisTool::ToolAction,
QEvent*, QPointF const&)
(this=, state=KisToolProxy::END, action=KisTool::Primary,
event=0x7fffd490, docPoint=...) at
/home/scott/git/krita/src/libs/ui/canvas/kis_tool_proxy.cpp:202
#4 0x76d260e0 in KisToolProxy::forwardEvent(KisToolProxy::ActionState,
KisTool::ToolAction, QEvent*, QEvent*)
(this=0x60b39fa0, state=state@entry=KisToolProxy::END,
action=action@entry=KisTool::Primary, event=event@entry=0x7fffd490,
originalEvent=originalEvent@entry=0x7fffd490)
at /home/scott/git/krita/src/libs/ui/canvas/kis_tool_proxy.cpp:132
#5 0x7703d60d in KisToolInvocationAction::end(QEvent*)
(this=0x5f0ee820, event=0x7fffd490) at
/usr/include/c++/9/bits/atomic_base.h:413
#6 0x770482a7 in
KisShortcutMatcher::tryEndRunningShortcut(Qt::MouseButton, QEvent*)
(this=this@entry=0x5f023620, button=,
event=event@entry=0x7fffd490)
at /home/scott/git/krita/src/libs/ui/input/kis_shortcut_matcher.cpp:679
#7 0x77049516 in KisShortcutMatcher::buttonReleased(Qt::MouseButton,
QEvent*)
(this=0x5f023620, button=,
event=event@entry=0x7fffd490)
at /home/scott/git/krita/src/libs/ui/input/kis_shortcut_matcher.cpp:296
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 413601] Assert/crash with Magnetic Selection tool
https://bugs.kde.org/show_bug.cgi?id=413601 --- Comment #1 from Scott Petrovic --- Here is another more detailed back trace. This might be a different crash than the first one... Thread 1 "krita" received signal SIGSEGV, Segmentation fault. __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:540 540 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: No such file or directory. (gdb) bt #0 0x7463af3d in __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:540 #1 0x7fffe4155c51 in memmove (__len=, __src=, __dest=) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:40 #2 0x7fffe4155c51 in QVector >::insert(QTypedArrayData >::iterator, int, QVector const&) (t=..., n=1, before=..., this=0x574d61b0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:755 #3 0x7fffe4155c51 in QVector >::insert(int, QVector const&) (t=..., i=, this=0x574d61b0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:442 #4 0x7fffe4155c51 in KisToolSelectMagnetic::beginPrimaryDoubleClickAction(KoPointerEvent*) (this=0x574d6060, event=) at /home/scott/git/krita/src/plugins/tools/selectiontools/KisToolSelectMagnetic.cc:281 #5 0x76d2600e in KisToolProxy::forwardToTool(KisToolProxy::ActionState, KisTool::ToolAction, QEvent*, QPointF const&) (this=, state=KisToolProxy::BEGIN, action=KisTool::Primary, event=0x7fffd490, docPoint=...) at /home/scott/git/krita/src/libs/ui/canvas/kis_tool_proxy.cpp:181 #6 0x76d260e0 in KisToolProxy::forwardEvent(KisToolProxy::ActionState, KisTool::ToolAction, QEvent*, QEvent*) (this=0x5a175df0, state=state@entry=KisToolProxy::BEGIN, action=action@entry=KisTool::Primary, event=event@entry=0x7fffd490, originalEvent=originalEvent@entry=0x7fffd490) at /home/scott/git/krita/src/libs/ui/canvas/kis_tool_proxy.cpp:132 #7 0x7703cf60 in KisToolInvocationAction::begin(int, QEvent*) (this=this@entry=0x5f0427c0, shortcut=, event=event@entry=0x7fffd490) at /usr/include/c++/9/bits/atomic_base.h:413 #8 0x77048c46 in KisShortcutMatcher::tryRunReadyShortcut(Qt::MouseButton, QEvent*) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413726] 'Show Painting Assistants', 'Show Assistant Previews', 'Show Reference Images' are not disabled after re-opening krita or document again.
https://bugs.kde.org/show_bug.cgi?id=413726 --- Comment #6 from Scott Petrovic --- It must not be saving that setting per document then. That is where that checkbox data is stored when you click it. Maybe what you are trying to ask for is that those settings are saved to the KRA file? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413726] 'Show Painting Assistants', 'Show Assistant Previews', 'Show Reference Images' are not disabled after re-opening krita or document again.
https://bugs.kde.org/show_bug.cgi?id=413726 --- Comment #4 from Scott Petrovic --- This checkbox is tracked by document...not at the application level. This was requested a while ago because that is what some people wanted. To have different on/off settings per document. When you open a document and turn one of those settings off, that setting should only be kept for that specific document. Because of this "per document" way of storage, there is no way for Krita to know that you want that setting saved globally...and not just for a specific document. it is a bit confusing -- but hopefully it makes a bit more sense. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413726] 'Show Painting Assistants', 'Show Assistant Previews', 'Show Reference Images' are not disabled after re-opening krita or document again.
https://bugs.kde.org/show_bug.cgi?id=413726 Scott Petrovic changed: What|Removed |Added Severity|normal |wishlist CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- This would be a feature request that needs discussion. What you are proposing is that these features be off by default. We could do that, but we will probably be getting new bug reports from people asking why their assistants aren't shown...which of course is the result of having them turned off by default. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413726] 'Show Painting Assistants', 'Show Assistant Previews', 'Show Reference Images' are not disabled after re-opening krita or document again.
https://bugs.kde.org/show_bug.cgi?id=413726 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410136] Brush Editor does not show the blending mode until that blending mode is changed
https://bugs.kde.org/show_bug.cgi?id=410136 Scott Petrovic changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/f4f03ccdabb088 ||b4fe6d07534869b238c1297052 --- Comment #2 from Scott Petrovic --- Git commit f4f03ccdabb088b4fe6d07534869b238c1297052 by Scott Petrovic. Committed on 04/11/2019 at 14:08. Pushed by scottpetrovic into branch 'master'. Show blending mode option when application loads M +5-0plugins/paintops/libpaintop/kis_compositeop_option.cpp https://invent.kde.org/kde/krita/commit/f4f03ccdabb088b4fe6d07534869b238c1297052 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413793] New: Feature Request: Show mask thumbnail for filter layer on layer stack UI
https://bugs.kde.org/show_bug.cgi?id=413793 Bug ID: 413793 Summary: Feature Request: Show mask thumbnail for filter layer on layer stack UI Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: scottpetro...@gmail.com Target Milestone: --- Filter layers allow you to apply a filter in addition to using a mask to determine how much of the image will use the filter. We do not show the mask image though on the layer stack...just the final projection of the filter. We might have to discuss a bit how this would be done. Do we want to show the final result and the mask, or just one of them. Showing the mask would be nicer at times when selecting the grayscale color. It helps to know what to pick and what the mask currently looks like when coming back later. STEPS TO REPRODUCE 1. Create a filter layer with any effect OBSERVED RESULT Only the final filter result shown in the thumbnail. EXPECTED RESULT The mask is shown somewhere on the layer stack to show that a filter layer has a mask. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413601] New: Assert/crash with Magnetic Selection tool
https://bugs.kde.org/show_bug.cgi?id=413601 Bug ID: 413601 Summary: Assert/crash with Magnetic Selection tool Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: scottpetro...@gmail.com Target Milestone: --- I am getting quite a few crashes/asserts with this tool. I am not sure if it is related to the tool, or something with the tile hash table. I am on a nightly build from yesterday on a Windows 10 64-bit machine. (git 9a8f3bc) Right now the "ASSERT(krita)" I get the most frequently says this in the dialog... krita/libs/image/tiles3/kis_tile_has_table2.h: line 133 STEPS TO REPRODUCE 1. Make a selection with the magnetic selection tool. 2. Try to make another selection and try to do things like go outside the canvas or double click. OBSERVED RESULT Eventually get a crash or the assert mentioned above. I can usually get a crash within a minute of using it. EXPECTED RESULT No crash or assert. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411001] Brushes will not appear
https://bugs.kde.org/show_bug.cgi?id=411001 --- Comment #10 from Scott Petrovic --- If it happened just after an update, maybe there was some configuration change that was messing it up. You could try to clear your krita configuration file. Maybe for some odd reason that messed things up. http://nonaynever.ru/kwiki/krita/ResetKritaConfiguration -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410136] Brush Editor does not show the blending mode until that blending mode is changed
https://bugs.kde.org/show_bug.cgi?id=410136 Scott Petrovic changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |scottpetro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412364] Audio doesn't play (OSX)
https://bugs.kde.org/show_bug.cgi?id=412364 --- Comment #2 from Scott Petrovic --- They said they were going to come back on later to maybe provide more info. What type of information would be helpful for diagnosing this? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412364] New: Audio doesn't play (OSX)
https://bugs.kde.org/show_bug.cgi?id=412364 Bug ID: 412364 Summary: Audio doesn't play (OSX) Product: krita Version: 4.2.6 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: scottpetro...@gmail.com Target Milestone: --- SUMMARY There was a report that audio doesn't work when playing an animation from the animation docker. Interestingly, the audio appears to be working while scrubbing the timeline for them. The person was on OSX and Krita version 4.2.6. Scott tested it on Windows 10 4.2.6 and the audio for the animation worked ok. STEPS TO REPRODUCE 1. Load an audio file for your animation 2. Press the play button OBSERVED RESULT No audio playing EXPECTED RESULT Audio plays -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411001] Brushes will not appear
https://bugs.kde.org/show_bug.cgi?id=411001 Scott Petrovic changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from Scott Petrovic --- Maybe the default brushes were de-activated somehow. Go here and see. Settings > Manage Resources You should see the "Krita_4_Default_Resources" listed in the Active area. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408669] Animation Curves Docker Frame Scrubbing Doesn't Update Visual Indicator
https://bugs.kde.org/show_bug.cgi?id=408669 Scott Petrovic changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |scottpetro...@gmail.com CC||scottpetro...@gmail.com --- Comment #2 from Scott Petrovic --- I started doing some fixes to it that are in this merge request: https://invent.kde.org/kde/krita/merge_requests/56 The main blocker for this merge request right now, I think, is fixing the animation cache. The animation cache doesn't handle the opacity tweening stuff very well and shows old frames. We need to get that figured out first before this can be merged. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412232] Color Inconsistencies in Krita neutral theme on welcome screen
https://bugs.kde.org/show_bug.cgi?id=412232 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 CC||scottpetro...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Scott Petrovic --- It looks like some of the color issue just has to do with theme changing, not necessarily the theme itself. A few areas that have a dark theme just aren't updating with a theme change. The disabled icon is interesting though which might be a separate issue. For example all the tools on the toolbox are completely invisible when I start Krita with the neutral theme. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412061] Rotating selection with Transform Tool makes the selection edge rough
https://bugs.kde.org/show_bug.cgi?id=412061 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Scott Petrovic --- When did this start? Can you give a better example than a rectangle shape? There is always going to be some jaggies when you rotate something like that. This is just how computers work (unless you are talking about something I don't understand). People usually just get around this by either 1. Increase the DPI so it minimizes the jaggies 2. Work with vector files so the edges are calculated mathematically If I am not understanding, please explain it differently -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412060] fill with opacity doesn't work while using some selection tools
https://bugs.kde.org/show_bug.cgi?id=412060 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 CC||scottpetro...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Scott Petrovic --- I can confirm this. When they say it is "greyed out", quite a few items on the toolbar get greyed out when you select most of the selection tools. For some reason the rectangle and circle selection tools don't grey out toolbar items. We would have to look in the code to see why certain selection tools are doing that. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407416] Timeline 'Remove Layer' option does in fact delete the layer
https://bugs.kde.org/show_bug.cgi?id=407416 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #6 from Scott Petrovic --- I think where people want complete layer control is some animators. They don't want to have both the layers docker and the timeline docker open when they work. They want to be able to manage layers and everything with just the timeline docker. This is probably how most other animation packages work. We might need to think about the usability with this. We might just need to work on some wording with these terms or how you work with the timeline to achieve this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368331] To display the eraser mode
https://bugs.kde.org/show_bug.cgi?id=368331 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #9 from Scott Petrovic --- FYI - I just made a merge request to add this in. You can comment on that if you have any comments. https://invent.kde.org/kde/krita/merge_requests/147 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411823] Properties window for Local Selection should be disabled
https://bugs.kde.org/show_bug.cgi?id=411823 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- Confirming this on my Windows 10 device with Krita 4.2.6. When you select "Properties", right now nothing happens. It either needs to be disabled, or the properties dialog needs to appear with any information it has. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411805] Issue with texture pattern in brush engine
https://bugs.kde.org/show_bug.cgi?id=411805 --- Comment #10 from Scott Petrovic --- I see the second attachment and I see what you are talking about now. That is really weird though. I tested it on git master and that is not happening. I also tested 4.2.6 on Windows 10 and it is not happening there for me either. Would it be possible that you could play around with it more with other settings to see if something else might be doing that. For example you could try to disable other properties to see if it still happens -- like turning off the "strength" property by the pattern. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411805] Issue with texture pattern in brush engine
https://bugs.kde.org/show_bug.cgi?id=411805 Scott Petrovic changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||scottpetro...@gmail.com --- Comment #9 from Scott Petrovic --- It seems to work ok for me on git master right now. Something is not right with the attachment, because I also cannot see anything being painted on the canvas. Maybe there is some other setting that is causing the brush stroke to not appear -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411853] Resizing vector shapes and reference images is buggy, flickery.
https://bugs.kde.org/show_bug.cgi?id=411853 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- I can confirm this on git master on my Ubuntu system. There must be some type of compressor or something going on to make the resize more responsive. I wonder if we can make it update a bit faster without slowing things down. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411001] Brushes will not appear
https://bugs.kde.org/show_bug.cgi?id=411001 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Scott Petrovic --- It appears your brushes are just filtered down, so you only see a few of them. Can you take a screenshot of what your Brush presets docker looks like that only has the 3 brushes? Does setting the drop-down to "All" still only show 3 brushes? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411695] Steam sluggishness
https://bugs.kde.org/show_bug.cgi?id=411695 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- I am not aware of any difference in the source code between the Steam version and the free version. I guess it is possible there is a Steam layer that is doing some communication that is slowing something down a bit. Not sure if there is much we can do with this report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411793] [Wish bug] Add an option in file menu to open the current file in file manager.
https://bugs.kde.org/show_bug.cgi?id=411793 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||scottpetro...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Scott Petrovic --- This would be neat. Maybe we could put it under the File > "Open existing document as Untitled document..." option and call it something like "Open file location" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407898] Freeze when coming back from simple action and painting
https://bugs.kde.org/show_bug.cgi?id=407898 Scott Petrovic changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||scottpetro...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #11 from Scott Petrovic --- It does look like there is also something going on with the saving as well if you look a the task bar. The saving seems to be getting hung up for a reason. Not sure if that could be part of it. It looks like the version being tested was 4.2-beta as well. I think there were some saving fixes that has happened since then Setting to needs info while Valu can check -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411351] Assistant tool's opacity drops down everytime you un/hide it or move it (only with custom color set).
https://bugs.kde.org/show_bug.cgi?id=411351 Scott Petrovic changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/e96181d3629ef3 ||fe00ba2a7aba51b6878bd788eb Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Scott Petrovic --- Git commit e96181d3629ef3fe00ba2a7aba51b6878bd788eb by Scott Petrovic. Committed on 31/08/2019 at 16:37. Pushed by scottpetrovic into branch 'master'. Fix custom assistant color opacity from shifting M +11 -2plugins/assistants/Assistants/kis_assistant_tool.cc https://invent.kde.org/kde/krita/commit/e96181d3629ef3fe00ba2a7aba51b6878bd788eb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409184] Feature Request: Ability to open image sequence and animated gif directly from file menu.
https://bugs.kde.org/show_bug.cgi?id=409184 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- This might be a task that is better for a python plugin for doing a set of commands quickly than something we need to build directly into Krita. I would consider an animated gif a video, which is a different problem than the video you posted with image sequences. Animated GIFs have an additional step of extracting images before importing them. I did make a python plugin recently that you can import animated gifs (or other video files) to make it easier to import without starting a document. https://www.youtube.com/watch?v=VsYGtPXgJIg=12s There could potentially be an option to import an image sequence...but it really isn't saving much time since that option already exists in Krita and it wouldn't save that much time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411351] Assistant tool's opacity drops down everytime you un/hide it or move it (only with custom color set).
https://bugs.kde.org/show_bug.cgi?id=411351 Scott Petrovic changed: What|Removed |Added Status|CONFIRMED |ASSIGNED CC||scottpetro...@gmail.com Assignee|krita-bugs-n...@kde.org |scottpetro...@gmail.com --- Comment #2 from Scott Petrovic --- I will do this one. It looks like a simple number conversion issue that is dropping some decimal points or something -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384110] Shift-drag brush size change doesn't work for inpaint
https://bugs.kde.org/show_bug.cgi?id=384110 --- Comment #3 from Scott Petrovic --- This issue still exists. The tool I think they are referring to is the "smart patch" tool. Something tells me this tool is hardly used as no one else has chimed in about this ticket 2 years now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410793] Settings dialog is too high for very space constrained screens
https://bugs.kde.org/show_bug.cgi?id=410793 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #5 from Scott Petrovic --- I think this window got too big when the HDR settings area was added to the display part. I just checked out a nightly build on my Surface Pro. Between the HDR area and all the text warning stuff we have with ANGLE and OpenGL, that is pushing this area further down so it doesn't fit on a 1366x768 monitor. We are probably going to have to break this Display area into multiple tabs like we do with the General section -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409944] Toggling 'Global Selection Mask' does not return to the originally selected layer
https://bugs.kde.org/show_bug.cgi?id=409944 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||scottpetro...@gmail.com --- Comment #3 from Scott Petrovic --- It is functioning like the bug reporter is stating. We will have to figure out if there is a way to save the last layer selected for that global selection so it knows when to change. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410739] Add Icon for python configuration setting area
https://bugs.kde.org/show_bug.cgi?id=410739 Scott Petrovic changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410739] Add Icon for python configuration setting area
https://bugs.kde.org/show_bug.cgi?id=410739 Scott Petrovic changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Scott Petrovic --- Closing this ticket. Rebecca wasn't seeing it on her docker build, but it is appearing on both git master and the latest builds. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410739] Add Icon for python configuration setting area
https://bugs.kde.org/show_bug.cgi?id=410739 Scott Petrovic changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410739] New: Add Icon for python configuration setting area
https://bugs.kde.org/show_bug.cgi?id=410739 Bug ID: 410739 Summary: Add Icon for python configuration setting area Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: scottpetro...@gmail.com Target Milestone: --- Right now when you configure Krita, Rebecca and I noticed there is no icon for the Python portion of the settings. It would be nice if it had something so the option would be consistent with everything else. -- You are receiving this mail because: You are watching all bug changes.
