You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"1. Just write some code with an Array or any other variable or object that shows collapsed in the variables window when debugging with processing IDE.
Start debugging and go to the variables window.
Click the Array for it to open, the > simbol at the left changes to the open position but do nothing happens.
Click again and the > simbol changes to the "closed" position.
Click again and now everything works as expected."
snippet
// Paste your code below :)String arrayTest[] = {"1", "2", "3"};
voidsetup() {
printArray(arrayTest);
}
// Setup a break point somewhere in order to be able to use the variables window
Additional context
I have seen this behaviour in the last two or three versions I tried.
After you double click and see contents of the Array it behaves ok and only one clik is needed to open and close it.
Would you like to work on the issue?
I can't work on the issue
The text was updated successfully, but these errors were encountered:
Most appropriate sub-area of Processing 4?
PDE
Processing version
4.4.4
Operating system
MacOS 12.7.6
Steps to reproduce this
"1. Just write some code with an Array or any other variable or object that shows collapsed in the variables window when debugging with processing IDE.
Start debugging and go to the variables window.
Click the Array for it to open, the > simbol at the left changes to the open position but do nothing happens.
Click again and the > simbol changes to the "closed" position.
Click again and now everything works as expected."
snippet
Additional context
I have seen this behaviour in the last two or three versions I tried.
After you double click and see contents of the Array it behaves ok and only one clik is needed to open and close it.
Would you like to work on the issue?
I can't work on the issue
The text was updated successfully, but these errors were encountered: