You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think being able to place components relative to other components coordinates would be simplified greatly by this and the amount of literal double/int values in the design would decrease significantly.
another example would be placing a component on the surface of a sphere by giving coordinates in spherical system with origin attached to the center of the sphere.
The schemes illustrated by the examples are of course something I came up with very quickly, and we could think of some more clever solution for placing components relative to each other in a way that the computer would calculate the coordinates for us based on the already placed components.
The text was updated successfully, but these errors were encountered:
I think being able to place components relative to other components coordinates would be simplified greatly by this and the amount of literal double/int values in the design would decrease significantly.
Making something like
Component cube = Cube::create(5.0, 5.0, 5.0);
CompositeComponent cubes = Union::create();
cubes << cube;
for(int i = 0; i < cube.corners.size(); i++)
{
cubes << Cube::create(2.0, 2.0, 2.0).translate( cube.corners.at(i) );
}
another example would be placing a component on the surface of a sphere by giving coordinates in spherical system with origin attached to the center of the sphere.
The schemes illustrated by the examples are of course something I came up with very quickly, and we could think of some more clever solution for placing components relative to each other in a way that the computer would calculate the coordinates for us based on the already placed components.
The text was updated successfully, but these errors were encountered: