Feature: ability to pause events also

[moos]

After reaching idle state, I'd like the component to be a no-op. Currently, events are still bound (potential perf issue), and handlers still called (unless stopOnIdle=true). Calling this.idleTimer.componentWillUnmount() does the trick - but it's not semantically correct.

Would prefer a this.idleTimer.destroy() (or similar) or have 'stopOnIdle' include events binding also. Thoughts?

[SupremeTechnopriest]

Hey, this is a great idea and probably a common use case. I will get this implemented ASAP.

…

On Tue, Jan 22, 2019, 10:59 AM Moos ***@***.*** wrote: After reaching idle state, I'd like the component to be a no-op. Currently, events are still bound (potential perf issue), and handlers still called (unless stopOnIdle=true). Calling this.idleTimer.componentWillUnmount() does the trick - but it's not semantically correct. Would prefer a this.idleTimer.destroy() (or similar) or have 'stopOnIdle' include events binding also. Thoughts? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#67>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACKCXpFEMoM2ZSnbCYeBuK0lLMdwuBEyks5vF1-BgaJpZM4aNTxQ> .

[SupremeTechnopriest]

@moos Hey buddy, thanks for your input here. Good stuff. I implemented dynamic event binding and it is published as version 4.2.0. The functionality that you requested should happen automagically for you, but if you want to manually bind or unbind the events, you can call the private methods directly this.idleTimerRef._bindEvents() and this.idleTimerRef._unbindEvents().

[moos]

Works great - thanks.