I said:
> Another way to do this (JMet does it) is to create a complex
> Tuple object with MathType:
>
> ((select1 -> ((x, y) -> (u, v))),
> (select2 -> ((x, y) -> u)),
> (select3 -> ((x, y) -> v)))
I should have said:
((select1 -> ((x, y) -> (u, v))),
(select2 -> ((x, y) -> u_1)),
(select3 -> ((x, y) -> v_1)))
with the ScalarMaps:
x -> XAxis
y -> YAxis
u -> Flow1X
v -> Flow1Y
u_1 -> IsoContour
v_1 -> IsoContour
select1 -> SelectValue
select2 -> SelectValue
select3 -> SelectValue
This way, when the user de-selects select2 and select3, you won't
still have iso-contours of u and v from ((x, y) -> (u, v)) used
for flow. Of course, u_1 and v_1 have the same values as u and v.
Cheers,
Bill
----------------------------------------------------------
Bill Hibbard, SSEC, 1225 W. Dayton St., Madison, WI 53706
hibbard@xxxxxxxxxxxxxxxxx 608-263-4427 fax: 608-263-6738
http://www.ssec.wisc.edu/~billh/vis.html
