How do I use the point select component of Shapediver to get the user to select a point in the mesh, couldn’t find any document/example showing this.
I’ve used gumball component in my definition file and am trying get the preview of it to turn off and turn the preview of the next component to turn on- but when I do this, grasshopper takes the object before the ‘gumball transformations’ occurred (see picture attached). Please let me know what am I doing wrong.
The Points Input is still in beta and the documentation is still in progress. Here is a small example model showing how to draw on a mesh using a Points Input component.
More extensive documentation will come in the next days, but feel free to ask follow-up questions here after you review the example.
–
I do not fully understand your second question. I see that the “Inject Attributes” component throws an error but it is not clear why without seeing the definition. Please explain more in details and attach a minimal example.
Hi @mathieu1 thank you for the example file (How do I set the default no of points in the point input though?)- it solved my issue, regarding the Gumball problem that was resolved too.
I do however, have another problem now- only the beginning of my grasshopper definition is showing up in Shapediver after I upload it on the platform.
A very big part of my definition file is not showing up in Shapediver. Can you please help me with this? (see attached pictures)
Hi, can you please look at the above issue once or tell me what I should be careful about to avoid this?
This is the only issue preventing me from testing the whole script in Shapediver.
Could you please share a minimal definition helping me reproduce the problem? I cannot provide help from your screenshot only.
Regarding the default points of the Points Input component: you can right-click on the component and set a default set of points or polyline using the “Default value” option.
Hi, I cannot as I don’t know what the issue is. This same definition was working earlier but when I added some Shapediver display components this issue came up- I’m now trying to add display to the other parts and see If the issue goes away. If not, I should be able to pinpoint the problem area and share a relevant definition file
Hi, is there a way I can show the changes that happen when a parameter is changed live in the app, instead of it just refreshing with the changes made?
I am not sure I understand your question. My best guess is that you would like to see the model updated in real-time when you move a slider, and not just when the slider is released. If that is what you want to achieve, there is no way at the moment. We could add a way to do this, but we do not recommend it as model updates can take a little time, and it would hurt the user experience to force updates of sliders tens or hundreds of times in a row when moving a slider.
Yes, that is exactly what I need- for my particular use case this would enormously increase the user experience. Is it possible to maybe limit this live update to only specific sliders then?
OR
Maybe have some sort of animation linked to this where the animation time is defined by when the slider is changed and released, and the change defines the animation movement?
If you are trying to show the rotation or translation of objects, or any other simple transformation which can be done in real-time in the viewer, you could use the viewer API to set them up. In the future, we will add components in Grasshopper to allow that.
If you are trying to show the evolution of a complex shape that depends on parameters of your definition, there is currently no good way to achieve what you want. We could add a slider mode in the App Builder that triggers updates as sliders move, but it would probably not be a good user experience (lagging because of server updates) and potentially hit rate limits.
Maybe you can describe your use case a little more in detail.
What you described should work for me. For my use case I wish to preview various operations like twist, rotation, scale and movement at different stages which I think should not be too complex to use the viewer API as you mentioned, I do however deconstruct and reconstruct my mesh to achieve these transformations (see the image attached). Would this complicate things?
I would need more information about what you are trying to achieve and the constraints of your project to help. In any case, at the moment, I do not see a way forward without development effort which will definitely require a developer background. Please contact our team if you want to discuss your project and how best to implement your application.
