I am currently discussing this with @mlampert.
https://forum.freecadweb.org/viewtopic. ... 20#p357390
Seems like there is a hole in the process - when you press "Add" it should bring up a file selector for a tool library. Once you've loaded a tool library all you have to do is select the tools you want and then press "OK".
If by "visualization" you mean the simulator - it is currently not aware of the new tools and the different shapes. This is one of the reasons why we wanted this reality check, there's a lot of work left to do and doing all of that and then realizing that this isn't working for users would be a huge waste.
That is not the edit button, and it should be disabled currently. That is a button to (in the future) open a dialog which lets you customize the view of the tool library editor/manager. The intent is to allow users to specify which columns they want to see, in which order .... not implemented yet because ...
The tool library editor does not let you edit a "ToolBit". ToolBit's are shared across libraries, so if you add the same tool to two libraries, they literally point to the same tool. An unsuspecting user could modify the tool for one library and think/assume it's a local copy, being unaware that they just changed the tool for all other tool libraries also. In order to minimize such an error tools have their own editor which needs to be started explicitly.memfis wrote: ↑Fri Jan 03, 2020 2:54 pmNothing happens to me either when I press this button. Moreover, you can hang on, but not on this button.
I edit simply by opening the file from the Shape folder, then correcting the installation description file in the Bit folder, and after that I add the installation to the library from the Bit folder. Be careful not to confuse the description file with case sensitive letters, which point to the model file in Shape. I suppose that you can use both absolute and relative paths in the description file.
There is no result - yes, the tool has created, I see its real form, it does not affect the form of the created path in any way (and should not), the form of the tool, real, important and necessary for the visualization, which (so far) I have not succeeded.
It touches on related issues that I'm concerned about - the necessary amount of RAM and the processor. My 8gb seems to be very good, but... My point is that starting and editing the right tool separately, from a file manager or something else probably requires less resources than starting editing the tool directly from another project where the tool is used.mlampert wrote: ↑Fri Jan 03, 2020 7:09 pm
The README.md should describe the process of creating a new tool, withouth having to manually create and edit json files. If that description isn't clear, please help making it clearer by editing it or letting me know how to improve (for all who come after us).
It's easy, already discussed - open the file of fcstd tool in a separate window or through a regular file manager. If you use appimage, you should unpack it beforehand. And the description file (parametric) of the tool lies next to it, in Bit, copy any and edit it to your liking.