Line-break support in Comments

Status: 

Fixed in Vuo version: 

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

Comments are a very useful way to help a larger composition be more readable.

However, while it's possible to type linebreaks using Option+Enter in the text field, these are not shown by the Comment on the page:

image image

Compositions: 

Sporadic crash when quitting with a subcomposition and parent composition open

Status: 

Vuo version: 

Fixed in Vuo version: 

Steps causing the bug to occur: 

  1. Open a composition that contains a subcomposition.
  2. Open the subcomposition (e.g. by double-clicking on the node in the composition).
  3. ?
  4. Quit Vuo.

Vuo may crash while quitting — crash report from mic.

Make Image from Web page breaks for width > 1024

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 11

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

  1. Load the built-in example ShowWebPage.vuo
  2. Change width to 1080
  3. Output is diagonal distorted image

Have you found a workaround?: 

no

Other notes: 

M1 Macbook Air

Screenshots: 

List Screens reports empty names

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 11

CPU architecture: 

Apple Silicon (M1/ARM64)

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

  1. Connect a secondary screen to Mac
  2. List Screen Node
  3. Names are reported as empty strings

Have you found a workaround?: 

None

Screenshots: 

Y Mouse Coordinate on Multiple screens seems wrong.

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.15

CPU architecture: 

Intel x86_64

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

  1. Make sure you have 2 monitors connected to your Mac
  2. Run the attached Composition
  3. The window updates its information based on which screen it resides on.
  4. Try dragging the Screen Information Window from the composition between each display and notice that the mouse position, which I understood should display the position of the cursor based on the screen layout, changes depending on which screen the window resides on when the mouse is returned to the exact same physical location on screen. (See Notes below)

Have you found a workaround?: 

No, I haven't

Other notes: 

I'm not sure if the the mouse cursor location is display an accurate Y coordinate. X seems to be working correctly, or maybe I'm just not understanding what the Receive Mouse Moves node is actually showing. So, if you look at the attached image you will see the screen layout my MacBook Pro and LG display are in. If I place the screen information window on my Primary MacBook Pro screen (see Pink Box) and move my cursor to the bottom right corner I get a value of roughly 1920 x 1200 which is what I would expect it to be. However if I place the Screen information window on my secondary LG display (see Green Box) and move the cursor to the exact same lower right corner on my MacBook Pro screen it now shows a value of 1920 x 1080 indicating that the X value is still being derived from the Primary monitor as I would expect but the Y value is now being derived using resolution information form the secondary display which is 1080 pixels high. I've tested this in multiple screen layouts and it appears that X behaves as I would expect and gives a consistent value no matter which screen is currently active however the Y mouse value seems to be calculated using which ever screen is currently active. I hope I've explained it in a way that makes sense, because it took me a long time to figure out what I think it's doing. :)

Screenshots: 

Compositions: 

AttachmentSize
Binary Data Screen and Mouse Position Issue.vuo10.37 KB

Pages

Subscribe to RSS - Resolved