Open jtroo opened 2 months ago
Wait... is that right? Maybe I just had a buggy cfg
Ah yes indeed it is here:
let is_idle = k.is_idle();
// Note: checking waiting_for_idle can not be part of the computation for
// is_idle() since incrementing ticks_since_idle is dependent on the return
// value of is_idle().
let counting_idle_ticks =
!k.waiting_for_idle.is_empty() || k.live_reload_requested;
if !is_idle {
k.ticks_since_idle = 0;
} else if is_idle && counting_idle_ticks {
k.ticks_since_idle = k.ticks_since_idle.saturating_add(ms_elapsed);
#[cfg(feature = "perf_logging")]
log::info!("ticks since idle: {}", k.ticks_since_idle);
}
It does not today; since this is extra code that runs in a different part of the processing loop,
on-idle
never activates.