Project

General

Profile

Statistics
| Branch: | Revision:

examples / src / main / java / org / distorted / examples / blur @ bf2e8f97

Name Size
BlurActivity.java 5.05 KB
BlurRenderer.java 6.7 KB
BlurSurfaceView.java 2.94 KB

Latest revisions

# Date Author Comment
bf2e8f97 07/30/2020 10:38 AM Leszek Koltunski

Improve the Blur App to catch the bug where a small part of the Blur (and Glow) halo gets displayed on the other edge of the surface.

c0f27889 07/22/2020 09:53 AM Leszek Koltunski

We need to pause an Activity in the following way:

1) Activity.onPause()
2) View.onPause()
3) Library.onPause()

otherwise sometimes there are artifacts when pausing!

061449ed 06/16/2020 07:37 PM Leszek Koltunski

Only compile the Full, Normal & OIT programs when they are actually needed.

278a214c 05/06/2020 10:04 PM Leszek Koltunski

Convert Blur to stretchless API.

678c391d 05/05/2020 12:55 PM Leszek Koltunski

Change the Postprocessing effects: separate the radius and the halo.
Reason: we needed a way to specify the size of the halo around a postprocessed object; before it was automatically (and not very correctly) computed from the radius - before we knew the size of the object's bounding box, so this automatic computation was possible. Now we're removing the MashBase.getBounding(0 API, so the size of the halo has to be explicitly given by the user. This way is more correct anyway and gives the user more control (as the Multiblur app proves!)...

386fd702 02/28/2020 11:58 PM Leszek Koltunski

Merge branch 'empty-matrix-effects-in-the-center' into modern-empty-matrix-effects-in-the-center

698ad0a8 02/26/2020 10:23 PM Leszek Koltunski

Move the Effects.setStretch to Meshbase.setStretch

687263cc 02/26/2020 03:52 PM Leszek Koltunski

Move the 'pre-multiply mesh before applying any effects' thing from [(Xsize of texture, Ysize of texture) x Mesh's zFactor] to Effects.setStretch(sx,sy,sz)

f3ca895f 02/21/2020 11:27 AM Leszek Koltunski

Rename MeshFlat MeshRectangles.

dae661e9 05/12/2019 09:18 PM Leszek Koltunski

Invert the order of Matrix Effects. Now, just as in the other queues, the first matrix effect is actually the first to act on the object - not the other way around!

View revisions

Also available in: Atom