title: A clean way to "add a cooldown" to fullpage.js scrolling with anchor buttons (without removing the anchors)?
body: <p>was wondering if anyone can give me advice on this matter about fullpage.js with react.</p>
  
  <p>My problem is that spamming buttons between sections causes scrolling to become erratic and background images to flicker. setAllowScrolling(false, 'all') etc doesn't seem to work for scrolling via buttons (works normally via wheel). Also need those anchors on at all times because I use the active class they add to the components.</p>
  
  <h3>Steps to reproduce it</h3>
  
  <ol>
  <li>Added a navbar outside the wrapper since I want it to be fixed.</li>
  <li>Added the menu functionality on my list with anchors etc.</li>
  <li>If the user spams them, scrolling becomes erratic and I am at a loss as to how to set a cooldown for them, since the anchor buttons seem to be an internal plugin function.</li>
  </ol>
  
  <p>[Chrome, Firefox, Windows 10, desktop.]</p>
  
  <hr>
  
  <p>Here is a barebones codesandbox: <a href="https://codesandbox.io/s/portfolio-3gb8z" rel="nofollow noreferrer">https://codesandbox.io/s/portfolio-3gb8z</a></p>
  
  <p>In the NavList.js at the moment, I got both onClick functions and anchors. The cooldowns I have implemented in the first two buttons work for the onClick functions but not the anchor/menu functionality.  </p>
  
  <p>Keep in mind that if you disable the onClick, the anchors will work only when clicking the outer button because the icons/text on the buttons don't register the click. That's why I also put onClick functions in there in the first place.</p>
  
  <p>The thing is I just want to find a way to apply the cooldown on the anchors too. Problem is reproduced by spamming buttons in succession or spamming them while the scroll happens (try the 2 first buttons).</p>
  
  <p>PS: I could just get rid of the anchors and keep the buttons with the working cooldown but I need that active class.</p>
  
  <p><strong>TLDR:</strong> because I suck at explaining: say you trigger a </p>
  
  <pre><code>  window.fullpage_api.setAllowScrolling(false, "all");
    window.fullpage_api.setKeyboardScrolling(false, "all");
  </code></pre>
  
  <p>The anchors still work - that's the essence of my problem.</p>