My main beef with the current sub composition behaviour is that on the outside, it looks like any other node, but it's impossible to build a sub composition that has actions associated with event arrival at specific ports, which is very common among Vuo's included nodes. The sub composition I submitted with the original (but report) post was a demonstration of this issue, using a Count node essentially inside a wrapper. Putting it inside a sub composition killed its functionality.
We need (or at the very least, I want) to be able to have better control and flexibility over events flowing into a sub composition, otherwise the ability to expand the functionality of Vuo will be limited only to people who want to program that functionality in C. That is a limitation I'm not willing to be stuck with, as it misses the point of being able to program completely in a visual environment.
The nice thing about the proposed change is that it will allow a composer to implement the old behaviour while allowing for far more complex functionality if desired.
If a composer uses a Receive Keyboard Buttons node configured to fire events when a standard keyboard shortcut (such as cmd+Q) is used, the standard behaviour should be disabled.
Alternatively, if the above is not implemented, the composer should receive a warning of some flavour if he or she attempts to use an existing keyboard shortcut in a Vuo composition.
Rather than expanding it to include all possible combinations of modifiers (growing the list of 6 above to a list of 17), would it be possible to have checkboxes and radio buttons or a switch? Something like this:
[ ] Command |
[ ] Option | Checkboxes
[ ] Control |
[ ] Shift |
( ) Any of the above | Radios or
( ) All of the above | a switch
For the "None", just select no checkboxes, (and Vuo can ignore the radios). For the "Any" option, select all checkboxes and the "Any of the above" radio.
Shortcut buttons or hyperlink-style labels could be placed at the top or bottom of the dialog to quickly select all or none of the checkboxes.
●●●○ — It prevents me from completing a specific task with Vuo.
Steps causing the bug to occur:
Open attached composition and run it. Observe the three rotating cubes:
The orange cube has a random rotation which is applied via a Combine Transforms node.
To its left, the purple cube receives the same rotation as a quaternion via a Make Quaternion Transform node.
And to the right, the blue cube also receives the same rotation, this time converted back to Euler angles, via a Make 3D Transform node.
Have you found a workaround?:
No.
Other notes:
All three cubes should, I believe, be moving in unison. Although the orange cube rotates correctly using the Combine Transforms node, the rotation gets muddled somehow when it's extracted from the combined transform and passed onto other nodes.
