This is best illustrated while using the bespoke-keys module. If you have 3 slides, and you deck.next() to the 2nd slide, it takes 3 more deck.next() calls to trigger activate to get to the 3rd slide (on L28 in bespoke.js).
I can't quite tell if this is because of a bad return within fire since these are joined with &&. :(
https://github.com/markdalgleish/bespoke.js/blob/v1.0.0/lib/bespoke.js#L28
This is best illustrated while using the
bespoke-keys
module. If you have 3 slides, and youdeck.next()
to the 2nd slide, it takes 3 moredeck.next()
calls to triggeractivate
to get to the 3rd slide (on L28 in bespoke.js).I can't quite tell if this is because of a bad return within
fire
since these are joined with&&
. :(