Prevent C# editor from minimizing and being opened multiple times

Hello,

Can I prevent the C# component editor from minimizing (reducing in scale) each time I click outside the editor? I would like to see the script even while I'm moving through the rest of the Grasshopper definition. Also, sometimes it might be useful to read several C# scripts in parallel (maybe to compare the two), which doesn't seem possible...?

More importantly, I've noticed it is possible to open the same script multiple times...I am new to C# but this seems like a potential source for huge mistakes and loss of code! It appears that the component saves whichever version is closed last (by clicking "OK"). So if I have been working on one version for a long time, and upon closing it realize there is another (older) version opened, and by mistake click "OK" on that one - all my previous work on the other version will be lost, right? Hasn't this been a problem for anyone? I'm used to working with GHPython where things are a bit different, so maybe I'm missing something.

Cheers,

Max

PS: The Python component editor shows you through dashed lines on the canvas which component it is that you're working on, and also disables itself and throws an error message if you delete the component. This can be pretty helpful - any chance this functionality could be added to the C# component?

Replies to This Discussion

Permalink Reply by David Stasiuk on June 29, 2016 at 3:03pm

The first concern you can address with the widgets in the upper right corner of the script editor when it's open...it's the right-most one called "Shrink Script Editor." It defaults to being checked, but you can uncheck it, and your script editor will stay the same size (it will also change your preferences and become the default automatically, which is nice). Up there is also the "Run Script" widget, which is great for testing results, if you weren't already aware of it.

The second concern is annoying for sure...as far as I know, there isn't any way to deal with it other than to be very observant about changes you're making to your scripts, and make sure that you just cancel out any versions you don't want to save.

Permalink Reply by Max Marschall on June 29, 2016 at 3:27pm

Fair enough, thanks for pointing that out.

Permalink Reply by David Rutten on June 29, 2016 at 3:45pm

Yeah it's a bug serious enough to be on the fix list for GH1. Although since no more releases of GH1 for Rhino5 will ever happen you'll have to switch to Rhino6 to (eventually) benefit from such a fix.

And indeed the current code editors are absolutely atrocious. I've been lobbying for a long time with McNeel HQ that we need a good, universal, consistent code editor for all of Rhino, and I'm glad to say that stuff is getting interesting now. Alain is working on a back-end agnostic SDK and I think both Atom.io and Visual Studio Code are being considered as potential engines.

Permalink Reply by Max Marschall on July 1, 2016 at 4:14am

Cool, good to know!

Permalink Reply by David Stasiuk on June 29, 2016 at 3:04pm

David has also said several times in the past that the script editors for GH1 are what they are, and we'll have to wait for GH2 for improvements.

RSS