Disable component preview if there's nothing to preview

Replies to This Discussion

Permalink Reply by Andrew Heumann on November 11, 2016 at 5:55am

what does this accomplish, though? the list length component isn't going to slow you down if its preview is enabled, is it?

Permalink Reply by Pieter Segeren on November 11, 2016 at 7:06am

Thanks for your response Andrew, it's not about speeding up calculations, it's about easier 'readability' and neatness (my ocd, you may have noticed). I never understood why some components have the isPreviewCapable property set to True when there is nothing (ever) to preview, like for instance the mentioned ListLength.
My personal preference is to disable the components that don't output (or take in for that matter) geometry, that's all, and I'm trying to have that behaviour automated somehow. Because of Human and Metahopper I guess you're the man to ask:) Do you think/know my goal is achievable?

Kind regards, Pieter

Permalink Reply by Andrew Heumann on November 11, 2016 at 7:45am

I personally think that's silly! BUT here you go anyway :-p

GrasshopperDocument.ActiveObjects()
.OfType<IGH_Component>()
.Where(
comp => comp.Params.Output
.SelectMany(p => p.VolatileData.AllData(true))
.All(d => !(d is IGH_PreviewData))
).ToList()
.ForEach(comp => comp.Hidden = true);

Permalink Reply by Andrew Heumann on November 11, 2016 at 7:50am

apologies if my long linq statement isn't super readable. To break it down:

1. get all the active objects in the document

2. get all the active objects that are components

3. get all the components where all the volatile data in all their outputs is not preview-capable

3. for each such component, set it to hidden.

Permalink Reply by Pieter Segeren on November 11, 2016 at 8:05am

I'm really greatful for that really cool code and your explanation Andrew! Yay!
n.m.: Did you mean my intended approach is silly, or did you mean that my goal is?

Permalink Reply by Andrew Heumann on November 11, 2016 at 8:06am

The goal :D :D :D Just my opinion. Everyone is entitled to their own OCD!

Permalink Reply by Pieter Segeren on November 11, 2016 at 8:12am

Ah, I thought you were going to say "both" :)

No really: thank you! Have a great weekend Andrew.

Permalink Reply by David Rutten on November 11, 2016 at 8:11am

I never did understand how anyone with even the mildest form of OCD could possibly stomach LINQ statements...

Permalink Reply by Pieter Segeren on November 11, 2016 at 8:26am

:) I'm just happy that the code is working right out of the box, of coarse I'm going to see what I can learn from it and how I can vanillafy it.

Permalink Reply by Andrew Heumann on November 11, 2016 at 8:45am

vanillified:

var activeObjects = GrasshopperDocument.ActiveObjects();

foreach(IGH_ActiveObject ao in activeObjects){
var comp = ao as IGH_Component;
if(comp != null){
var outputs = comp.Params.Output;
bool hasAnyPreviewData = false;
foreach(var param in outputs){
foreach(var data in param.VolatileData.AllData(true)){
if(data is IGH_PreviewData) {
hasAnyPreviewData = true;
break;
}
}
if(hasAnyPreviewData) break;
}
if(!hasAnyPreviewData){
comp.Hidden = true;
}
}
}

personally I think the first one is conceptually much clearer! There also may well be a prettier vanilla ¯\_(ツ)_/¯

Permalink Reply by David Rutten on November 11, 2016 at 10:16am

Yeah tastes definitely differ. Lots of people seem to like Linq and unfortunately many, many algorithms online seem to use it.

Yours is at least relatively readable, often times the legibility of a Linq statement seems to approach Regex levels of nope.

I may come around though, I've started liking careful use of lambdas and anonymous statements over the past few months.

Permalink Reply by David Rutten on November 11, 2016 at 8:10am

List Length has a Generic input, which, if it contains previewable data that didn't come from elsewhere will preview. Any component which could potentially draw a preview has preview enabled by default.

• ‹ Previous
• 1
• 2
• Next ›
• Page