shaise wrote: ↑
Sun Sep 17, 2017 5:17 pm
1. As I would be happy if this tool will eventually be integrated into the path workbench, indeed the tool head is taken from the tool controller. And all the angles, radiuses and other parameters are taken from the tool controller. I still need to find out the meaning of each parameter so I can design other tools accordingly.
Right. But I'd like to see the TC's shape representation improved rather than re-implemented in your simulation code. Your CreateToolProfile() is vastly superior to what TC does now. It could move into the TC and then simulation (or anything else that needs it) could ask the TC for it's shape. Does that make sense?
2. Instead of simulation bar, I would like to leave only one workbench button, that when pressed on will open a parameters dialog in the task window. The reason is that I want to give a lot of flexibility to the user: Select what job to perform, and which operations within. Perhaps select a different object as a stock.
cool. Makes sense to me.
3. Showing animation or not does not affect the calculation time. What you see in the video is max speed. Disabling the animation will save 1 or 2 percent not more. (unfortunately)
Maybe now but who knows in the future? Short-cuts or alternate implementations might make it faster to go directly to the result. Also, we might think about the other extreme. It looks like the booleans are calculated for each Path command. What if I wanted to calculate MORE intermediate steps? This might really slow down the calculation but if I want to generate a smooth animation for a video and don't mind waiting... Well, you get the idea.
4. When the simulation ends, the result is left on the model tree so you can export it or do whatever. (right now the tool is left as well, but this is only temporary)
Fine for now. In the long run, I don't think we want to clutter up the tree with the simulation shapes but we can figure that out.