Bug 319443 - SVG, PNG and ABR predefined brush source ignores spacing setting.
Summary: SVG, PNG and ABR predefined brush source ignores spacing setting.
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Brush engines (show other bugs)
Version: git master (please specify the git hash!)
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-07 01:56 UTC by vanyossi
Modified: 2013-08-08 09:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
svg brush (3.61 KB, image/svg+xml)
2013-05-07 01:58 UTC, vanyossi 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description vanyossi 2013-05-07 01:56:35 UTC 
When using a brush from an SVG source (in brush folder) the spacing setting is ignored.

Scale and rotation works fine.

Reproducible: Always

Steps to Reproduce:
1. Add an svg brush by placing an svg file in he brush folder.
2. Select predefined brush, the svg file
3. try to vary spacing
Actual Results:  
Spacing does not change

Expected Results:  
Spacing change according to set value

Spacing seems to be in an "on/Off" state because if spacing 10.0 is set then spacing is applied. Anything less than 10.0 like 9.99 will turn the swith to "off" and all spacing will remain unchanged from 9.99 to 0.01

Video showing the behavior
http://youtu.be/r9fkHZqSsZU
Comment 1 vanyossi 2013-05-07 01:58:36 UTC 
Created attachment 79747 [details]
svg brush

Added the svg brush created using inkscape.
Comment 2 vanyossi 2013-05-08 02:13:08 UTC 
This also happens with PNG image sources. Spacing is ignored and set automatically to 0.02 unless spacing set to 10.0
Comment 3 vanyossi 2013-05-08 04:06:18 UTC 
Just to add. photoshop ABR brushes have this behavior too. brush tips loads but spacing won't work.
Comment 4 Halla Rempt 2013-05-13 17:10:36 UTC 
Maybe Lukas can look into this?
Comment 5 Dmitry Kazakov 2013-08-08 09:53:10 UTC 
Looks like this bug has also been fixed by the recent refactoring. I cannot reproduce it anymore.