I guess the title is scary, but it is actually quite easy what I started today. To finally get the socket into the wall, I need the ability to cut out a hole. As I still haven't fixed the problem in the CSG, that it needs at least one edge of an object to run through a closed loop of the other, I implemented the huge change to the edge loop modifier, which I finished yesterday.
So what is keeping me from adding the socket is, that the box I need for cutting the hole is part of the group which combines the elements of the socket. And I can't access that object from the CSG-difference. The problem is, that the current code can only access two object pointers, one I need for the wall, the other would be the box. But as it is in a group, I wouldn't get the full transformation. The problem stems from the ability of my program to recreate the geometry, therefore I need access to the object after I have defined the CSG-operation. Worse, I want it to react to any changes in position and so it has to have the ability to get the complete transformation. For the user that means I want to be able to move the socket and the hole is supposed to move together with it.
To finally fix this problem, I started with a new object which will store pointers to all the relevant objects so I can recalculate the transformation. As that is basically the topological information it should explain the strange title. Currently not much is working, the object exists and it has some storage for information. But only storing is implemented, I still have to add loading tomorrow. It is quite hard to tell, how long I will need for this thing, but I hope it will be easier than the last thing.
It slowly becomes a tradition to be late. So here comes the review of March. Channel MaterialThe channel material is still unfinished. But it saw quite a bit of progress in March. I started with implementing the OpenGL version of the renderer. It tur
Tracked: Apr 09, 22:34