Does anyone have a recommended IDE to use with Vision for debugging running code? Curious because coming from VB environment I found stepping through code is very valuable.
No. Print statements are going to be your best option to debug code. My philosophy with Ignition projects is to make it 80+% simple bindings and expressions. Just use scripting to do the "fancy" stuff.
2 Likes
I agree you should use bindings as much as possible.
Prints are ok for script console and debugging at first but ultimately they should be replaced by a logger. You get to specific the severity with a logger and it won't slow your program down.
Something like
for i in range(0, 10000):
# do some logic on something
print i
that print statement will slow down you application a lot. Logging will not.
3 Likes