That gets a little hairy since we don’t really have any concept of how many elements a given input has at the node level. For various reasons, the data types coming into a node are only resolved at render time, meaning it isn’t possible to produce the correct number of connections on a ToScalar node, since the input may have 1, 2, 3, 42, etc. elements.
On the other hand it isn’t unreasonable to make a “shorthand” form, perhaps VectorToScalar that is just a wrapper around an Integer input and a ToScalar node. We will discuss the ramifications of enabling multiple outputs (which we intend to avoid in general) for this specific application.
In short no, since that’s the entire point of ToVector. We tried to make it really simple to just drop a Float then a ToVector and hit the spacebar three times to connect them up. We discussed this concept when designing the editor, and decided that we wanted to avoid implicit conversions for the sake of error checking.
You need to have both nodes selected, then the spacebar should connect the lower numbered node to the higher numbered node’s first unconnected socket. Shift-spacebar will do the same but go from the higher numbered node to the lower.
Also, holding shift and dragging a node is supposed to unlink that node from the flow passing its Input1 to whatever nodes it was connected to. You could delete it afterward, but backspace is a shortcut for that whole operation.