Split AHSV component is actually AHSL

Replies to This Discussion

Permalink Reply by David Rutten on December 17, 2014 at 9:58am

Will do, thanks.

Permalink Reply by Gwendolyn on March 14, 2017 at 4:10pm

I just set up the same components as in the picture, with the same results. Did this never get addressed?

Permalink Reply by David Rutten on March 15, 2017 at 3:00am

Apparently not. I think I decided I didn't want to change the behaviour of the existing component, lest it change the behaviour of existing files. But I just renamed the existing one to match the output values, and added new components that work correctly.

This should become available in Grasshopper in RhinoWip sometimes after I merge these changes into the official version.

Permalink Reply by Gwendolyn on March 15, 2017 at 8:06am

Thank you once again for the swift implementation! Since I've been having terrible frustrations with this HSV/HSL problem for weeks now, I suppose this will finally nudge me towards using the WIP (unless you felt like additionally providing these components for the Rhino 5 Grasshopper, but that's entirely up to you :p).

Permalink Reply by David Rutten on March 15, 2017 at 8:53am

I can't release them for Rhino5, but you can certainly use some C# components that do the same.

Edit: actually no, HSV doesn't seem to work well at all. There's bugs in the colour convertor code in Rhino. This needs more looking into.

Permalink Reply by David Rutten on March 15, 2017 at 3:29pm

Ok, I found the bug in Rhino to do with HSV colours, so the attached file with C# components will start working when the next Rhino WIP release goes out. But then when that happens you'll also get the new components, so that won't help you.

I'm afraid if you need to solve this in Rhino5, you'll have to code up your own HSV -> RGB -> HSV algorithms in a scripting component.

Attachments:

• huespaces.gh, 28 KB