I don't have an M1 myself. I've had two reports of 3-5 second video lag with my Vuo-made application, when running on M1 Macs. Given the performance of these machines, I can only guess something else is going on.
●●●○ — It prevents me from completing a specific task with Vuo.
Steps causing the bug to occur:
Make a composition using Make Text Field
Type in text field until the length of the characters are longer than the text field
Look at the growing text field
Other notes:
Expected behavior is scrolling the text preserving the Text Field size. As the field can overlap other UI elements and will not clear on hitting enter, it can break compositions using the feature
●●●○ — It prevents me from completing a specific task with Vuo.
Steps causing the bug to occur:
Open and run attached composition
Observe somewhat sluggish but usable behavior (might be related to text usage or the Mac it's being run on)
Open sub-composition
Attach Window input port to Window port of arrange node
Start main composition
Observe slow/unusable behavior
Looking at the event flow the arrange node fires events constantly
Have you found a workaround?:
Don't attach window cable to arrange node
Other notes:
I assume the arrange nodes aren't optimized for using them with UI layers (which they are super-useful for). Having an option to "Allow changes" for the Window port type could perhaps solve this?
If I'm running a composition in a window, ie VuoCompositionLoader is running, and then I sleep my Mac, when I wake my Mac the main Vuo app has forgotten about the window, and so there's no convenient way to kill the window except for quitting VuoCompositionLoader.
Expected behaviour would be that the Stop button in the main Vuo app would still be visible, and hitting that would close/stop the current app in the VuoCompositionLoader.
