Could potentially be a flaw or design oversight in any of those three modules or Decker itself. I think I'll need a reproduction case to investigate.
i have pet chickens, i make drawings, and i write software of questionable usefulness. that's pretty much the extent of my personality. ask me about array programming, decker, or anything, really.
Could potentially be a flaw or design oversight in any of those three modules or Decker itself. I think I'll need a reproduction case to investigate.
I have whipped up a quick demo https://zine.milliesquilly.com/surprises/pathddbug.html
The follower pops up a couple of lines of dialogizer when it reaches its destination. The two buttons basically just walk the follower from point to point. When you click the button that it's already at, that's when the issue presents.
It's a really subtle kinda foot-gun to be aware of when designing contraptions that fire events: code running inside an attribute accessor/mutator like set_path is subject to its own special kind of execution quota which is separate from ordinary scripting flow, so it's best to always fire events via an exposed function or in response to a "natural" event like a click[] or a view[] sent to an internal widget.
I grabbed the updated contraption in from SVN and it looks like it's working now! I haven't otherwise run into execution quotas causing me dramas (I think the one time I noticed them was reading the doco for overriding the audio loop handler) but it's definitely one to keep in mind.