Currently, VuoCompositionLoader’s windows don’t respond to ⌘W. I’d like to be able to close individual windows (without quitting the VuoCompositionLoader app), and to be able to programmatically show/hide windows.
@cwright depending on how a feature request by @jvolker to generally disable nodes will be implemented I could imagine that it would solve this too.
The link to the request : https://community.vuo.org/t/-/4916
If yes, it’s a more general solution and has already more votes ;)
@bodysoulspirit, the feature request you mentioned is an in-editor feature — when you’re running Vuo Editor and editing a composition, you’d be able to temporarily disable a particular node.
@cwright’s feature request, however, is about giving the composition itself control over showing and hiding windows — so that, for example, you could create a composition with a Make Button node, then when you click it, it would show or hide a second window.
1 Like
@Smokris, ok, yes, but I thought if I can disable whatever a node, I could disable a “render layers in window” node too and that disabling it would have make the window disappear.
Yes of course not so sophisticated as the make window closeable thing :)
But hey, Smokris, I believe in you man, when you tell me the sky is red, then I say it’s red man :)
No kidding but yeah sometimes I don’t know the background, the possibilities and the limit of what is possible to code or not :)
Ok we’ll see what the future will offer us concerning these windows then ;)
As spoken with @jstrecker this feature request would also be handy to get rid of the glitches on Apps launches because we could choose to show a window ONLY when some nodes fully rendered
(see the discussion here : https://community.vuo.org/t/-/5042)
So I’m voting !
I’d like to be able to show/hide the console window so I can use it as a debugging window but also disable it at times (it slows comp down amongst other things, and yes I realise I could make a switch to disable the data flow to it to speed things up).
If putting an enable switch on the Console Window node is easier than dealing with full render windows, perhaps it could be first cab off the rank for a quick fix?
For interactive displays it would be nice to have a depth camera trigger some UI controls to display. I can think of a few instances where I may want a keyboard shortcut to bring up a secondary window showing some basic UI controls for a full screen composition. This could be useful.