From 97684500b67423c02e3af558e51489781c4d13c7 Mon Sep 17 00:00:00 2001
From: ray <ray@6335cc39-0255-0410-8fd6-9bcaacd3b74c>
Date: Tue, 20 May 2008 19:38:42 +0000
Subject: [PATCH] Added a note explaining why this may not actually work as
 Charlie wants it to without some restructuring of his code.

git-svn-id: https://samskivert.googlecode.com/svn/trunk@2308 6335cc39-0255-0410-8fd6-9bcaacd3b74c
---
 src/java/com/samskivert/util/Interval.java | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/java/com/samskivert/util/Interval.java b/src/java/com/samskivert/util/Interval.java
index 97615ba3..e0b0c4f5 100644
--- a/src/java/com/samskivert/util/Interval.java
+++ b/src/java/com/samskivert/util/Interval.java
@@ -115,6 +115,10 @@ public abstract class Interval
      * expired calls will match the amount of time elapsed. If false, it uses
      * {@link Timer#schedule(TimerTask, long, long)} which ensures that there will be close to
      * <code>repeateDelay</code> milliseconds between expirations.
+     * Note that scheduling things with a fixed delay on an Interval that uses a RunQueue is sort
+     * of sketchy, because the Timer task will be considered "run" when all that's happened
+     * is the RunBuddy has been posted to the RunQueue, and the interval hasn't actually expired
+     * yet.
      */
     public final void schedule (long initialDelay, long repeatDelay, boolean fixedRate)
     {