Bug 387082 - Liquify smooth
Summary: Liquify smooth
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: Tools/Transform (other bugs)
Version First Reported In: 4.0 pre-alpha
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-18 18:19 UTC by reptillia39
Modified: 2017-11-25 11:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description reptillia39 2017-11-18 18:19:08 UTC
Right now, sometimes liquify leads to bumpy results that requires smoothing, and there doesn't seem to be a smoothing function in liquify. I would like to make my liquify changes rather guassian in an area or something on the line of that. It would be useful to fix up drawing in the final stage or starting stage. Might be used seldomly, but in a few scenario, I can see it useful. Not necessary as manual smoothing by hand would do the job in the majority of the case, but it'd be nice to have to make people a bit more productive.
Comment 1 Halla Rempt 2017-11-25 11:12:12 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.