Hi, it would be great if you added more colors.
Hi! It is difficult due to some grasshopper limitations. I am using standard palette. Maybe some time in the future I will change the approach and it will be possible
Sure, thanks a lot for the reply! I thought about it because of the limited readability when there are a large number of inputs
dear @dfytz1
I did not use telepathy for a couple of weeks + weak memory, so forgot how it works.
A shortcuts list / bit of help would be great.
For now the only one I remembered/reread here is Command + t (mac)
Searching now on: how to (after selecting a slider + then Command + t) get the name of that slider to sender and all receivers. ?? There must be a way to do so.
Regards, Eef
Hi Eef! Glad to hear from you.
There is only two shortcuts for the whole plug in.
Selected component + Command + T = Create sender receiver for component outputs
Selected sender/receiver + Command + T = Select all telepathy components sharing the same name, + repeat to zoom canvas on each of them.
Command + Double click telepathy sender/receiver to create matching receiver/sender
Hope it helps
thanks. That is already a relieve 
I also discoverd something about names of sliders.
- If no name is given, it gets the name of the connection (connected to)
If I then use Command T the slider gets the name of the sender - If a slider has a name, it is the other side around.
Normally this would only happen when using Option when connecting a wire.
This got me a bit confused. Not very clear, but I hope to rembember untill next time
Sliders change their name automatically based on input they are plugged in.. And its not the same rename as when you do it by hand. So yeah, I suppose there will be some inconsistency in the behaviour. But I am not really sure how to work around that, and if that worth any effort. My personal usecase - name slider/component outputs, select + cmd + t. So i never encounter that problem.
It would be good if there was a way to rename the sender along with the rest of the receivers of the same name, so you can rename it right after creation. But i am not sure how to approach that, its very good in the beginning but unintuitive and asks for trouble in the rest of the usecases.
what maybe could help:
Case: Imagine you have a group with more components (including senders receicers), you want to copy/paste elsewhere. To avoid double names, you want to rename several componts.
An option what I would use is:
- rename slider/component
- re-wire first sender with Option selected.
That will rename the first sender. It would be nice (maybe already available) if the complete group connected receivers, would be renamed at same time.
Yess More colours, please 
Also, when I change a colour of sender, I loose connection to receivers.
Workaround - select all components, change colour of one - and it works.
Is that intentional?
Try to use command(ctrl) + T shortcut. When your sender/receiver selected, you can press that to select all of them and then change the colour.
That is intentional. I know its not very handy, the same - when you change name of the sender it disconnects from receivers. I did not find a better workflow. But it feels slow only on the first stages; when you have a big definition - control and predictability becomes priority.
I need to think about it, I am afraid about scenarios where you copied part of algorithm and want to change its colour, or when you want to disconnect something, but now you can’t
Love the plugin! I can’t get the keyboard shortcuts to work though (RH8 on win 11), and it doesnt show up in the settings panel where you can assign shortcuts. Any idea as to what the problem could be?
I went ahead and solved it myself, I’ll attach the file here in case anyone else were having the same problem
Telepathy_Rhino8.gha (54 KB)
Telepathy_Rhino7.gha (54 KB)
You should be able to change the shortcut under the interface settings in GH with this ver. now. I also added a few more shortcut options.
Love to see that! Since i do not have a windows pc, its kinda difficult for me to test what is happening there.
I have problem, I don’t know if the mac version has it, but when you are working with mutiple monitors it sometimes there is a bug where you start to type into grasshopper and you end up writing on the rhino command line instead of grasshopper, like if windows lost focus of the grasshopper screen.
And that is making impossible to use the shortcuts, because the ctrl click goes straigth to Rhino instead of grasshopper.
Could a Telepathy2 dropdown be added to the top banner (where File, Edit, View, etc resides) like the guys from eleFront did.
Pretty please?
Hi Altamiro! I am currently very busy with some other projects, i will come back to telepathy in 2-3 months probably. Will add some things that were discussed above in this thread (like shortcut setting in gh). Adding the menu you mentioned is very easy; testing if multi monitor set up works on windows - difficult for me 
No no, the multi monitor problem is something from grasshopper itself, thats McNeel’s problem, not yours, just having the menu is the perfect workaround. Thanks
Something strange happened, and not (yet) able to reproduce.
My Mac crashed, so maybe the file got corrupted. This is what happened.
In this file are 2 senders with same name (that is what I discovered later, so probably a mistake of myself).
And there are many receivers.
After the crash 3 or 4 of the receivers turned into senders, so they did not send 1 item, but there was a list of 5-6 duplicates.
Maybe someone has a suggestion how to fast “undo” this (I now had to delete the false senders, and connect to first source. ) So problem solved.
I guess I have copy/paste a sender somewhere in a group, creating two senders with the same name. They could co-exist until this crash and “automatic repair”
No idea how to prevent this, (forbid to have two senders with same name +colour? and give error)
Just loudly “brainstorming” to get some idea. Regards, Eef
My guess is that the sender got overwritten following the grasshopper processing logic.
At least, that is what would happen in regular programming, so visual programming must be the same way, I guess.
So maybe forbidding is not the right patch to take, but at least create a yellow warning telling that the sender gets overwritten or is overwritting something.
edit: typo proramming → programming.