What is the relationship between context in the editingLogic function and in the feature?

dave_cowden
dave_cowden Member, Developers Posts: 484 ✭✭✭
Based on a simple experiment with set/get Variable, it seems that the context passed to the editingLogic function and the context passed to the feature are not the same. This surprised me.

I'm looking at a use case in which the editingLogic function needs to construct some geometry in order to adjust user inputs. I'd like to avoid repeating these calculations again in the feature, but then i need these constructions to be accessible ( and mutable ) by the feature.

If I create geometry in the editingLogic function, are those things accessible and mutable if thy are passed to the feature via the definition?

I know that performance will be a concern if i'm getting into creating geometry in the editingLogicFunction, but in this case, there's no way to make a nice-to-use feature without it.

Best Answer

Answers

  • dave_cowden
    dave_cowden Member, Developers Posts: 484 ✭✭✭
    As a side note, it was implied, but to make it clear: i would find it both more intuitive and more helpful if the context was shared between the editingLogic function and the feature itself...
  • dave_cowden
    dave_cowden Member, Developers Posts: 484 ✭✭✭
    Ok thanks, this answers the question. Sorry for not checking the docs first.