WISH: Make Auto-Complete Prioritize Suggestions by TOTAL Usage Count

I am so tired of dealing with Rhino’s auto complete…

I have been dealing with surfaces recently, so I have been using OffsetSrf quite a bit.

Now I am done and I am back to curves.

image

I have to type the entire Offset word because the stupid auto complete types in OffsetSrf because I have been using it recently.

I am pretty sure I use Offset way more, like x10 times more than OffsetSrf. Just because during a single day I typed OffsetSrf more than Offset, auto complete now prioritizes OffsetSrf. How can a single day of work take priority over my entire Rhino usage?!

Same happens with DupEdge and DupBorder. I haved used DupBorder so many more times in total. Yet it auto completes to DupEdge everytime because recently I have been Duplicating Edges…

PLEASE. If someone at McNeel still has some common sense, change it to TOTAL usage count.

Also, if I have curve selected, I am not going to use OffsetSrf now am I? It is time for auto-complete to become smarter.

We have got all types of AI tracking our habits and giving recommendations, I think you can do better than a simple count that gets erased every week.

1 Like

There’s actually no “common sense” to that at all, it’s an arbitrary thing that you don’t like. The entire concept behind the fuzzy auto-complete is contrary to the most basic concepts of interface design and has NEVER been good. The interface should be CONSISTENT, not constantly rearranging itself to try to read your mind about what you want.

1 Like

@JimCarruthers Fuzzy autocomplete is something else, that’s about typing something like fse and getting the closest suggestions
image

@ShynnSup if you use Offset a lot, then it makes more sense imo to make an alias for it. I have of and os as aliases for Offset and OffsetSrf as I use them both often.

Did you try out changing these settings?

Will try those options, thanks.

There should be an option to reset it.

Also it should no complete to an entire command if there is a previous command with the first word.

For instance OffsetSrf

If you type O it should complete Offset. Then if you type S it should complete Srf. This way if you wanted Offset alone you are fine with just typing O. But right now it completely skips Offset and auto completes OffsetSrf altogether… which is pretty dumb if you ask me.

I see what you mean, just did this small test:

I ran OffsetSrf 5 times, typing off
first time it Shows Offset
After running OffsetSrf it starts to show OffsetSrf instead.

then I tried Offset, by typing off
it autocompletes to OffsetSrf 5 times before autocompleting to Offset again.

I haven’t designed this tool, so I am not entirely sure how it works, but a reset would certainly be handy. Maybe @brian can shed some light on the workings of it and if there is a way to reset it.

I tried Rhino.Options.AppearanceSettings.popularity_based_inline_autocomplete = False, but that did not stop OffsetSrf from autocompleting.

1 Like

Command use counts are stored and your settings.xml file and are used to influence autocomplete.

In my opinion, the autocomplete must prioritize the shortest possible command, followed by a list with all the remaining commands that include both, the original word and the additional letters behind, in an alphabetical order. Or, at least add such an option, so that Rhino users could decide which behaviour they want to use. Example:

Note that the screen-shot shows some quite clever arrangement of the commands, where they are listed alphabetically to include the two letters “zo”, then, as a separate sub-list dividev by e blank space, extra commands are shown that include only the letter “z”.

However, I still see some room for improvement, because the aforementioned list does not offer “Zoom extents”, “Zoom dynamic”, “Zoom selected” etc. All these UNLISTED commands are way more often used than “Zoom1To1Calibrate”, “ZoomNonManifold” and so on.

1 Like

Agree, this could be a possibility too. Anything would be better than current.

1 Like