NeodigmMetronome | Move native timeout and interval functions to a separate thread.

[neodigm]

Improve performance by overloading the setTimeout and setInterval with a multi-threaded implementation.

[arcanus55]

Behind a feature flag. I imagine, off by default?

[neodigm]

This is complete in v2.5. This logic has been integrated into the NeodigmMetronome init method.

Usage: Turn on feature flag.

<script>
let neodigmOptCustom = {  neodigmWWInterval:true }
</script>

[neodigm]

Reconsider this. Perhaps make it N55 specific. Meaning, conditionally use setTimeoutN55() within the N55 components. This would negate compatibility risks.

[neodigm]

Update: Turning on Feature Flag, however the components that make use of it will be limited.
Using the setTimeoutN55() idea and it seems to work.
Adding some debug level logging.
Documentation, will be just a comment in the architecture overview.

[neodigm]

This issue is resolved in v3.0 (Toast Only - setTimeout Only)
Feature flag is true by default

<script>
// Turn on Feature Flag
// Turn  on debugger to verify | neodigmOpt.N55_DEBUG_lOG = true 
let neodigmOptCustom = {  neodigmWWInterval:true }
// Verify by neodigmToast.q("If this Toast goes away, it is working", "brand")
</script>