People will never know that the options exist. So many features are added to LV in each version that it becomes impossible for experienced programmers to notice small additions to various functions. The subVI node setup you mentioned, for instance, is something I almost never notice - my brain simply edits it out of a subVI's pop up menu.
This is basically connected to the context sensitive help topic you brought up way back - can we get LV to draw attention to properties which would otherwise go unnoticed without being annoying?
As for creating a standard way to access properties, there already is one - "when in doubt, right click". It is likely that adding to this (not replacing) a properties page for each subVI will help - maybe users which will miss some of the information available in the context menu will notice it when it appears in a separate dialog window, especially if new features are highlighted.
As for the configuration appearing on the BD - I'm not sure whether I would want configuration information for subVIs cluttering up my diagram, and I'm not sure how much you can actually change the configuration at run time (many options, like the aggregate comparison you mentioned, are design time only), but I never really used express VIs or timed loops, for instance, so I'm not sure about this.
Just some ramblings so far.
This is great! It would make it invisible to casual observation (looking over someone's code) if you did not want to see it. It would not stand out when printing. It would however, not change the difficulty of not knowing the configuration of a node merely by looking at it (as is a common complaint of the Express VIs).
Phillip Brooks wrote: <snip> Maybe a new block diagram cursor type that appears when the mouse is placed over a configurable function (a magic wand? 🙂 This cue to the operator would be context related and not change the look of / complicate the block diagram. <snip>
For me, the old "the diagram IS the code" paradigm is a biggie. Stuff that requires a right-click to see which mode options are selected are an annoyance, and another potential source of hard-to-find bugs.
When I look at the diagram, I want to be able to know at a glance which nodes may have some additional hidden config options WITHOUT having to hover my mouse over each one individually. (The magic wand idea sounds interesting, I just don't want it to be the ONLY hint). Exactly what the visual cue should be is not something I have a strong opinion about, but I'd propose that it be one of the things that can be user-configured in Tools-->Options-->Block Diagram. Maybe it's a bounding box with a possibility for the user to define the color (like the tip someone posted about making coercion dots bright red to stand out more). Or maybe a semi-transparent overlay that can be enabled or disabled by an individual user. I think the key is that people like me that want an obvious visual cue can have one and people who consider it to be clutter can turn it off.
I think new features should be very fast to use, but there should always be also an easy way for not so advanced users. However LabVIEW is a daily tool for many of us and therefore the needs of power users should never be overlooked. I conclude my thoughts of configurable nodes with the following list of ideas.