Autorelay is way overdue.
Iām using v4.2.2 and had the beta installed next to when it was first released but didnāt like having some of the commands twice. Reading the descripition in the package manager v4.3.0 might solve this problem?
In order to avoid compatibility problems with my existing definitions I would somehow prefer if I could test the new EleFront in Rhino 8 WIP.
@tay.othman and @JoostGevaert ā we donāt use relays internally to organize definitions, we use the data descriptions with variable names as standard practice, so I can tell you that is why relay interaction has never made into eleFront. It would be great if you guys could educate us on how you use them and what would be valuable so we can think of ways to integrate functionality.
1 Like
Thanks for the reply Evan,
I first started cleaning up my messy scripts with AutoGraph and fell in love with it, especially because of
- Hotkeys (Looking forward to user defined hotkeys in GH 2)
- Automatic naming of the data descriptions.
Apart from these two functionalities, I see no advantage of AutoGraph over relays, with which you can also organize your GH script and give names to the data in the wires.
I would love to be enlightened however 
The main two drawbacks of AutoGraph for me are:
- Some people donāt like my scripts, because they like to keep the number of plugins required as low as possible.
- The Data Descriptions do not by default display the name of the Data Description, while many people use the Display > Draw Icons setting (I also like it more). Therefore, the utility ādescriptionā part of AutoGraphās utility falls away for me, unless I manually go around the entire script to select the āAlways draw nameā option of the Data Descriptions.
I recently started organizing my scripts with native Params and Relays as shown in the screenshot below. (I can unfortunately not share this script, but I could share a minimal example if you wished.)
Then there is also the ShapeDiver way of organizing GH scripts: How I Keep My Rhino Grasshopper Definitions Organized | 4 Productivity Tips! - YouTube. Which uses native Params with the āAlways draw nameā selected and invisible wires between groups.
@elevelle, would love to hear your thoughts
1 Like
Getting my script uploaded to a cloud tool like shapediver didnāt like my script either due to data description.
My take on relays:
Pros:
- easy and fast to create (double click wire or connector)
- Compact. Take up less space than data parameters
- Names are always visible regardless of any other display settings
- Names are inherited by connected relays
- Easy to delete
- Native component
Cons:
- Cannot preview contents or flatten etc
1 Like
Hi @dharman @tay.othman @JoostGevaert
Thanks for the input! Longer term we will look into integrating relays as an option in the future as I can see the benefit for people, but it is not on the immediate roadmap as we are wrapping up the beta in the next few weeks and are focused on porting the last few features from the R6 version and killing of the remaining bugs. Since we did a full re-write, it has taken a bit longer than we wanted, but those are the breaks when managing project work as well!
Anyways, to immediate issues we have broken the link between Autograph and eleFront and move the data description back into eleFront, with integrated hot-keys for propagation of these components. This means:
- Hot Keys have been implemented in GH to add/propagate the data description parameters
- Automatic Naming of data description
- Names are inherited by connected data description components (this has always been a feature)
- Autograph is no longer required
- Preview/Flatten/Full suite of parameter options are available (plus extra ones for eleFront).
All of this is available in the current beta.
This doesnāt address all the issues, hopefully is a good middle ground while we look it updating this bit of the plug-in. The data description parameters preceded the introduction of relays by McNeel as we needed something to help keep our scripts clean and organized and it has since become our default way of working, even after relays were introduced that offered some of the same functionality, hence the questions.
2 Likes
@elevelle I really appreciate your insights and consideration regarding the relays. I believe that Quick relays should be considered by mcneel as well. I already placed a request last year. Probably it wonāt happen anytime soon. Unless I learn C#.
Yep, thatās is pretty much the sole reason for 4.3ās existence, to help distinguish between āoldā components and the forthcoming new ones when you have them side by side.
Regarding the Rhino 8 WIP, the new version does work there, itās just not in the Package Manager. Iāll make sure to include the Rhino 8 flag for the next update. In the mean time you could set your Rhino 8 GrasshopperDeveloperSettings to your local folder that contains the elefront beta, if you like.
1 Like
Moved to new topic
The Define Object Attributes component in the Beta version is missing the Material input. Can this be added please?
Iām also missing the Duplicate Data Match componentā¦ I figured out I can use the Cross Reference component instead but the Duplicate Data Match component was niceā¦
2 Likes
Yeah the Material input is one of the most requested features. Itās a bit tricky because McNeel has changed how Materials are handled since the v4 components were written for Rhino 5. Itās taking some time to get it right, but should be in the next update (this month).
And yes, Duplicate Data Match hasnāt been reinstated yet, though I believe itās functionality can be replicated with Cross Reference, as you mention, or Longest List, and some others. For that reason I do have to admit itās at the bottom of the list.
1 Like
Duplicate Data Match: Thatās fine, I figured out it can be done with Cross Reference quicklyā¦
Regarding materials I think it would really make sense to have the option to add a material as attribute. Iām using EleFront in my climbing wall algorithms and a large climbing wall can consist of hundreds of different panels which all need a material. Filtering parts and changing the material is very efficient with EleFront.
1 Like
Hi @elevelle,
Are there any plans to expose the auto-update for the reference components to Boolean Toggles or by clicking a button on the component itself, instead of right-clicking these to enable live updates. Makes it more insightful in which mode they are too.
E: Is it me or is the auto-update feature not working for the Beta?
1 Like
Hi @Intuos - right now there is no immediate plans alter the access to the auto-update feature. This is a design choice on our part as when you are working with large models, the experience can become very poor, very quickly if auto update is left on.
You are correct in noticing that the auto-update feature is not working in the new version yet. This feature hasnāt been ported over yet. It is on the list, however.
2 Likes
I understand. I usually use the auto-update during the concepting phase, after which I would turn it off and resort to the manual update. I think being able to switch between auto-updates on/ off easily, scripts can become more flexible in transitioning from the concept phase to the next. Just for a bit of context on the request. 
1 Like
Is this a bug? Or am I just doing it wrong?
Goals
- I have an external 3dm file that I would like to take block instances offā¦ Or layer instances. Either would work.
Problems
- RefBlock component will not find any blocks (There should be around 52 in that doc.)
- Ref layer is still stuck on the open file.
I do have the correct file path connected.
To check the file path, I used the Import3dm component and it imported all the geometry. (except the blocks obviously.)
Here is a pic of the problem. I canāt share the file because this is technically owned by the company I work for.
Anyways, some guidance would be appreciated. 
Works for me.
Are you sure your blocks are on the Default layer, or named One?
1 Like
@richard.aubin
So sorry, should have updated.
I had each blockās exploded geometry on an individual layer. I was trying to reference those layers to create a block from each of those individual layers to then place in the document.
So, I think it is because I had nested blocksā¦ I was able to explode all the blocks, rename them and place them in the reference document again. (I also purged all the old block references) Now I am able to reference all the blocks from the file. I have not tried the reflay component again simply because I did not need after I figured out the blocks.
A lot of trial and error today lol. I think Thomas Edison said something like
I have not failed. Iāve just found 10,000 ways that wonāt work.
Thanks for looking at this for me though! It is much appreciated.