Bug 283184 - Avanced outliner for sketchbrush
Summary: Avanced outliner for sketchbrush
Status: RESOLVED DUPLICATE of bug 278034
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: git master (please specify the git hash!)
Platform: Unlisted Binaries Linux
: NOR wishlist
Target Milestone: ---
Assignee: LukasT
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-02 16:08 UTC by David REVOY
Modified: 2011-10-08 12:29 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David REVOY 2011-10-02 16:08:32 UTC
Version:           svn trunk
OS:                Linux

( for 2.5 )

When painting/sketching with the 'Sketch-brush' engine ( the harmony-like one )I often end up with a preset having a large brush visual outline for a little brush.
ex : http://img269.imageshack.us/img269/429/selection001.jpg
This is a bit hard for a user feedback to use it, even if I understand the radius show the magnetic distance of the brush. Still, I miss a 'center'. 

As a proposition ; I can imagine this 'radius for substrokes' as a secondary feedback, and a marker for the center of stroke as a primary feedback . Something like this mockup : http://img4.imageshack.us/img4/4846/selection004.jpg
( center cross + radius circle transparent )

Discution on the mailing list : 
topic name 'Sketch-brush outline issue (or not)' around 30/09/2011

Note : This kind of 'double radius feedback' could also solve other brushes/presets with dynamic on radius size (as pressure, etc) ; showing -for example- a mini and maxi radius for a brush to give a visual feedaback range to the user...

Reproducible: Didn't try


Actual Results:  
 

Expected Results:
Comment 1 Halla Rempt 2011-10-08 11:05:18 UTC
Hi David,

Thanks for the report. We've discussed this on the mailing list with you as , and there are plenty of good ideas here.
Comment 2 Halla Rempt 2011-10-08 12:29:36 UTC

*** This bug has been marked as a duplicate of bug 278034 ***