●●●○ — It prevents me from completing a specific task with Vuo.
Steps causing the bug to occur:
run the attached comp
right click and fire event on yellow node "list two".
right click and fire event on "go backward" port of blue node
Outputted "Item" from blue node is correctly "3" - the value of the third element of "list two" node - while outputted position is 4. I'd expect this latter to be 3, it's very strange that cycling a list with just 3 elements could output a fourth position. And in any case, this data doesn't match with "Item" data.
Have you found a workaround?:
Don't know if this can be considered a proper bug, but in my opinion it's quite inconsistent and just when I simplified a task with this example realized what could be happening in a more complex comp that isn't behaving as i'd expect.
"Change Windows Screen" nodes needs to receive an event to be activated and route its output to "Render Image to Windows" nodes. So, just add two event cables from "Fire on Start" and I think this will solve the external monitor position. There's a second issue in cable connecting "Change Window Screen" set to display on main monitor, and its "Render Image to Window". You shouldn't use a thin cable (event-only), but a data-and-event cable. Probably you'd need some time to read documentation, that explain all basics you need.