FreeCAD|
|
Schermafdruk - 27-04-16 - 07_56_03.png (133,276 bytes) |
|
|
I'm not sure I understand this well... Isn't it more or less what the bounding box does? |
|
|
Poking sliptonic... |
|
|
Sorry Yorik, I don't know why I didn't get the earlier poke from Mantis. I agree that this is essentially the bounding box. The linuxCNC feature is plotting the box extents but also labeling the dimensions and changing the labeling appearance if the path extents exceed the machine extents. This is very friendly for an operator since he can see with a glance where a problem lies. A few years ago, David Nichols added added some functionality to HeeksCNC to catch all kinds of common errors and problems. The code was later removed but I thought it made a lot of sense and I planned to add something similar to Path eventually. Instead of just displaying the bounding boxes, we could could actively check for un-cuttable conditions, collisions, use of default tools, paths intersecting the base object, etc, and notify the user. I'd like this 'sanity check' to be run as a separate command so it isn't interfering all the time and could be run in a batch mode or other automated process. |
|
|
Sounds like a good plan! I see you have no "developer" status here in the tracker, if you want at some point to attribute an issue to yourself, tell me and I upgrade you. Not wanting to put any pressure or whatsoever, though ;) |
|
|
I guess I'm the only one working on Path right now so you might as well upgrade me. I'll try to stay on top of these issues and shepherd them as we get more help. |
|
|
Ok it's done, you can now attribute issues to yourself if you wish. Don't consider this as an obligation of any kind, though, or that it is expected that you solve an attributed bug in a certain time frame... You know the FreeCAD way ;) |
|
|
A basic path sanity framework is in place. It's not very sophisticated but something to improve going forward. The bounding box works very well for visualization so I'm closing this issue. |
- Anonymous
