Warp image node number parsing bug.

Bug Reports
1

Steps causing the bug to occur

  1. See attached project.
  2. Swap between “mapper.data” and “mapper_new.data” on the input the the warp image node, one works the other doesn’t.
  3. But the data is basically the same except for numerical formatting.

Other notes

  • Vuo version: 1.2.6
  • macOS version: macOS 10.12
  • How severely does this bug affect you? It’s annoying but I can work around it.

Archive.zip (1.75 MB)

2

The issue is that some of the numbers in the not-working file are very long, and Vuo’s parser for mesh data files only handles up to 20 digits. (When the parser reaches the 20th digit of the x value, it thinks the x value is complete and parses the remaining digits as the y value.)

The reason for limiting the number of digits is to prevent a potential bug reported by Cppcheck (https://stackoverflow.com/questions/9292861/how-could-reading-numbers-using-sscanf-crash). However, we can easily bump up the limit to 30 digits.

3

Fixed in Vuo 1.2.7.