Why does addDebugEntities take regen time when the debugged feature's edit dialog is closed?

monroe_weber_shirk
monroe_weber_shirk Member Posts: 103 EDU
in Community Support
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 selected without using this debug feature?

From the standard library...
As with debug, highlighted entities are only visible while the debugged feature's edit dialog is open.
Tagged:

Best Answer

  • ilya_baran
    ilya_baran Onshape Employees, Developers, HDM Posts: 1,274 image
    Answer ✓
    Just because we show debug entities when the dialog is open doesn't mean that the code is running any differently.  Internally, because the feature doesn't know if the dialog is open or not, we can open a feature dialog without executing any FeatureScript, just by rolling back.
    Ilya Baran \ VP, Architecture and FeatureScript \ Onshape Inc

Answers

  • ilya_baran
    ilya_baran Onshape Employees, Developers, HDM Posts: 1,274 image
    Answer ✓
    Just because we show debug entities when the dialog is open doesn't mean that the code is running any differently.  Internally, because the feature doesn't know if the dialog is open or not, we can open a feature dialog without executing any FeatureScript, just by rolling back.
    Ilya Baran \ VP, Architecture and FeatureScript \ Onshape Inc

Categories