Inconsistent Rhino tool UX

Rhino Rhino for Windows
,
1

I’ll start with the two major ones I fight with every time I use Rhino:

  • BlendSrf has a nice symmetric tension slider, BlendCrv does not.

    image
    image364×403 11.6 KB

    image
    image228×376 8.08 KB

  • With Trim you select the cutting objects first, with Split you select them second.
    image
    image

  • ExtendCrv continues the command after the first extension, ExtendSrf does not.

And a bonus from 4 years ago:

  • With MatchSrf you can match two (or four) sides of a surface. With Match you can only ever match one side of a curve. (Rather, Match is missing the MultipleMatches option from MatchSrf… also, the fact that it’s not named MatchCrv is another inconsistency.)

Also, regarding history:

  • There seems to only be a single command in all of Rhino which allows History edit, and that’s BlendSrf and BlendCrv. But that should not be removed to make it consistent with all other commands, rather all other commands should also have the edit functionality!
2

I totally agree on hating those.
I set up the
inconsistency
Tag - you may want to add it to the topic as well.

Regarding blendsrf:

I hate that blendsrf will automatically switch to 2nd edge when selecting a closed loop - which is great- , but subd bridge does not.

ExtrudeCrv
I hate that mouse position matters for z direction.
Pure keyboard input is not possible.
Extrudecrvtapered , box, and many other commands do not care about mouse position.
In my brain finishing a command with a mouse click - mouse position can influence tge result. But pressing enter mouse position should not matter.

There is many more:
Some tools/ commands allow interacting for example with the layer manager - while dialog is active/ others don t.

Window hierarchy / input focus is still very painful, for example script editor is front most but it needs an additional click.
Some dialgues finish if you press enter, other’s do not care about focus behing changed

…
Many more.
I gave up reporting them.

But i would love to have at least the top 50 of those inconsistencies beeing addressed before rh9 ships.

@mcneel do a search with inconsist, counter intuitive, or similar… this forum and youtrack is full of them.

Would be great to see some improvements here.

Thanks

Happy Eastern - kind regards-tom

4

Thanks @eobet @Tom_P

I will definitely start collecting these for Rhino 9.

5

Rhino V8 macOS - Settings… in one place, Options… in the other; why?

6

Rewriting that part of Rhino for Mac is not scoped for Rhino 9 unfortunately. It’s a massive and also risky task.

7

It’s only changing a word in the interface. Both menu selections bring you to the same location.

8

Sorry I clearly misread your comment. So it is about this being named incorrectly, right?

image
image628×420 49.9 KB

9

Rhino 8 > Settings… (menu)
Tools > Options… (menu)

Both open “Rhino Settings”.

10

thanks,

Yes I think that that and the Title of the dialog it opens should be consistent with Rhino for Windows, and called Options

11

Yep, same things, wherever in the program, should be called the same : ) because such things can really throw off novices or those transitioning to Rhino. I have also seen on various manual pages or tutorials that, for example, “points” sometimes refers to CPs or Greville points or ends (curves). I believe it’s important that things are consistently called out by their beautiful name : )

12

Another naming inconsistency that always gets me:

In Grasshopper creating a surface from curves is called BoundarySurface, but then in Rhino its just called PlanarSrf. It would be cool if typing “Boundary Surface” would also get us to PlanarSrf and vice versa.

image
image715×320 12.6 KB