Links to the bug tracker:
On 27/7/10 01:29, Krzysztof Kosiński wrote:
I noticed there are several issues with the filter effects dialog:
- Wrong initial value for the "Type" combo box of feColorMatrix when
adding a new filter effect or loading an existing one (patch snippet attached, please apply to 0.48 as well).
similar issues with Effect Parameters UI tab: 386627 Data display remanence in filters Color matrix dialog https://bugs.launchpad.net/inkscape/+bug/386627
216945 Filter Effects - editing text control problem https://bugs.launchpad.net/inkscape/+bug/216945
194408 Filters don't always use parameters as displayed in dialog https://bugs.launchpad.net/inkscape/+bug/194408
- Undo does not work correctly: when modifying a parameter using a
slider, undo does not restore the slider to its value at the start of the drag, but to intermediate positions during the drag. (Fixing this likely requires a substantial rewrite.)
579932 Too much states saved for undo/redo when using sliders https://bugs.launchpad.net/inkscape/+bug/579932
- It says feComponentTransfer is not implemented in Inkscape, but in
fact it is.
190063 filter component transfert don't work https://bugs.launchpad.net/inkscape/+bug/190063
- Some sliders have completely bogus ranges. For example the surface
scale slider on feDiffuseLighting operates in the absurd range [-1000, 1000] with a step of 0.1, whereas 90% of the useful values lie in the range [-1, 1]. [-5, 5] is a more appropriate choice. (I'll follow up with a ptach that fixes some of the more outrageous ranges.)
related(?) - default value not representable with slider 193924 limiting cone attribute settings UI https://bugs.launchpad.net/inkscape/+bug/193924 193926 divisor attribute for feconvolvematrix (default value UI) https://bugs.launchpad.net/inkscape/+bug/193926
related(?) - improved slider increments: 178336 spin boxes increment values on filters UI need tweaking before 0.46 release https://bugs.launchpad.net/inkscape/+bug/178336
On 27/7/10 02:04, Joshua A. Andler wrote:
The current dialog should really be replaced by something more intuitive and less "rigid" feeling at some point. I personally like the way they do the compositor nodes in Blender and think that perhaps something more like that could be easier to work with.
Here's one screenshot with it for those who aren't familiar. http://www.blender.org/typo3temp/pics/61389a332f.jpg
308773 filters UI versus blender nodes https://bugs.launchpad.net/inkscape/+bug/308773
506580 filter : thumbnails of each step + disable operations after step n https://bugs.launchpad.net/inkscape/+bug/506580
Blueprint: "Improving the Filter Effects Dialog with better visualization and flow" https://blueprints.launchpad.net/inkscape/+spec/improved-filter-effects-dialog
~suv