I agree with the general idea of having better access to the relevant class methods. In practice I would modify your idea slightly to "Insert class method with right-click on WIRE"... Seems more natural 🙂
I like it a lot. I think it fits well with this popular idea (you know, for an LVOOP idea ). That one just mentions property nodes but I like the concept of shoving the methods int he other half of the palette.
You can already do this... you just have to build the palette yourself. You can set the properties of a class in the Class Properties dialog to pick which .mnu file LV should show in the right-click menu for a terminal or wire of the class type.
If you want the palette to be autobuilt, here's the existing idea:
Sure, you can build you own menu, but it should be a "live" experience where new items are available as soon as they have been created.
It should also be aware of the scope. So if you are in a member VI, and you click on a wire, you should get access to the private methods as well, not just the public.
I agree with Mads - It has to be live. One possibility is that right-click shows all (relevant) class methods by default, but that any user-defined palette overrides the defaults.
PS: No "autobuilt" palettes either, thanks... I just want to see all methods available at that point in time.
I would say an even better idea would be to allow class methods accesible via invoke nodes (similar to accessing accessors via property nodes.) Ins and outs of the method VI would be shown as ins and outs of the method with the same label.
11 years later and still no decision on this very useful feature. Right-clicking a class wire should have a context menu that allows the insertion of public class member VIs. Can we at least get a decision? I did a re-kudo to maybe get this back on the radar screen.
