Navigation and Debug

[VS_10698162]

Hi, guys!!! I'm very appreciate you for your product, it's genious, really. I've tried a lot of programs (such as WolframAlpha, Maxima, MathLab and etc.), but when I tried MathCad, I understood - i fell in love with it.
But there are two really major flaws:
1. I can't debug the program I wrote and it makes it difficult to find errors, I have to spend a lot more time looking for them. You have primitive programming language (in terms of implementation complexity), so I guess it shouldn't be hard to implement.
2. I use your program with my laptop, and when I use draft page, it becomes very difficult, to navigate in horizontal directions, so I'm forced to drag the slider, which is not so fast and comfortable. So that's my second request - basically improve touchpad navigation, in every sense)
Good luck with development and thanks again for your product!!!

[VladimirN]

You can submit your own idea or vote for existing ideas here: https://community.ptc.com/t5/Mathcad-Ideas/idb-p/PTCMathcadIdeas

[GeoffD]

I write pretty large programs - probably beyond what Prime is intended for. The debug facility is primitive. A few things that might be useful if you are very new to Prime:

1) Use the "return" command anywhere in the program where you think the error occurs, followed by the variables that you think might reveal the fault, such as: "return A,b,C, h(2,6)" .

2) The "try" command is helpful in bracketing a region of code where the bug may reside:

3) A bug in a program causes all the data to be lost. The "try" command is handy if you are running an iterative program and generating a lot of data for which you might have to wait a long time (days maybe). It allows you to harvest what has been generated via a return command if a bug occurs in the bracketed region. The downside is that the Error Tracing function won't reveal where the error is.

Thanks 

GeoffD