We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Does anybody know how many columns that Processing Message Area can display? (without lose first data)
Why don't you write a little test program that tests how much can be printed?
void setup(){ for(int columns = 1; columns < 100; columns++){ println(columns); for(int i = 0; i < columns; i++){ print("W "); } println(); } }
It's going to depend entirely on the width of your window.
Alternatively, it appears that Processing doesn't break on non-whitespace, so you could try separating your columns by underscores instead of tabs.
Better yet, why don't you just save your output into a csv file?
i think he means lines rather than columns and that the question is asking how long the buffer is.
there is (on linux at least) a file that contains all the console output. it's in, iirc, the tmp directory somewhere.
I would not rely on the message area for outputting data. Instead, save it to an array of Strings and write it out to a file.
@TfGuy44 gets a +1 from me.
I wouldn't rely on the console output: I've often suspected that to be the cause of crashes when it gets heavily overloaded...
I needed info about message area because library which I used create log error data using "System.out.println".. But, finally I found solution by copying file from console log..
Answers
Why don't you write a little test program that tests how much can be printed?
It's going to depend entirely on the width of your window.
Alternatively, it appears that Processing doesn't break on non-whitespace, so you could try separating your columns by underscores instead of tabs.
Better yet, why don't you just save your output into a csv file?
i think he means lines rather than columns and that the question is asking how long the buffer is.
there is (on linux at least) a file that contains all the console output. it's in, iirc, the tmp directory somewhere.
I would not rely on the message area for outputting data. Instead, save it to an array of Strings and write it out to a file.
@TfGuy44 gets a +1 from me.
I wouldn't rely on the console output: I've often suspected that to be the cause of crashes when it gets heavily overloaded...
I needed info about message area because library which I used create log error data using "System.out.println".. But, finally I found solution by copying file from console log..