FIXED: empty table -> convert DAT = 0 rows 1 col?

099 13080 x64 win10
088 62160 x64 win10

If you place a tableDAT down, and set rows/cols to 0, and then a convert DAT after that, it generates 0 rows, 1 col even though there is no input data.

This causes issues for me if a script checks a table’s .numCols/Rows attribute in order to generate certain logic.

Not sure if this is intentional? It seems to have been around a bit even though I’m just now noticing it.

Lucas

Thanks for reporting.
This will be fixed in the next posted build.