filter.blurGaussian, how to prevent updating every frame

Is there any way to prevent a snapshot from continuously updating every frame when using a gaussian blur?

I’m aware of the work around of putting a snapshot within another snapshot to prevent the child snapshot from updating each frame but this solution isn’t really helpful if you need to update the original child snapshot now and again (and we shouldn’t really even have to do this work around if the filters were work properly.)

Would be great if we had a variable to tell the sdk not to update a snapshot every frame (i actually thought it shouldn’t update unless we tell it to invalidate but seems gaussian blur filters are continuously applied each frame whether you invalidate or not, not sure if other filters do this also).

Right now the only solution to using any type of  blur filter on a snapshot without serious drop in frame rate is to use the standard filter.blur. It doesn’t seem to cause any lag per frame (in my tests it still runs at 30 frames, while using even a low value gaussian blur reduces the frame rate to 7! And that is without invalidating the snapshot again at any time after applying the filter).

However the default values of filter.blur are too high making the snapshot way too blurry. It would also be great if corona can at the very least allow us to set the default blur value of the filter.blur if it’s too hard for them to prevent gaussianblur from updating every frame.

So just asking for 2 very simple additions; let filter.blur be adjustable, and let filter.blurGaussian have a variable that allows us to decide if we want it updating every frame or one time only.

has this been fixed?

I doubt it. We would need a bug report.

Rob

Has this been fixed?

I don’t believe any one has filed a bug report yet. I can’t find an open one.

Rob

has this been fixed?

I doubt it. We would need a bug report.

Rob

Has this been fixed?

I don’t believe any one has filed a bug report yet. I can’t find an open one.

Rob