Did a few experiments with the goal of improving our current framerate
of ~4 compared to ~12 before adding multiple params, etc.  Got a tiny
bit but my sense is that there is one bottleneck that I haven't quite
found yet.  Tried passing params flat, i.e., on the stack, and got some
barely perceptible gains.  So I suspect that's not where it is.  I also
eliminated the template weirdness around the wrap mode in favor of a
branch-free wrapOrClamp, and again, seemed to help slightly.  Made the
code less horrendous so I like.
Recreated the eclipse project, somehow, weirdly.  It had to happen, was
getting intolerable with the unresolved includes, unattachable source,
etc.  I created a new workspace, then went to my working directory and
deleted everything that wasn't written by me, and created a new android
project from existing code.  I then managed to get the new project
hooked up with the git repo again somehow, and now it's as good as new!
Tightened up some transformation code in the view.
Fixed eclipse project setup some more by adding linked folders for
includes
Attempted to speed things up by moving the transformation from [0,1]^2
-> [-1,1]^2 into the actual sampling code rather than requiring a pre-
and post- transform every sample.  It is significantly faster (~8fps
rather than ~5) and removes at least one of the ugly lhs and rhs steps.
The zooming part is still not quite working right, so I'll need to get
that sorted next.
Continued the switch to [-1,1]^2.  Scaling is off - but it's fast!
Some small improvements to make the transformation behavior align with
the working version before the multiparam adventure, and to improve
efficiency.  At this point, the affine transformations match in java and
in C++ land.  But the scaling is still strange.  So the mystery
remains...
Um.  Oops.  Got complex multiplication wrong.  How come noone
complained? :)
Finally fixed the thing with the scaling.  As expected, it was the
dumbest thing conceivable: Basically, I had a bit of non-const code that
did some in-place matrix multiplication and neglected to consider the
subtleties of computation in-place.  To dress it up so it sounds less
dumb.  But now, we are golden!  Dot and map are in sync.  My
determination was seriously flagging for a bit there.  But with renewed
energy I will merge this to master and proceed with more optimization.