Hi,
I have a python component that takes all dots in the document and spits out their coordinates.
My question: how do I make it so that when I move a dot, the python component runs to update it’s output?
Thanks
-Willem
The best way would be to feed the points to the script via a normal GH Point “Param”. They listen to document updates.
Giulio
–
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com
@Willem, i tried first to reference the annotation dots as @piac recommended but i was not able to pick dots only point objects. Referencing guids worked but it did not update.
If i a timer is allowed and you do not want to reference each dot, you might try this:
c.
Oh I see, I did not think that the point Param does not accept Dots.
This could be a wish for @DavidRutten.
If you are using Rhino WIP, this will be a lot simpler to set up, otherwise, in Rhino 5, it’s a bit tedious and error-prone, but also possible. I much rather would only try to figure out the Rhino WIP way.
Please let me know,
Giulio
–
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com
1 Like
Hi Giulio, i was testing with the WIP. Can you reference a Dot using the point component ? I am not able to repeat this. It works with Guid component but does not seem to update when the Dot is used. (Which i find OK as the Guid did not change).
c.
It will starting with next week’s WIP.
2 Likes
Nice addition 
Hi Clement,
Thanks for the tip. It’s a rather expensive definition so an update every X time will do more harm than good. I opted for a dummy input from a button component, a toggle of the button will update the button. So I’ll just manually have to update.
-Willem