Telepathy S

Telepathy is not supported for a long time already, so i made a version for myself with some extended features - like

  • convert multiple existing wires into telepathy components
  • delete all telepathy components and replace them with normal wires before sharing the document with someone who does not have the plug in.
  • delete telepathy components that share same key and replace with normal wires
  • search keys
  • optimized performace through cashing (2048 recievers on one screen - 37 fps on M2 vs 17 fps in original telepathy)
  • Zoom cycle through key components (Same shortcut) (Idea by Eef, thank you)

If you have any ideas i would like to hear. Also report if you find bugs.

:backhand_index_pointing_down: :backhand_index_pointing_down: :backhand_index_pointing_down: :backhand_index_pointing_down: :backhand_index_pointing_down: :backhand_index_pointing_down: :backhand_index_pointing_down:

The plug in works with your definitions that contain old telepathy

GHA:

ACCESS THROUGH PACKAGE MANAGER

  • Added group colours (components look for same name components only in the same colour group)
  • Added shortcut to create senders and receivers automatically - outcoming from selected components
    mac command + T
    windows control +T
    pressing shortcut with telepathy selected will select all telepathy components with that key and colour.
  • Fixed how some undo redo operations work


The larger the definition the more useful the thing becomes:

Explode telepathy:

One menu to replace keys and edit current key.

Test with 2048 components gives 37 fps vs 17 in original telepathy:

Looks great! Do you intend to put it to package manager as well?

Thank you! No, its too big of a hassle, i made it primarily for myself, for quality of life. I will update the component here in the main post from time to time, in case anyone needs it.

Its in the package manager

Recievers support more wildcard matching patterns than the original (it supported only ? and *)

and no problems with that:

Np. For convenience, can you add version nb or update date in text next to gha file

*hassle

Hello, from experience, Package Manager is not an hassle, food4rhino could be.
For my Nautilus plugin, at each compilation Visual Studio write all the files (gha dll …) in a directory (named food4Rhino)


Then to put that on package manager I have a little file that helps me to to the operation

So update the manifest, the only thing to do is to change the version number

Then open a dos windows on the directory RUN

  • “C:\Program Files\Rhino 7\System\Yak.exe” build
    it will generate a file
    Run

  • “C:\Program Files\Rhino 7\System\Yak.exe” login

It will connect to your account
Run don’t forget to put the good Yak name

  • “C:\Program Files\Rhino 7\System\Yak.exe” push nautilus-2.0.0.7-rh7_38-any.yak
    it will send your package

So the biggest work is to publish on Food4rhino in order to have a validation from McNeel

Thank you Laurent! Honestly i did not research this too much, because I do not think that many people would be interested in the plug in.
But thank you, maybe i will do that later

Hello
I still use Telepathy for myself and my client. It is a great tool I think it is quite used but as it has a low number of components and didn’t evolve too much the number of downloading doesn’t reflect the userbase. it could be a good thing to know the real number of user for each plugin.

I know what it is, plugin creation is not really rewarding (I speak for myself) so I do it mainly for myself.

It was easy indeed.

@dfytz1
Great job you did with telepathy.
Now trying to include it into a bigger job I am doing.
If I may as a question here?

  • is there some kind of manual (besides what you wrote above)?
    I am now specially interested in this:
  • Is there a way to jump from sender to receiver(s).
    The only way I see now is to use : Ctrl F

Regards, Eef

Hi Eef!
Nice to hear it might be useful to you.

I did not make any manual, because i was making the plug in for myself. Also it is pretty simple and i do not think it needs much explanation. I will share a few more insights with you, about things that might be a little bit more hidden:

command + T shortcut (the most useful thing to me); Creates pair of sender/receiver from outputs of a component. If it is connected to nodes downstream, creates receivers for all downstream components. If sender/reciever selected, pressing same shortcut selects all components with that key and colour.

in the Key UI window after replacing some keys someone might press Apply instead of Close, and it will rename the node unintentionally (I do not know what would be a better solution in terms of UI).

Colour groups are made so user sees when command + T shortcut creates components with same names. After we run out of colours it starts appending:

Components search only within same group colour.

Everything else in my opinion is as simple as it gets and does not require any more explanation. No hidden features there.

No way to zoom to components in the current implementation. I am not sure how this would work, if you have any ideas please share.

Thanks for your fast reply. I found command-T and differrence between apply/close :frowning: (no damage done).

There is also the component jump what works in pairs (and also in a bit larger groups. Just clicking jumps to the next with the same name , etcetera,
In grasshopper view there is Zoom Selected. That can maybe be used:

  1. After clicking->
  2. Select next item in group
  3. Zoom selected.
    Maybe that is an idea to use?

Regards, Eef

Ughhhhh maybe i will replace it to something like this in the future..

About zoom.. I am not a big fan of how its made with search/jump, i do not use any of these. And for this to work:

it has to be either double click(occupied) or right click (too many clicks) to work right away.

In theory it can be added in the UI menu, but again, it means cycling through dozens of components with the same key..

OK. let me brainstorm a bit more.

  1. You allready have the option to select a courgroup.
    What about circling around in the colourgroup (or all items with same name) what can be many (in big projects),
  2. Select all in the group at same time, and zoom out, so you see where they are globabally located on the canvas.
  3. I did not mean search/jump (what could be option to. In fact already available) but:
    Select component → Shift Z

oh, shortcut to cycle.. okay why i did not think about it? I will try to do something like that. can be useful

Perhaps something like that? I updated the plug in in the package manager. Press same command + T shortcut to cycle through components

Updated menu button too, so its less confusing:

I want to ask your opinion on something. When we copy sender, should it become a different colour group right away? Or It should send data right away..
Because right now to make it send data to same receivers you have to rename it. It is safe behaviour to not send duplicate data when copying to create a different sender for example. At the same time I feel like assigning it different colour right away would force user to go and change colour back to blue. Changing its text feels off too. What do you think?

Somethings to think about longer (and ask more users, because I just started using it).

-maybe I should explain how I want to use it (as a replacement of some methods I use now:

  • I work on a technical design with lot’s of measurements to be set, like “tolerance”, what is used on many places. Now my design has lots of wire + relays to reach all those inputs. I would like to use TeleP to replace all these wires + relays in one move. It should update immedeatly, so the functionality stays the same. Name + Colour may be default at first. I will probably rename/recolour these as my design grows (and for example I get a second tolerance, etcetera).
  • When I set up a new design, I now start with a long list of sliders + names + settings, for all the measurements I allready know. Instead of relays, I would like to use TeleP senders there, what get there name with Option + connect wire.
    Later when working on the design, I now have to connect a wire + relay and pull it to the correct place. (if I have many I will entwine them and BANG them at the destination. I love the Set Key list, what will make my life much more easier. I can now place a receiver. And then I will search in Set Key for the correct one. Name + colour should be copied (what already works like that).
  • Often I have to split a measurement in two or more, I have to be carefull there, to disable a relay in the wire first. This to prevent that my canvas goes nuts (for example to prevent that I get a Solid Diff from a Brep with itself (ending in a frozen Rhino). So copy pasting a Receiver, would be good to set default to Not Active. and activate when correctly placed.
    I hope my explanation is a bit clear, it is hard to analyze + describe your own working methods :wink:

Regards, Eef

PS:
Maybe in set key double selection list: name key + colour of key ?
It is like first + last name selection
How I would use this:

  • Somewhere I decide to create a new tolerance in a cloned group components.
    I copy past the components including TeleP. And set the tolerance (for example: Tolerance + Blue) to colour Brown. (I now have a receiver without sender)
    I go to my init_list, make a new sender. Set Key to tolerance + brown. Done