Having to update tool library changes in multiple places is not fun!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I understand why the local or cloud tool libraries are not linked to project tool libraries. For example, I may want to update a tools feeds and speeds only in the project or toolpath I am working on.
However, there have been many times where I realized the feeds and speeds for a tool were incorrect, and that tool was used in multiple toolpaths in several projects. So now, I have to correct the feeds and speeds in multiple places, the projects the tool is used in and the local or cloud tool library.
It would be really nice to have an option, such as a checkbox, on the tool edit screen that allows us to propagate any tool changes we make to all the libraries that the tool is defined in. This would be a huge time saver!
I submitted this as an idea. If you like it and would like upvote the idea, here is the feature request.
In the meantime, does anyone have any ideas or workarounds for this problem? For example is it possible to make tool setting changes one time in Excel (after exporting the library to the CSV) and then bring those changes back into the library and the toolpaths that use that tool?
Thanks!
