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.


milliesquilly
@milliesquilly asked:

Bit of a decker issue using the follower contraption in conjunction with dialogizer/puppeteer - essentially I'm wanting to set things up so that when the follower hits the end of its route (i.e. the on finish event is triggered) a dialogizer script is triggered with accompanying puppets. I've got this working fine for the case where the follower isn't already in the finishing square (i.e. it walks a bit and then triggers the on finish), but if it's already in the finishing square then the script doesn't seem to run properly, like it'll do the beginning setup bits (creating the box and puppets and such) but then it's like the script terminates early. Not sure if this makes sense but I could use some advice - let me know if I need to explain what I'm doing in more detail

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.


You must log in to comment.

in reply to @internet-janitor's post:

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.