Awesome stuff here.
I am interested in strategies for debugging. After a breakpoint, I can step through code, and there is visibility of some variables. However, it is difficult to evaluate functions on the fly, and that is a problem it they cause an error. Also there is some odd behaviour around dialog forms, where it seems particularly difficult to pin-point the root cause... This must be a frequent difficulty for the more creative coders and I wondered how people work around it. I am used to the VBA IDE and being able to see and test stuff in real time.
One strategy that occurred to me is to have a stock piece of interactive safe code, like a "hello world" message that could be moved during the step through, and possibly used to evaluate functions before they impact the main programme.
Any ideas will be tried most gratefully.
Last seen: 11 months 3 weeks ago
Joined: 03/02/2016 - 12:12