Overrides on a per-component basis?

Of course, a system like this would first and foremost require that components with [Seamless-Tiling] and [Non-Seamless Tiling] can peacefully co-exist within the same filter. Non-seamless components would render as expected within the image bounds, but may produce visible seams if a filter author is not careful.

There exist many filters on the library which contain procedures that could be considered 'non-seamless' (take the often used polar coordinate transformations (a.k.a. 'Spherify')), yet they tile perfectly fine!

Many filters that mix Frame components with size-affected components suffer from the inability to disable [Size, pixels] on a per component basis. Finally, Profile Gradients could become much more versatile if they could be made unaffected by [Size, pixels].

Quote
StevieJ wrote: ...but maybe you'll have better luck with it...

Looks like I don't have any luck with it either!

Quote

Vladimir Golovin wrote: Roughly speaking, all components should have separate mappable transforms (of which the current implementation of Size is just a special case), seamlessness and the possibility to specify target image bounds on a per-component basis, along with the user-selectable method of handling samples beyond these bounds (wrap, mirror, extend etc.) -- or to acquire these image bounds from images loaded into FF.

Yes, that's exactly what I mean!

To describe it in Filter Editor / node-network terms: All components are currently automatically and irrevocably hard-wired to three global Control Components (which are always there and thus hidden inside the Filter Editor for user-convenience):

- Size, pixels
(a slider control component that is connected to each and every components' invisible Scale map input)

- Variation
(another slider control component connected to each and every components' invisible Variation input)

- Seamless Tiling
(a checkbox control component that is connected to each and every components' invisible Seamless Tiling drop-down selector)

Overriding any of the above global controls on a single component would be equivalent to deleting the respective connection to one of their 'invisible' inputs and setting this value manually (or even map it with another component?).

In effect, we could visualize this as a set of "underground connections" which are normally not visible inside the Filter Editor -- they are located on a sub-level of the Filter Editor, so to speak. Spinning this further, one could imagine putting the Filter Editor into an "underground" mode that allowed for visually editing these "under-the-hood" connections.

Hmmmm... the possibilities!

Or what if - instead of activating some "underground" mode - these hidden inputs were actually exposed from the get-go as visible control/map inputs on each and every component? We'd have to deal with a lot of previously hidden connections cluttering the editor! That is, unless we find a way to visually represent these global control connections without actually drawing connection lines inside the Filter Editor...

Quote
ronjonnie wrote: My point is, Beta 2, when I copy & paste one of my old filters, or a part of one into a new one I'm building, the Seamless option is grayed out, (non active)

Does the new filter you're building and into which you're copy/pasting your previous work include any of the new non-seamless components (Scale, Rotate, Free Gradient, Free Ellipse etc.)?

Quote
Yes, sorry. As a test, I used a filter from the Forum, I It was XY Anchor by Work, Yes it was not seamless. Why is that?

Ron

XY Anchor.ffxml

Vladimir,

Thank you. When the final Version of Filter Forge is finished, after all of the Beta testing, will this problem be resolved? I sure hope do.

Thank you for your time Vladimir, I love the program!
I will love it more after certain issues are resolved.

Ron

Vladimir,

Thank you. Lots to learn.

Crapadilla wrote:

Quote
Yes, that's exactly what I mean!

6th down from the top. Must be in here somewhere.

Ron

The current plan is as follows:

1. Implement a balloon notification that pops up when a user adds a non-seamless component to the filter. We would have added it in a hotfix already, but it requires some additional coding in the Editor.

2. Implement an additional override option for the Seamless Tiling checkbox that would force it to "always enabled". This will make previews of non-seamless components look weird when the Seamless Tiling is turned on, but it will solve the problem.

Hopefully, both will be available in the Beta Stage 4.

No, definitely not a modal dialog with a mandatory OK button -- I'm talking about the yellow thingies that we use as notifications in the Filter Editor, such as the thingy that shows elapsed rendering time.

Quote

Vladimir Golovin wrote: The current plan is as follows: 1. Implement a balloon notification that pops up when a user adds a non-seamless component to the filter. We would have added it in a hotfix already, but it requires some additional coding in the Editor. 2. Implement an additional override option for the Seamless Tiling checkbox that would force it to "always enabled". This will make previews of non-seamless components look weird when the Seamless Tiling is turned on, but it will solve the problem.

Both are now implemented (will be available in the upcoming beta stage.)