Another Timer techinical question

Quote from red51

If you pause a timer while the task is still active, the current task will still be completed, but no more tasks will be executed until you restart the timer. E.g. if your task runnable looks like this:

Java

System.out.println("before");
timer.pause();
System.out.println("after");

...the output will be:

Code

before
after

Even if you kill the timer, the currently active task will still be completed Or did you mean something else?

Well that was good but, No it was not what I was asking. The routines in the timer always execute when the timer goes off. The question is about detecting a .isPaused. I have a routine that was detecting a paused timer in an if statement just fine but then I enhanced the routine which moved it up in the ladder and it seemed to never detect the paused timer out of the executable never executed. I finally put a toggle variable in and that appears to have remedied it.

I was asking of the .isPaused detection of a routine is not a reliable IF routine trigger for one. Then if the timer is in .isPaused mode would code below it execute properly this could include turning the timer back on when another event was detected? Because the next time the event detection happened my routine would act if the timer was not paused.

In any case I have it working good enough but I did not like using a detection boolean variable as it as problematic in the logic. But the reliable detection of .isActive verses .isPaused is the question. Are they reliable detection methods of what the timer is doing or can they be sometimes not detected? And if the timer is paused will the routine detect this and skip it the next time around as if it was not there?

Is the reverse true for pausing then restarting it? The .isActive to see that it is counting down is important. So the routine .isActive sees that it is running and continues to the next statement which .pause() it. The next time I go through the event it should see that it is .isPaused and that is where I was having trouble. The next time it would not jump the .isPaused routine and would execute the routine IF statement trying to detect it with IF (timer.isActive) blah blah. It was as if I did not start the timer but I put a output that said it was started at the correct line. I move the statements around in the logic and it worked better but not reliably until I put the toggle in. When checking for either the timer and the toggle it works. So I was wondering about the ability to toggle the timer off and on and detect it immediately.

Quote from Minotorious

ok I am confused Why don't you do something as simple as this:

Java

//Define Timer as a Field
public static Timer myTimer;


//Initialise the Timer
public static void myTimerInit(){
	myTimer = new Timer(blablabla);


	myTimer.start();
}


//Check if the Timer is active or paused and do something
public static void myTimerCheck(){
	if (myTimer.isActive()){
		myTimer.pause();
	}
	else if (myTimer.isPaused()){
		myTimer.start();
	}
}

Display More

Just make sure the Init method is definitely called before the check method else you might get an exception (probably null Exception)

Well thanks for that but what I am doing is not that simple. The detection of the timer being active or paused by of the actions of another player someplace else on the map is important. With a bunch of other imbedded decisions in between. Anyway I have it working <knock on wood>. It is probably that the timer starts once or is not initialized because of a second event. Probably a start and restart of the routine caused the timers to stop in a branch not totally sure. The toggle solved the issue just had to do some extra statements and placement of the actions to make it reliable both in a fast or delayed response. You guys are indicating that it should follow through so seems a branch out a logical the culprit but I get bleary eyed looking at it.

It is testing fine now.

Not a problem Minos.. thanks for the confirmation. What I am doing is pretty ugly code and it would take a bit to explain why this pause vs this start if this pause is on .. so I am sure it is/was a sequencing error. It is working on my server now so I dont want to touch it. Thanks again.. you guys are/have been really helpful.