an incomplete list of aspects on vvvv usability that are concerning me since a while
Most important - this is in my eyes even more a bug than a feature in the current version:
opening and closing of patchwindows causing them to be marked ‚dirty‘ is bad.
we usually work in projects with large hierarchichal patch structrues. When you need to make a change to one specific scene or part of the project this usually means, that you have to navigate through the whole hierarchy until you are the patch you need to edit. The opening and closing alone causes all parent patches to be marked ‚dirty‘. Especially the main patch(es) of the project are permanently dirty, even though there are no relevant changes made. This makes working in teams very hard, because the save dialog is virtually rendered useless, because you have to keep track of all changes yourself in order to avoid commit conflicts.
So I would strongly ask for something like a ‚session view‘, where the box/windowstate and position changes are ignored in patches - unless you save them using a special shortcut or menu item.This would make it convenient set a default opening state for a project, and allow just to change the lowest patch. Even node positions could be ignored.
using tab to navigate through the pins of a node. e.g when you have a translate node, you need to click each pin manually to enter x y z values. It would be convenient to just edit-select the next pin using the Tab key.
mark pins that hold user data: pins that are not on default value, i.e. that have been changed (and have an entry in the XML). With nodes with large pinsets it can be very tedious to find out for which pin value they are actually in the patch graph. E.g. Transform 3D. It could just be a differentiation in grey / black values
like in VL: doubleclicking a link brings up the node browser, filtered with the nodes fitting the in- and ouptut types and if a new node is created, it is linked with the first pins.