How does Quick Drop determine its list?

[RavensFan]

Using LV 2018, I noticed something odd in Quick Drop that makes we question how it gets its list.

I'm looking for Obtain Queue.  I start quick drop and type "obtain".

When I get to "obtai", actually just "obt" works, I get this.

 

If I type the "n" to have "obtain" fully typed, I get this.

 

Obtain Queue or any Obtain is nowhere in the list.  Instead it is a random bunch of functions that don't seem to have anything to do with "obtain".

Very, very strange.  Any explanations?

[JÞB]

SCROLL down

It is assuming that you typed incorrectly. 

Darned automatic correction!

<sea story >

I once referred to a neighbor in a text by mentioning his car's model and color.  He is now known far and wide as the "Rectum Arrow" guy.

Yes, he drove a red Camero.

</Sea story >

I don't use quick drop 

[Hooovahh · Accepted solution]

Obtain Queue gets me everytime.  NI is using a non-G implementation to provide a list of suggestions and it has a few alternate words that can mean the same thing.  In this case the word Obtain could also mean Get, so suggestions give you the Get as well as Obtain but the Obtain Queue is buried.  If the sorting and suggestions were done in G one could try to fix it by prioritizing the Obtain Queue over the Get suggestions.  You can modify the QD list to show the Obtain first but only if Obtain is even in the list at all.  The suggestions are limited in their results so the thing you want might not even be in the list.

https://forums.ni.com/t5/Quick-Drop-Enthusiasts/QD-Oddness-in-Search-Obtain-Queue/gpm-p/3665060

Disabling relevant search in the settings fixes this but then obviously you lose that feature.

[crossrulz]

Yep, that relevant search algorithm does not prioritize well.  I have seen this a ton in LabVIEW 2016.  Can't say I remember this farther back.  But I used to have that feature turned off for some reason.  Maybe it was because of this...

[RavensFan]

Hooovahh,

What you say makes sense.  Now that you pointed it out, it looks like all the entries have either "Get" or "Find".  I don't see any of them say "obtain".  So I guess they are pushed so far down that they are beyond the cutoff point of the list.

I don't know why I hadn't noticed it before. 

[altenbach]

I probably would still prefer if the entries starting with "obtain" remain on the top of the list, even if all these "get" entries show up. (i.e. exact matches before synonyms)

[Darren · Accepted solution]

This is one of the reasons I turn off "Enable relevancy-based search" in the Quick Drop configuration options:

Another reason is that Quick Drop is slightly more responsive to fast typing when this option is unchecked.

[Hooovahh]

---

@Darren wrote:

Another reason is that Quick Drop is slightly more responsive to fast typing when this option is unchecked.

---

Lets pretend that's why you're faster than me.  But to be honest I have seen plenty of QD not responding for several seconds and maybe that is some part of that delay.

[JÞB]

Load pallets on launch rather than as needed and it will keep up.

I type too poorly to use qd for anything but built in qd shortcuts 

[paxtury487]

---

@RavensFan wrote:

Using LV 2018, I noticed something odd in Quick Drop that makes we question how it gets its list.

I'm looking for Obtain Queue.  I start quick drop and type "obtain".

When I get to "obtai", actually just "obt" works, I get this.

 

If I type the "n" to have "obtain" fully typed, I get this.

 

Obtain Queue or any Obtain is nowhere in the list.  Instead it is a random bunch of functions that don't seem to have anything to do with "obtain".

Very, very strange.  Any explanations?

---

what solution did you get? I feel I am facing same issue.