Bug When Saving CSVs

Frederik,

This bug is causing me some pain...

I render a table, chose Export, select CSV as the format, when dialog changes leave delimiter as is, hit Next, then enter the file name. Works fine the first time.

But from that point on here is what happens instead:

I render a table, chose Export, select CSV as the format, when dialog changes leave delimiter as is, hit Next, and then NOTHING. The file name dialog fails to appear. Which means I have no way to save my table.

The workaround is to save, quit NodeBox, relaunch, and try again. As long as I am saving for the first time in a session, it works fine. But if I forget to quit and relaunch before each subsequent CSV export I am hosed.

Can you please confirm and fix?

Thanks,

John

So the dialog doesn't appear the second time, is that correct? That seems annoying indeed! I'll take a look.

It doesn't appear the first time for me. I thought it wasn't working completely until I came here. Closing Nodebox and retrying was going to be my next attempt. I was also trying to export from a filter_data node which I suppose is incorrect?

Joe,

This problem was causing me much pain every day for several weeks last Fall - and then the problem went away without any updates to NodeBox - and since then it has never reoccured. I just tried again and everything now works fine for me. Strange.

There is nothing wrong with saving a CSV from a filter-data node. I suggest rebooting your machine and trying again. If the problem recurs please write again and tell us what version of Nodebox you are using (the latest version is 3.0.51) and whether you are using a Mac or PC. Are you able to save other sorts of files (SVG, PNG, etc.)?

My only guess (and I'm probably grasping at straws) is that there may be a memory leak or memory management issue at play here. Sometimes NodeBox develops some odd behaviors if it's been running for awhile.

Good luck and please keep in touch!

John

Hi John!

I can normally save other files without issue. I'm on macOS 10.13.6.

I think your guess is correct. I had been using Nodebox for a while when setting that up. So that's probably it as restarting it did resolve the issue. I just wanted to note that it was on my first attempt to save in that session.

Thanks! And thanks for all of your work on these forums. I haven't commented before, but you have helped me greatly.

Scratch that, it does happen with other formats too. I do believe it's memory related. I was messing with a large data set that I've used before. It's a list of US cities—about 40K rows. I had to close and reopen to save an SVG. I vaguely remember having to do that before but I can't be sure.