Add Intellisense support to the property node

Question

 
I really hate having to dig through a long hierarchy of menus when I know what I want:
Visual Studio (and other MS and non-MS products) have a feature called Intellisense, which is meant to make this easier. Basically, as you type, it pops up a list of matching objects, based on context, so you can quickly select what you want:
It would be nice if LV had a similar feature - click on a property in the property node using the text tool (or Ctrl+click if using the auto-tool) and now you can type in the property name and you will get an Intellisense-like pop-up, which will have all the relevant properties.
Specific features it could have:
It should know all the relevant names - full names with the hierarchy (Boolean Text.Font.Color), long names (Mechanical Action) and short names (MechAction). This could probably be similar to how Quick Drop handles shortcuts or they could simply appear as separate items.
It should be context sensitive. If the class is Boolean, then there's no need to have Listbox properties in the list.
It should match all the properties which include the search string (so "in" on a boolean would match both "Indicator" and "Strings[]") and only them.
It should have the ability to use caps for acronyms (e.g. in the above screenshot you could use "BT" instead of "Boolean Text", similar to what appears in this video).
It could probably also work on the invoke node, although there it's less needed.
It could probably also be used to quickly select a class if you have a class specifier using the same basic mechanism.
This example (LV 2009) shows how useful this could be. You don't need anything installed. Just run the VI and start changing properties.
Caveats:
It will only work on the last property in the node.
It doesn't have the proper list of names and it doesn't implement all the features in the idea, as this is just a basic example.
Note - this is similar to this idea, but I think that it's much more usable. Also note that the second idea refers to a QDKS which ships with 2010, but that is far from perfect.

Answer 1

Here's a more detailed response.
Browser:
Click Ctrl+Shift+B.
Get a new window. Great. Just lost a little bit of focus on what I was doing.
Find the search button. Oh, there it is. It's that little button.
Oh, another window popped up. What did I want? ...   ...   ... Ah, yes. It was that property.
Search for it. OK, that was easy. Now Enter.
Oh, I'm back to the original browser window, but the property is highlighted.
OK, so now I can drag the property into the BD and get a new property node with that property, but that's not actually what I wanted. I wanted to set a property on an existing node.
So, to summarize: A key combo, some mouse activity, 3 window changes and we still didn't get what we want.
Compare that to:
Ctrl+Click on the property you want to replace.
Start typing.
The intellisense popup appears as part of the current window, already navigable with the up and down keys.
Press Enter.
And two additional points:
Imagine working in VS without intellisense. What if you had to use something similar to the browser (or the menu hierarchy) every single time you wanted to get a property?
You encourage people to work with LV classes. Property nodes offer a productivity enhancement when working with classes and this offers another one, so you not only not be questioning it. You should be evangalizing it.
And for those who survived this far, a bonus. This example (LV 2009) shows how useful this could be. You don't need anything installed. Just run the VI and start changing properties.
Caveats:
It will only work on the last property in the node.
It doesn't have the proper list of names and it doesn't implement all the features in the idea, as this is just a basic example.