prongs error

Replies to This Discussion

Permalink Reply by Daniel González Abalde on September 19, 2017 at 3:55am

Hi Hieu Le,

Peacock has some components that have not been passed to code yet, they are gh definitions and this sometimes (along with my implementation at that time) makes the processes only work with certain data structures. For example, [Prongs fasten] does not work with lists, each element you have to include it in a branch doing Graft. When all the components are passed to code these problems will not be. You can see those that are not passed to code leaving the mouse over the icon, if you see a long definition is that you can have this inconvenience, if there is practically only one component inside, that is a scripting component, which establishes the input data structure. Simply if someone does not behave as you expect, try to put each element in a branch. [Prongs studio] seems to work as expected.

Attachments:

• unnamed.gh, 320 KB

Permalink Reply by Hieu Le on September 20, 2017 at 5:17am

Hello Daniel González Abalde. Thank you very much for your help. But I think, these two tools are not exactly what the jeweler desired. I have two suggestions 
1 / prongs studio: prongs not properly positioned

Actually it must be like this:

2/ prongs fasten : This tool prongs the correct position but the prongs are bent. If the designer just stopped at the drawing or used for the render, it was very good, but when printing to make metal, sure they get in trouble.

Permalink Reply by Daniel González Abalde on September 20, 2017 at 6:07am

Please do not get confused, these tools have been designed for my own use and I have shared them freely with the community. When I release a paid version then I will focus on what the jewelers need. Anyway, any suggestion is welcome.

1. Your proper version of how prongs should be applied is only valid when working with gem lines, that is not always the case. I prefer to make generalist tools because knowing a little of GH you can get any configuration. Again, particular tools will be in the paid version, especially in the subject of paves.

2. Im aware of that. For me it is not a problem because in case of wanting to manufacture only I have to make the following image, very easy, less than 1 min. But of course, your point is valid. When I pass that component to code I will add a boolean input to decide whether to grab the gem or not.

EDIT: Peacock has other Prong tool (and two more components) that we have been delivering to our students. I think it's time to include this 3 new tools in the public version. One of these days.