#Online timer clock .net manual#
#Online timer clock .net code#
#Online timer clock .net Pc#
#Online timer clock .net download#

#Online timer clock .net Pc#

Fixed Countdown not starting unless pc had an IP address.

Really fixed settings version issue preventing user interface from loading correctly.

Negative signs removed from overtime (e.g.

UDP broadcast for Remote Display now opens a port on every active network interface, not just the first one it found.

Touch input no longer throws System.ArgumentException error.

No longer crashes if unable to open all network ports.

Settings version will not change unless more features and options are added. When upgrading, if the new version uses the current settings version then settings will be kept, else your settings will be reset. Settings now have their own version number.

Added 15 minute max limitation post-trial.

Escape key brings up user interface (to help in single display mode).

Messages can now be shown in Black mode.

#Online timer clock .net download#

Added option to announce if a new version is available for download.Added option to hide output display (for single screen + remote display usage).Added option to change background to transparent.Added option to change background color.Selecting Black mode now shows a blank Web view.Selecting Clock mode now shows a clock on Web view and UDP.Added alternative status feedback for Companion (available in 1.4 and 2.0 builds, not 1.3).Added new commands: JOG, MESSAGE, UPDATEMODE.Starting at 00:00:00 for 'stopwatch' mode no longer shows negative sign.All times now shown as hh:mm:ss to avoid hh:mm / mm:ss ambiguity.

#Online timer clock .net manual#

Added seconds to presets and manual selection.Corrected window position saved to config when exiting minimized UI window (no more 'where's my UI?').Behaviour change: elapsed time will also pause.Text encoding set to UTF8 to preserve accents etc.Public static Task DoActionAfter(TimeSpan delay, Action action) if you want your main method to wait for the action Var delayInterval = TimeSpan.FromMilliseconds(5000) To actually use the method: using System If you want to be able to cancel your action you should feed a CancellationToken into the method (and the delay). If it doesn't need the result straight away it can just store the task and check its status later.

#Online timer clock .net code#

Return Task.Delay(delay).ContinueWith(_ => action()) Īs you're returning a Task your code can synchronously wait using.

public static Task DoActionAfter(TimeSpan delay, Action action) You should also use TimeSpan to represent an interval - an int can mean many things, a TimeSpan represents the information unambiguously.įor the sake of completeness, for this trivial example I think it's clearer without the async and await but that's just personal preference. Your second option isn't bad but you should accept an action to run after the delay otherwise it won't be very flexible. Your first option is about as bad as it gets, it will thrash CPU because as far as the CPU is concerned that while loop is important work - it doesn't know you're just calculating a time over and over again. Without more context it's really hard to give you a particularly helpful answer but I can suggest a couple of things. I think they're both pretty easy to understand, but my uncertainty with C#'s async for the second solution and the CPU cycles being used for the first worry me. I also have this alternative when I was futzing around with async, which I'm kind of new to in C# using System Īsync static Task CountDownTimer(int delay)Īwait Task.Delay(TimeSpan.FromMilliseconds(delay)) If (timeDifference.TotalMilliseconds >= delayInMilliseconds) TimeSpan timeDifference = timeNow - initialTime Static void CountDown(int delayInMilliseconds) The time-range expected for the tool will be from 200 milliseconds to a few hours. The code below is what I have working for PoC, but when I went to make this and check out existing examples, none really seemed this slim/simple without going all-out on lambdas, so I'm worried that I'm doing something wrong, or at the very least very inefficiently. I'm looking to add a module to one of my utility classes that functions as a countdown timer for tools that execute tasks after a certain amount of time.