10 |
Transformations |
Transformations |
11 |
--------------- |
--------------- |
12 |
|
|
13 |
Add into VobCoorder the following convenience function:: |
Add into VobCoorder the following convenience functions:: |
14 |
|
|
15 |
public int translate(int into, float x, float y) { |
public int translate(int into, float x, float y) { |
16 |
return coordsys(into, 0, x, y, 1, 1); |
return coordsys(into, 0, x, y, 1, 1); |
20 |
return coordsys(into, z, x, y, 1, 1); |
return coordsys(into, z, x, y, 1, 1); |
21 |
} |
} |
22 |
|
|
23 |
|
public int scale(int into, float x, float y) { |
24 |
|
return coordsys(into, 0, 0, 0, x, y); |
25 |
|
} |
26 |
|
|
27 |
|
.. IMPORTANT: |
28 |
|
Should 3D scaling be here as well? |
29 |
|
|
30 |
And into AffineVobCoorder the following convenience function:: |
And into AffineVobCoorder the following functions:: |
31 |
|
|
32 |
int rotate(int into, float degrees); |
int rotate(int into, float degrees); |
33 |
int rotate3D(int into, float degrees, float x, float y, float z) ; |
int rotate3D(int into, float degrees, float x, float y, float z) ; |
34 |
|
int scale(int into, float x, float y, float z); |
35 |
|
|
36 |
.. IMPORTANT: |
.. IMPORTANT: |
37 |
Should we add default implementation of rotate? |
Should we add default implementation of rotate? |
38 |
|
|
39 |
|
.. IMPORTANT: |
40 |
|
Should rotate3D really be there? It extends the capabilities? |
41 |
|
Should there be a third interface, ThreeDCoorder? |
42 |
|
|
43 |
Transforming points interactively |
Transforming points interactively |
44 |
--------------------------------- |
--------------------------------- |
45 |
|
|
63 |
simply performance. |
simply performance. |
64 |
|
|
65 |
.. IMPORTANT:: |
.. IMPORTANT:: |
66 |
|
Names? |
67 |
|
|
68 |
|
.. IMPORTANT:: |
69 |
Should we provide a form with a default return of float[] for convenience? |
Should we provide a form with a default return of float[] for convenience? |
70 |
How would inverse then work? |
How would inverse then work? |
71 |
|
|