Man that looks terrible. Clearly I’m not getting the correct colour when I ask the OS what the default background of controls ought to be…
Logged here: RH-68167.
I’ve had this bookmarked for ages, wanting to try to set Rhino up to use these colours, but never got around to it - maybe something like this, David? Has both a dark mode and a light mode.
Thanks, VSCode also has lots of dark themes available for perusal that seem pretty well put together. But I wonder if a text editor just requires slightly different theme colours from a node editor… Anyway, if I’m fed up with fixing bugs some-day soon I’ll give this a whack.
Case in point, I need different fill colours for regular components, hidden components, and disabled components, all in both selected and unselected modes.
I will try to find good examples to provide!
But I think the colours you already selected work pretty well, and other people in the thread are liking them very much. As far as i can see it is more of a matter of approach: in most cases you take the outer edge of the icon and swap the darkest for the lightest in the gradient, but it simply does not work.
Out of the icons I picked here the ones that work best are Sift (which stays the same) and Log (which stays the same but with tiny white border). Combine and Square are just terrible, and Shake, Cull and Curve Planarity lose clarity (the lightest colours are very white and confuse together). I think the"stay the same" approach, with “thin contour” is a simple and effective way of approaching this.
Also, darkening the components a bit more helps as well.
After this changes I quickly tried photoshopping (not my strongest asset, ahem) a darker background for both modes.
I think it helps quite a lot increasing the contrast between components and canvas (see current state for comparison)
I did not know about the “?” feature, promptly noted.
Waiting for full functionality to be added and expanded.
Also… numeric range does not work? 
I have them all installed. I think the one displaying now is Menlo, the default monospaced for MacOS.
But having it configurable could be nice.
Forget about this. I forgot I had created an user object that I use all the time to add items to lists (with its little cute icon as well) and while thinking at the naming problem I mistakenly classified it as a default component whose function was 95% similar to Expand.
What do you get if you type something like 0..10 or 1..1000..#50?
This is how many people used to quickly spawn number sliders with a defined minium and maximum value. Now, it generates an integer range from the minimum to the maximum inclusive, which is kinda neat!
I always invoke sliders with 0 < 7 < 10 or 0 < 10, which always felt more natural to me and still works flawlessly! Kudos for that.
I get normal integer parameter containing first number before dots
They disappear… and rhino freezes…
This was a good move. +++
What does this mean 
???
This looks so exciting! I’m so pleased that you guys took the brave step to do a full overhaul. I can’t wait to get started with it.
Hi @DavidRutten and everyone involved in GH2, and thank you for your amazing work.
There are people who want to use GH but can’t or at least meet some serious difficulties because the interface is only in English.
Is there a way to make GH2 multilingual?
thx
The advantage though is that it is actually quite easy to find information when searching either here in the forum or using a search engine. If you have all commands, components, etc. localised, it will become much more fragmented and harder to find information, because you will likely then first have to find out what a certain thing is called in English.
As a german speaker myself I would be curious though how things like “graft”, “flatten”, “reparameterize” and some of those concepts would be translated without sounding super clunky.
Hi @DavidRutten ! Very cool that you’re working on this and I will definitely try it out once I have a bit more time in about two weeks.
There is one request that I would like you to consider to add, which is about the simulation of light. It would be really cool if you could add some of the functionality that Dialux Evo has, which allows you to do very accurate light simulations. Lights/luminaires are made available by manufacturers as simple files that just contain a small amount of data about the spread of the light beam and the light intensity at different distances. These can be imported into Dialux Evo so the light simulations can be done and suitable luminaires can be chosen. It would be super cool if it would possible to be able to import these same files into grasshopper and have the ability to do these light simulations in combination with the complete freedom in environment creation that Rhino and Grasshopper already offer.
Good luck in further development of GH2 and thanks for your great work so far!
The topic of metadata looks very promising to me. It hopefully opens up a lot of possibilities for BIM (improved Rhino.Inside.Revit integration, amongst others) and interoperability with GIS software (e.g. QGIS). Are there also plans to provide access to certain open databases, such as OpenStreetMaps directly in Grasshopper? In GH1, OSM and GIS functionality usually require plugins…
Here comes the cake. Question. Are you targeting net 5.0 or later or is it still bound on net 4.8? Most of the reaaly cool stuff is now on 5.0. Specially torchsharp tensors. We cannot use beta versions, because of stupid system admins…So I have to ask.