C# ScriptEditor is still a Pain... Everywhere

@RIL wrote:

Scripting C# with the ScriptEditor is still a pain. The Search Dialog behavior is killing me. I had hoped for it to be fixed in R6, but not so, not so.

< rant >
Before two decades ago any Windows Search/Replace Dialog was capable of

1. …picking up the selected word/text on CTRL+F / H. Everytime.
   Not only the first time but also next time if something else was selected before pressing CTRL-F/H again. This usually works, but it stops to work as described in §2 below.

2. …always putting Focus on the first Edit Field in the Dialog.
   If ticking the “Find Options” then Focus is not regained on CTRL-F/H, and also §1 stops working. CTRL+H doesn’t switch from Search (CTRL+F) if the dialog is open, and vice versa. This zombification of the search dialog drives me nuts, if I’m not nuts already.

3. …refrain from changing the Search scope (“Look in”). Ever.
   If I set the scope then I want it to stay there until I change it. Don’t fiddle with it. Extra reasons why not tampering with it automagically is described in §4 below, which explains why any automagic chnages forces you to Mouseclick it back to desired scope, although you are both hands on the keyboard

4. responding to the TAB key. So the Tab key really isn’t working in the Search/ Replace Dialog.
   It works only for tabbing down from the Find/Replace-Tabs and between the two Field edit boxes, but not tabbing further down to Selection scope (“Look in”) or Find options. This forces users to leave the Keyboard to grab the Mouse in order to Click my options, a zillion times a day. And worse yet, when I have set the Selection scope over and over again by grabbing the Mouse, then it will most likely change automagically again next time I press CTRL+F/H, and so I will have to grab the Mouse again and…

No good. No good.

< / rantings & ravings >

One good thing though in R6 is that you seem to have fixed the Goto (row) dialog (CTRL+G, which could lock up the search dialog AND THE ENTIRE ui if it was open at the same time).

5. Only problem is that I just tested that again as I was typing this, and guess what? Pressing CTRL-G while the Search dialog was open again locked up the Rhino/Grasshopper UI beyond recovery. Had to kill my Rhino process. Hm.

I spend day and night with this code editor. And it is becoming more and more disturbing. It hurts.

// Rolf

Edit 1: The Goto-disaster is an old one:

Edit 2: This time I lost the Goto dialog (behind somewhere) and only the Search dialog is visible, but stone dead and so is Rhino & Grasshopper UI. I must write this text in the space below the silly dialog that got stuck in the middle of my screen.

bild.png731x486 31.2 KB

Posts: 13

Participants: 6

Read full topic