Timeline for How to see/trace Manipulate steps?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2019 at 18:33 | comment | added | houdini | Nasser, Yes you are right bult-in debug is very sophisticated that avarage person can not use it correctly:). I also tried debug trace tool at the : dbaileyconsultancy.co.uk/debugtrace/debugtrace.html. Normally in my opinion it is better than built-in debug option. But because of " Manipulate" function has so many parameter options, none of these debuggers can solve it correctly. And I'm gonna try "Print" may be it work. Thanks. | |
| Aug 3, 2019 at 18:21 | comment | added | houdini | I've already do that. But because of very intricate and spreading structure of code make it untraceable. So simply step by step evaluation approach not work as expected. | |
| Aug 3, 2019 at 17:54 | comment | added | b3m2a1 |
Can you not just copy the Manipulate source block and evaluate that step-by-step and inspect the result periodically?
|
|
| Aug 3, 2019 at 17:50 | review | First posts | |||
| Aug 3, 2019 at 20:33 | |||||
| Aug 3, 2019 at 17:45 | history | asked | houdini | CC BY-SA 4.0 |