featurescript debug
Discussion List
-
Temporary Items During Edit?
How do first party features do things like "Show isocurves"? Is there a standard way to draw stuff without debug() or manipulators that disappears when not editing?
-
Use Report, viz(), and dbg() for conditional println and debug visualizations
Earlier this year I wrote a utility called "Report". The one-sentence description is "Conditional debug visualization and println controlled by feature and not by code". Here's an intro video: https://www.youtube.com/watch?v=Eu7puEa8Oak You can find the feature and functions here:…
-
FeatureScript writers: Stop using println! And start using Report (New FeatureScript announcement)
Actually, It's totally ok to continue using println! But I wanted to introduce a new FeatureScript called Report that will help you control your featurescript notice area output. It's a bit hard to describe, so take a look at the HOWTO video below:…
-
Why debug feature is not displayed ?
Hello, When I use the debug feature on a vector, the data are displayed in the FeatureScript Notice, but the lines are not drawn on the screen.I thought they should appear, right? I use the debug feature to display these lines on the sketch { // 1st line var line1Start = [x1, y1]; var line1End = [x2, y2];…
-
Debugging a feature script
Hi all, I start to use feature script, great stuff indeed. As there are not too many tutorials and a basic doc I still make a lot of errors and many operations I have to learn by try and error. Now when something is wrong I see in the part studio the message "Feature did not regenerate properly " plus a short error message…
-
Looping Through Debugs Breaks unstableIdComponent
It turns out that looping through any debug function (such as addDebugPoint and addDebugArrow) causes any features inside the same loop which rely on unstableIdComponent to break. Notably, the output of features which rely on unstableIdComponent still happen, but the output becomes unusable by other features downstream -…
-
Why does addDebugEntities take regen time when the debugged feature's edit dialog is closed?
The addDebugEntities apparently adds about 13 ms to a feature's regen time. That ends up being a lot because I have many calls to this in my part studio. I'm wondering if that is a bug because this code shouldn't be called when the dialog is closed. Is there an alternative way to show a user which objects they have…