- 03 Jun, 2019 1 commit
-
-
Boudewijn Rempt authored
We probably should warn the user that they are rendering from a different place than the animation starts, but we should not forbid it, so we need to think of how we might implement that warning. BUG:408198
-
- 17 May, 2019 1 commit
-
-
Agata Cacko authored
Before this patch, there were two layers of error codes: KisImageBuilder_Result in KisImageBuilderResult.h later converted into ConversionStatus in KisImportExportFilter.h In case of usage of libraw, there were also libraw error codes. After this patch, only one error code system and error messages system is implemented. Error codes should match the previous ones, but are not necessarily correct now.
-
- 16 May, 2019 1 commit
-
-
Dmitry Kazakov authored
We shouldn't try to end the same stroke multiple times. The patch also makes sure KisProcessingApplicator is owned by a scoped pointer instead of manual handling. BUG:407520
-
- 10 May, 2019 2 commits
-
-
Dmitry Kazakov authored
-
Dmitry Kazakov authored
-
- 09 May, 2019 1 commit
-
-
Victor Wåhlström authored
Change Document::createFilterMask API to require either a Selection or a Node from which to initialize the selection with. This prevents a crash that would occur when parenting a FilterMask without a selection to a node. BUG:395000
-
- 03 May, 2019 1 commit
-
-
Boudewijn Rempt authored
The histogram dialog shows incorrect histograms, compared to the histogram docker. The histogram docker is also prettier and more clear. We do lose the ability to show histograms in diffrent colorspaces than the layer's colorspace, but that seems to be even more broken. We also cannot scale histograms for floating point colorspaces anymore, but that also seemed to be broken.
-
- 01 May, 2019 1 commit
-
-
Boudewijn Rempt authored
Differential revision: https://phabricator.kde.org/D20931
-
- 30 Apr, 2019 1 commit
-
-
Boudewijn Rempt authored
This also disables the video options button if the current format is gif, since there are no extra options for rendering to gif, and removes the extra options for gif in the videosaver, so we don't get unusable arguments like baseline profile for gif. BUG:403873
-
- 24 Apr, 2019 2 commits
-
-
Dmitry Kazakov authored
The patch fixes two problems: 1) DlgAnimationRenderer didn't initialize frames' mimetype correctly, so exporting always happened into PNG format. 2) DlgAnimationRenderer should correctly initialize saving format settings from the default cfg.exportConfiguration(). Using the same settings for both, animation rendering and normal image save is a disputable approach, but that is how we do it for ages. 3) EXRConverter shouldn't call any blocking functions on the image (and shouldn't change the state of the image as well). So it should convert non-16f/32f layers on the fly. BUG:406830
-
Ivan Yossi authored
save, now accepts an optional bouding region to set export area. Differential Revision: https://phabricator.kde.org/D20573 BUG:404615
-
- 18 Apr, 2019 1 commit
-
-
Boudewijn Rempt authored
BUG:406666
-
- 16 Apr, 2019 3 commits
-
-
Yuri Chornoivan authored
Summary: There are few 'grey' and 'colour' in the Krita messages. It would be good to use 'gray' and 'color' consistently. Test Plan: none Reviewers: #krita, woltherav Reviewed By: #krita, woltherav Subscribers: woltherav Tags: #krita Differential Revision: https://phabricator.kde.org/D20609
-
Boudewijn Rempt authored
-
Boudewijn Rempt authored
BUG:405108
-
- 05 Apr, 2019 1 commit
-
-
Boudewijn Rempt authored
Because, when running krita as a flatpak, we want our ffmpeg, not the distribution one. BUG:405146
-
- 26 Mar, 2019 1 commit
-
-
Alvin Wong authored
PyQt5 started requiring a private copy of the sip module, so we have to build sip as a private sip module for PyQt5. BUG: 405796
-
- 07 Mar, 2019 1 commit
-
-
Wolthera van Hövell authored
-
- 06 Mar, 2019 1 commit
-
-
Agata Cacko authored
Summary: This commit changes the limit for image size in the dialog from 90k pixels to 100000k (100M) pixels which is the same limit as in the File -> New dialog. BUG:395267 Test Plan: - trying to scale image to 1000M pixels in any dimension (dialog should not allow for that) - trying to scale image to 1000M pixels, but in a different unit (according to dpi); dialog should not allow for that - trying to scale image to 20k pixels, it works fine Reviewers: #krita, woltherav Reviewed By: #krita, woltherav Subscribers: woltherav Tags: #krita Differential Revision: https://phabricator.kde.org/D19545
-
- 04 Mar, 2019 1 commit
-
-
Boudewijn Rempt authored
-
- 27 Feb, 2019 3 commits
-
-
Boudewijn Rempt authored
And rename it to KisSqueezedComboBox. WidgetUtils should contain all widgets that don't depend on any of the pigment or flake or resource related parts of Krita.
-
Dmitry Kazakov authored
H264 and H265 codecs cannot handle odd image sizes and just fail.
-
Dmitry Kazakov authored
When the image is not yet saved, the default base for relative paths should be 'Pictures' filder.
-
- 26 Feb, 2019 5 commits
-
-
Dmitry Kazakov authored
-
Dmitry Kazakov authored
-
Dmitry Kazakov authored
-
Dmitry Kazakov authored
-
Dmitry Kazakov authored
1) Remove 'video' impex plugin. Now the exporting classes are built in into animationrenderer plugin. It allows us not to pass the options via untyped KisPropertiesConfiguration, but via a type-safe and compiler-tracked KisAnimationRenderingOptions. 2) Add options for configuring HDR video encoding with HEVC (H265) codec 3) When HDR video option is activated, then PNG export filter is automatically forced to output HDR PNG files (see a hack in DlgAnimationRenderer:: getFrameExportFilterConfiguration()) 4) !!! Rendering dialog now supports relative paths for video and frame export locations. As a base it uses either document location, or the location of animation/frames, if it is present and absolute.
-
- 22 Feb, 2019 1 commit
-
-
Wolthera van Hövell authored
This fixes a bug where exporting exr frames caused a crash.
-
- 05 Feb, 2019 1 commit
-
-
Boudewijn Rempt authored
We can now log important events to a krita.log file. It is completely independent of qDebug, and only meant for those actions that we know users often get wrong or have problems with. Right now, it logs creating, loading, exporting and saving a file, and switching between the smoothing options. The krita.log file is NOT automatically uploaded or shared or anything like that. The header that explains this is translated so users can see that for themselves. We rotate 10 sessions in the log file, so even if the user starts Krita a few times after having a problem, we should still be able to review the problematical session. The logging api is pretty simple: a static KisUsageLogger::log method that writes a timestamp, and a KisUsageLogger::write method that writes an informational line without a timestamp. Note that the logger is created and torn down in the main function: this means that the location is GenericDataLocation, not AppDataLocation. CCMAIL:kimageshop@kde.org
-
- 29 Jan, 2019 1 commit
-
-
Dmitry Kazakov authored
You need to add -DHAVE_HDR to enable HDR-related code. But you will need a patched Qt for that. The patch also makes the code behave correctly on Linux systems. PS: The patch also makes it possible to select OpenGL ES renderer on Linux. The renderer is selected fine, but doesn't work for some reason. I guess some texture format is set incorrectly.
-
- 25 Jan, 2019 1 commit
-
-
Rebecca Breu authored
This will produce basic method signatures in the inline Python help.
-
- 23 Jan, 2019 1 commit
-
-
noemie scherer authored
One use-case for the imagesplit is modifying spritesheet found externally (for example on the internet): splitting them then re-importing them in the animation timeline lets you use the dedicated animation tools, like the onionskin, and easily preview the animation with your modifications. But most spritesheet found on the internet are horizontal, like so: 1, 2, 3 4, 5, 6 while a few are vertical, like so: 1, 3, 5 2, 4, 6 Adding a button to choose which is more appropriate lets the imagesplit be used in both cases and still name the individual images correctly. I put the default at horizontal, while it was at vertical before, because it seems more widely used. Differential revision: https://phabricator.kde.org/D18442
-
- 10 Jan, 2019 1 commit
-
-
Scott Petrovic authored
-
- 06 Jan, 2019 2 commits
-
-
Boudewijn Rempt authored
-
Yuri Chornoivan authored
-
- 03 Jan, 2019 1 commit
-
-
Boudewijn Rempt authored
Krita could not save them, we save as svg gradients. Karbon is unmaintained, and I couldn't figure out how to save a karbon gradient with Karbon anyway.
-
- 25 Dec, 2018 2 commits
-
-
Dmitry Kazakov authored
Summary: As discussed with @rempt yesterday, I've modified `Node.save` to accept this `InfoOjbect` just like `Document.exportImage` in order to be able to save layers in batch mode with predictable output settings. As it happens, I can't get Krita working with Python on my PC due to incompatibilities between PyQt5 (v5.11.3) & Qt5 (v5.11.1) libraries. It can't easily be solved as I couldn't find compatible packages, there's no PyQt5 v5.11.1 release unfortunately and the change appears in v5.11.2 Patch by Razvan Radulescu (https://phabricator.kde.org/p/razcore.art/) Reviewers: rempt, #krita Reviewed By: rempt, #krita Subscribers: rempt Tags: #krita Differential Revision: https://phabricator.kde.org/D17639
-
Dmitry Kazakov authored
Summary: Call the implicit KisImageSP destructor with scoping. Alternatively, we could remove the: // check if the image has actually been deleted KIS_SAFE_ASSERT_RECOVER_NOOP(!sanityCheckPointer.isValid()); check from KisDocument which seems a bit possessive about its current image. Test Plan: Cf. https://bugs.kde.org/show_bug.cgi?id=396985 Patch by Beuc (https://phabricator.kde.org/p/Beuc/) Reviewers: #krita Subscribers: dkazakov Tags: #krita Differential Revision: https://phabricator.kde.org/D17708
-
- 19 Dec, 2018 1 commit
-
-
Boudewijn Rempt authored
QPointF shouldn't be passed by reference
-