Fix wakeupToken handling - don't respond to toggle, but to different value

vs. that at registering function with scheduler.

Author: dok-net

cores/esp8266/Schedule.cpp

@@ -176,8 +176,6 @@ void run_scheduled_recurrent_functions()
         done = current == stop;
         const bool wakeupToken = current->wakeupToken && current->wakeupToken->load();
         const bool wakeup = current->wakeupTokenCmp != wakeupToken;
-        if (wakeup)
-            current->wakeupTokenCmp = wakeupToken;
         bool callNow = current->callNow;
 
         if ((wakeup || callNow) && !current->mFunc())

cores/esp8266/Schedule.h

@@ -59,8 +59,8 @@ void run_scheduled_functions();
 //   functions.  However a user function returning false will cancel itself.
 // * Long running operations or yield() or delay() are not allowed in the
 //   recurrent function.
-// * If a wakeupToken is used, if its value toggles, any remaining
-//   delay is disregarded, and the lambda runs on the next scheduler iteration.
+// * If a wakeupToken is used, anytime during scheduling when its value differs from that
+//   during this call, any remaining delay from repeat_us is disregarded, and fn is executed.
 bool schedule_recurrent_function_us(const std::function<bool(void)>& fn, uint32_t repeat_us,
     const std::atomic<bool>* wakeupToken = nullptr);