| Summary: | Liquify smooth | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | reptillia39 |
| Component: | Tools/Transform | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | halla |
| Priority: | NOR | ||
| Version First Reported In: | 4.0 pre-alpha | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
reptillia39
2017-11-18 18:19:08 UTC
Hi Reptilian, I'm sorry, but this kind of bug report is just not very useful. What we see is a bit of a wall of text with a rather vague kind of wish. There are two kinds of reports that can go into bugs.kde.org: bugs and wishes for feature requests. This is a guide on making a good feature request: https://krita.org/en/item/ways-to-help-krita-work-on-feature-requests/ A bug report on the other hand should be about something that is clearly an error in the way Krita works (so no vague things about performance, nothing about application X works differently, so Krita should be different). It should have the following features: * the version of Krita and the OS hardware used. * a clear description of the issue * a concise set of steps that allows us to reproduce the issue * optionally files that help with reproducing the issue, a video that shows the issue, images that show the issue. This report fits neither category, so I have to close it: it's cluttering up our todo list with something we cannot take action on. |