jmcc's picture
Jean Marie commented on Paul's Bug Report, “Node Library window

Paul,

We were able to reproduce this by closing all composition windows. Then the node library remains visible (and on top) when switching to other apps.

2bitpunk's picture
cwilms-loyalist's picture

Save Subcomposition - Can't type to change Node Title

Status: 

Vuo version: 

OS version: 

  • macOS 10.15

How severely does this bug affect you?: 

●●○○ — It's annoying but I can work around it.

Steps causing the bug to occur: 

  1. Select nodes and right click to Save as Subcomposition.
  2. Save Subcomposition window comes up but keyboard does allow me to change the name and won't let me press save either.
  3. Moved over to Notes app, keyboard and mouse are working properly over there. Move back to Vuo and it won't let me type.

Have you found a workaround?: 

Don't use subcompositions. :(

jmcc's picture

Mardus,

We understand this is a long time coming, and we appreciate your patience. Now that Vuo 2.0 is out, one of the projects we've been working on is researching, planning, and performing tests toward Windows support. But we're still very early in the process, so we don't have an estimate yet. In a few months, when we're deeper into this project, we should be able to give an estimate.

cwilms-loyalist's picture

OK, I think I've figured it out, I had some custom nodes that were missing on the system I was trying to run it on (fresh install). Normally, I expect, this wouldn't be a problem however one of the custom nodes had another custom node nested inside of it. Vuo doesn't seem to like that. ;-)

So, once I installed the nested custom node on the system the composition actually opened and told me I was missing the other custom node. Once I installed that node the composition would run. Yay!

2bitpunk's picture
jmcc's picture
Jean Marie commented on Paul's Bug Report, “Node Library window

Thanks for the update; we've closed this report.

cwilms-loyalist's picture

OK, I've verified the file also doesn't open in Vuo 2.0.0 under OSX 10.15.3 on my 2013 Mac Pro either so it doesn't appear related to the version of 2.0.x. Any ideas, Catalina specific issue maybe?

Edit 1: I just noticed there is a OSX 10.15.4 update, I'll give that a shot too.

Edit 2: Nope, the OS update didn't fix the issue.

cwilms-loyalist's picture

Here is a screen cap of the console errors I get get when I run it.

I ran console a 2nd time and added a couple of other screen caps showing some of the other messages around the Errors and Faults in case some of those are important.

Pages

Welcome!

Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion


Browse Feature Requests

Suggest a Feature


Browse the Composition Gallery

Share a Composition


How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.