System.Timers.Timer problem

[Rune Hunter]

I have a System.Timers.Timer setup like so:

System.Timers.Timer timer = new System.Timers.Timer();
 
timer.AutoReset = false;
timer.Interval = frametime;
timer.Elapsed += new System.Timers.ElapsedEventHandler(timer_Elapsed);

I than start the timer only once calling the timer.Start() method and after the period of time specified it executes the event and than stops like it is suposed to. However in that event I set the interval of the timer to a different value like so:

if (currentframe == framecount - 1)
{
    timer.Interval = framepausetime;
}
else
{
    timer.Interval = frametime;
}

When I set the interval it starts the timer again without me calling Start. I checked to make sure that it wasn't enabled and it is not enabled when I set the interval. Why does it keep starting when I set the interval?

It also apears that calling Stop() on the timer doesn't stop it.

[GanglyLamb]

I dont know the exact cause but I read an article on msdn:

...
As I mentioned earlier, the System.Timers.Timer class members are very similar to those of the System.Windows.Forms.Timer class. The biggest difference is that System.Timers.Timer is a wrapper around Win32 waitable timer objects and raises an Elapsed event on a worker thread rather than a Tick event on the UI thread. The Elapsed event must be connected to an event handler that matches the ElapsedEventHandler delegate. The event handler receives an argument of type ElapsedEventArgs.
Above and beyond the standard EventArgs members, the ElapsedEventArgs class exposes a public SignalTime property, which contains the exact time the timer elapsed. Because this class supports access from different threads, it is conceivable that the Stop method may be called on a thread other than the thread that is used for the Elapsed event. This could potentially result in the Elapsed event firing even after the Stop method has been called. You can deal with this by comparing the SignalTime property to the time the Stop method was called.
The System.Timers.Timer class also provides an AutoReset property that determines if the Elapsed event should fire continuously or just once. Keep in mind that resetting the Interval property after the timer has started will reset the current count back to zero. For example, if the interval is set to 5 seconds and 3 seconds have already elapsed before the interval is changed to 10 seconds, the next timer event will be 13 seconds from the last timer event.
...

Probably has something to do with this...

I cant imagine a timer firing off by itself so ...

[Rune Hunter]

ahh ha there we go. Okay yea working with that helped a lot, thanks.