A few errors in your code snippet: You extend the Thread class, which is not really good practice You have a Timer within a Thread? That doesnt make sense as the a Timer runs on its own Thread. You should rather (when/where necessary), implement a Runnable see here for a short example, however I cannot … Read more
You have to create the Handler in the UI Thread, i.e. in onCreate of your Activity. Because you create it in the run method of a background thread, the handler will execute your code in that very same background thread. You could also initialize your Handler directly: public class MyActivity extends Activity{ private Handler handler … Read more
(1) On first start, Set _timer.Interval to the amount of milliseconds between the service start and schedule time. This sample set schedule time to 7:00 a.m. as _scheduleTime = DateTime.Today.AddDays(1).AddHours(7); (2) On Timer_Elapsed, reset _timer.Interval to 24 hours (in milliseconds) if current interval is not 24 hours. System.Timers.Timer _timer; DateTime _scheduleTime; public WinService() { InitializeComponent(); … Read more
you can go to Capabilities and turn on background mode and active Audio. AirPlay, and picture and picture. It really works . you don’t need to set DispatchQueue . you can use of Timer. Timer.scheduledTimer(withTimeInterval: 1, repeats: true) { (t) in print(“time”) }
Calendar today = Calendar.getInstance(); today.set(Calendar.HOUR_OF_DAY, 2); today.set(Calendar.MINUTE, 0); today.set(Calendar.SECOND, 0); // every night at 2am you run your task Timer timer = new Timer(); timer.schedule(new YourTask(), today.getTime(), TimeUnit.MILLISECONDS.convert(1, TimeUnit.DAYS)); // period: 1 day
DispatcherTimer is the regular timer. It fires its Tick event on the UI thread, you can do anything you want with the UI. System.Timers.Timer is an asynchronous timer, its Elapsed event runs on a thread pool thread. You have to be very careful in your event handler, you are not allowed to touch any UI … Read more
The difference is best explained by this non-Android documentation: Fixed-rate timers (scheduleAtFixedRate()) are based on the starting time (so each iteration will execute at startTime + iterationNumber * delayTime). In fixed-rate execution, each execution is scheduled relative to the scheduled execution time of the initial execution. If an execution is delayed for any reason (such … Read more
The easiest way to do this is to change the event handler into an anonymous function. It allows you to pass the string at the point of declaration. string theString = …; timer.Elapsed += (sender, e) => MyElapsedMethod(sender, e, theString); static void MyElapsedMethod(object sender, ElapsedEventArgs e, string theString) { … }
Since you also want to show the countdown, I would recommend a CountDownTimer. This has methods to take action at each “tick” which can be an interval you set in the constructor. And it’s methods run on the UI Thread so you can easily update a TextView, etc… In it’s onFinish() method you can call … Read more
As stated by both BFree and James, there is no difference in Start\Stop versus Enabled with regards to functionality. However, the decision on which to use should be based on context and your own coding style guidelines. It depends on how you want a reader of your code to interpret what you’ve written. For example, … Read more