Bugged Filter Placement in Library

i just noticed on this filter: http://www.filterforge.com/filters/5432.html that it isnt really an effect filter. it's a texture. however, it's listed in the effect filters. the reason is, it has an image component within it. however, that component isnt hooked up. it's just there. and that got me to wondering how many other filters might fit this same situation.

so, a suggestion on this, change your criteria for effect versus surface to ONLY include components that are actually in the subtree back from the result component. otherwise, we're going to have a very screwed up library in places.

(though, it is kind of an interesting trick to hide a surface/texture filter out of sight of the texture sellers ).

Quote
Crapadilla wrote: that definitely looks like a bug

It's not a bug, it's a feature
Effect filters are determined by the presence of the Image component. If the author submits an update without this component, the filter will fall into the correct category.

yup, what dilla said. and i do know that this really is the author's responsibility in prime, but, it's YOUR library, too

the thing is, if i went looking for a 'dragon skin' filter, i'd go looking in texture filters, not effect filters. so, with a touch of programming, at least some of this could be addressed when an author goofs and leaves something in where it shldnt be. and heck, i sometimes leave orphaned routines in just to give someone else a look at other possibilities, but i wouldnt want them placed in the wrong spot because of it.