/ - Diff - Distorted Android

src/main/java/org/distorted/library/effect/FragmentEffect.java
38	38	*/
39	39	public static final int NUM_INT_UNIFORMS = 4;
40	40
41		static final int VALUES_OFFSET = 0;
42	41	static final int CENTER_OFFSET = 5;
43	42	static final int REGION_OFFSET = 8;
44	43	private static String mGLSL = "";

+      {
       private final Data1D mAngle;
       private final Data3D mAxis, mCenter;
       private float[] mTmp1 = new float[16];
       private float[] mTmp2 = new float[16];
       private final float[] mTmp1 = new float[16];
       private final float[] mTmp2 = new float[16];
     ///////////////////////////////////////////////////////////////////////////////////////////////////
     /**

      * <p>
      * Here and in Shear we have the whole reason why there are two separate 'P' and 'V' (Point and
      * Vector) matrices - Scale and Shear have to manipulate Points and Normal Vectors differently.
+     *
      * <p>
      * Points get multiplied by (sx,sy,sz) - and vectors by (1/sx,1/sy,1/sz) (think about it!) - or
      * better by sx*sy*sz*(1/sx,1/sy,1/sz) to avoid dividing my zero (vectors are normalized after)
+     *

      * At this moment the 'buffer' contains a) preprocessed object b) real object rendered 'on top' of
      * the preprocessed one.
      * Postprocess buffer. What this means exactly depends on the effect -
+     *
      * <p>
      * Only for use by the library itself.
+     *
      * @y.exclude
-...
        * Do we render the object directly to the final surface, and only postprocess and then blit its
        * 'halo', or do we render the object along with its halo to the intermediate framebuffer and
        * postprocess it as well?
+       *
        * <p>
        * Only for use by the library itself.
+       *
        * @y.exclude

         if( weightsCache[offset]==0.0f )
+          {
           float z, x= 0.0f, P= (float)NUM_GAUSSIAN / (radius>3 ? radius:3);
           float z, x= 0.0f, P= (float)NUM_GAUSSIAN / Math.max(radius,3);
           mWeights[0] = GAUSSIAN[0];
           float sum   = GAUSSIAN[0];
           int j;

     ///////////////////////////////////////////////////////////////////////////////////////////////////
     /**
      * Set Mesh association.
+     *
      * <p>
      * This creates an association between a Component of a Mesh and this Vertex Effect.
      * One can set two types of associations - an 'logical and' and a 'equal' associations and the Effect
      * will only be active on vertices of Components such that
+     *
      * <p>
      * (effect andAssoc) & (component andAssoc) != 0 || (effect equAssoc) == (mesh equAssoc)
+     *
      * <p>
      * (see main_vertex_shader)
+     *
      * <p>
      * The point: this way we can configure the system so that each Vertex Effect acts only on a certain
      * subset of a Mesh, thus potentially significantly reducing the number of render calls.
      */

     /**
      * Pull all points around the center of the Effect towards a line passing through the center
      * (that's if degree>=1) or push them away from the line (degree<=1).
+     *
      * <p>
      * Note: this is not a fully 3D effect - the pinching is always within the XY plane; z coordinates
      * of all vertices remain unaffected. If someone wants a fully 3D Pinch effect, we'd probably need
      * to write another VertexEffectPinch3D with 2 more arguments (latitude and longitude angles defining

     ///////////////////////////////////////////////////////////////////////////////////////////////////
     /**
      * Pull all points around the center of the Effect towards the center point (if degree>=1) or push them
      * away from it (degree<=1).
      * Pull (degree>1) or push away from (degree<1) all points of an infinite 'pipe' shaped region.
      */
     public class VertexEffectPipe extends VertexEffect
+      {

     ///////////////////////////////////////////////////////////////////////////////////////////////////
     /**
      * 'Swirl' part of the Mesh, i.e rotate part of it around a point.
+     *
      * <p>
      * Note: this is not a fully 3D effect as the swirling happens entirely within the XY plane - z
      * coordinates of all vertices remain unaffected. If someone wants a fully 3D swirling, we'd
      * probably need to write another VertixEffectSwirl3D with two additional parameters: latitude and

     ///////////////////////////////////////////////////////////////////////////////////////////////////
     /**
      * Directional, sinusoidal wave effect.
+     *
      * <p>
      * Not a fully 3D effect. To achieve a fully 3D one we'd need another parameter making the whole thing
      * a 6D effect but there's no room in the Vertex Uniforms which assign only 5 floats for interpolated
      * effect values. Rethink this. ATM fully enough for 2.5D meshes like the MeshCubes.

Distorted Android