I agree that the line number would be very handy, but 100 lines of code in grasshopper? I know it's actually not that much if you where doing it in rhinoscript for example, but I don't think grasshopper is the right platform for large chunks of code. Are you sure you can't divide the scripting component in smaller ones, each doing a specific task, and maybe doing some of the things with standard components?
On Nov 29, 3:29 pm, Dimitrie <[EMAIL PROTECTED]> wrote: > hm... any chance we're going to have the errors outputing together > with the corresponding line of code's number? > it gets quite, say, unproductive :) to search through 100 lines of > code and try and guess what's wrong and where (especially for a > inexperienced .net programmer as i am)... dubgging as it is now is > nearly impossible on larger scripts. > thanks,d.
