[Release] TimeOut functions

Page 1 of 2

03/24/2015 23:51 pintinho12#1

Hello guys, i think this will be my first real contribution to the forum. By the way, it's nothing so hard to do heheh.

I've been working on my WCProject and on the Battle System that is based on Demons Source, i noticed that they have those classes implemented.
Firstly, i tried using what most sources use, DateTime and Environment.TickCount, I don't know if this class will save or spend more resources, but i don't need to rewrite Update and Reset codes all the time, and it got a lot easier to code timers with this now.

Note: This do not execute anything automatically, just stores the time.

First, you need a Unix Timestamp class, something to return Seconds and Milliseconds.
I will provide my code, if you have anything better to contribute, i will edit here.

Unix Timestamp.cs

Spoiler

Code:

using System;

namespace Core.Common
{
    public static class UnixTimestamp
    {
        public static readonly DateTime UnixEpoch = new DateTime(1970, 1, 1, 0, 0, 0, 0);

        public const int TIME_SECONDS_MINUTE = 60;
        public const int TIME_SECONDS_HOUR = 60 * TIME_SECONDS_MINUTE;
        public const int TIME_SECONDS_DAY = 24 * TIME_SECONDS_HOUR;

        public static DateTime ToDateTime(uint timestamp)
        {
            return UnixEpoch.AddSeconds(timestamp);
        }

        public static int Timestamp()
        {
            return Convert.ToInt32((DateTime.Now - new DateTime(1970, 1, 1, 0, 0, 0, 0).ToUniversalTime()).TotalSeconds);
        }

        public static long LongTimestamp()
        {
            return Convert.ToInt64((DateTime.Now - new DateTime(1970, 1, 1, 0, 0, 0, 0).ToUniversalTime()).TotalMilliseconds);
        }

        public static int Timestamp(DateTime time)
        {
            return Convert.ToInt32((time - new DateTime(1970, 1, 1, 0, 0, 0, 0).ToUniversalTime()).TotalSeconds);
        }

        public static long LongTimestamp(DateTime time)
        {
            return Convert.ToInt64((time - new DateTime(1970, 1, 1, 0, 0, 0, 0).ToUniversalTime()).TotalMilliseconds);
        }

        public static int MonthDayStamp()
        {
            return Convert.ToInt32((DateTime.Now - new DateTime(DateTime.Now.Year, 1, 1, 0, 0, 0, 0).ToUniversalTime()).TotalSeconds);
        }

        public static int MonthDayStamp(DateTime time)
        {
            return Convert.ToInt32((time - new DateTime(DateTime.Now.Year, 1, 1, 0, 0, 0, 0).ToUniversalTime()).TotalSeconds);
        }

        public static int DayOfTheMonthStamp()
        {
            return Convert.ToInt32((DateTime.Now - new DateTime(DateTime.Now.Year, DateTime.Now.Month, 1, 0, 0, 0, 0).ToUniversalTime()).TotalSeconds);
        }

        public static int DayOfTheMonthStamp(DateTime time)
        {
            return Convert.ToInt32((time - new DateTime(DateTime.Now.Year, DateTime.Now.Month, 1, 0, 0, 0, 0).ToUniversalTime()).TotalSeconds);
        }
    }
}

*
Below, i have the TimeOut and TimeOutMS classes.
TimeOut hasn't been tested yet, but i am using TimeOutMS on my Meele Attack, and it's working like a boss.

Spoiler

Code:

// World Conquer Project - Phoenix Project Based
// Source Development by Felipe Vieira (FTW! Masters)
// Source Infrastructure by Gareth Jensen (Akarui)
// 
// Computer User: Administrador
// File Created by: Felipe Vieira Vendramini
// zfserver - MsgServer - TimeOut.cs
// File Created: 2015/01/13 00:53

// This is the UnixTimestamp location
using Core.Common;

namespace MsgServer.Structures
{
    public sealed class TimeOut
    {
        private int _updateTime;
        private int _interval;

        public TimeOut(int nInterval)
        {
            _interval = nInterval;
            _updateTime = 0;
        }

        public int clock() { return UnixTimestamp.Timestamp(); }
        public bool Update() { _updateTime = clock(); return true; }
        public bool IsTimeOut() { return clock() >= _updateTime + _interval; }
        public bool ToNextTime()
        {
            if (IsTimeOut())
                return Update();
            return false;
        }
        public void SetInterval(int nSecs) { _interval = nSecs; }
        public void Startup(int nSecs) { _interval = nSecs; Update(); }
        public bool TimeOver()
        {
            if (IsActive() && IsTimeOut()) return Clear();
            return false;
        }
        public bool IsActive() { return _updateTime != 0; }
        public bool Clear() { _updateTime = _interval = 0; return true; }

        public void IncInterval(int nSecs, int nLimit) { _interval = Calculations.CutOverflow(_interval + nSecs, nLimit); }
        public void DecInterval(int nSecs) { _interval = Calculations.CutTrail(_interval - nSecs, 0); }

        public bool IsTimeOut(int nSecs) { return clock() >= _updateTime + nSecs; }
        public bool ToNextTime(int nSecs) { if (IsTimeOut(nSecs)) return Update(); return false; }
        public bool TimeOver(int nSecs) { if (IsActive() && IsTimeOut(nSecs)) return Clear(); return false; }

        public bool ToNextTick(int nSecs)
        {
            if (IsTimeOut(nSecs))
            {
                if (clock() >= _updateTime + nSecs * 2)
                    return Update();
                _updateTime += nSecs;
                return true;
            }
            return false;
        }

        public int GetRemain() { return _updateTime != 0 ? Calculations.CutRange(_interval - ((int)clock() - (int)_updateTime), 0, _interval) : 0; }
        public int GetInterval() { return _interval; }
    }

    public sealed class TimeOutMS
    {
        private long _updateTime;
        private int _interval;

        public TimeOutMS(int nInterval)
        {
            _interval = nInterval;
            _updateTime = 0;
        }
        public long clock() { return UnixTimestamp.LongTimestamp(); }
        public bool Update() { _updateTime = clock(); return true; }
        public bool IsTimeOut() { return clock() >= _updateTime + _interval; }
        public bool ToNextTime()
        {
            if (IsTimeOut())
                return Update();
            return false;
        }
        public void SetInterval(int nMilliSecs) { _interval = nMilliSecs; }
        public void Startup(int nMilliSecs) { _interval = nMilliSecs; Update(); }
        public bool TimeOver()
        {
            if (IsActive() && IsTimeOut()) return Clear();
            return false;
        }
        public bool IsActive() { return _updateTime != 0; }
        public bool Clear() { _updateTime = _interval = 0; return true; }

        public void IncInterval(int nMilliSecs, int nLimit) { _interval = Calculations.CutOverflow(_interval + nMilliSecs, nLimit); }
        public void DecInterval(int nMilliSecs) { _interval = Calculations.CutTrail(_interval - nMilliSecs, 0); }

        public bool IsTimeOut(int nMilliSecs) { return clock() >= _updateTime + nMilliSecs; }
        public bool ToNextTime(int nMilliSecs) { if (IsTimeOut(nMilliSecs)) return Update(); return false; }
        public bool TimeOver(int nMilliSecs) { if (IsActive() && IsTimeOut(nMilliSecs)) return Clear(); return false; }

        public bool ToNextTick(int nMilliSecs)
        {
            if (IsTimeOut(nMilliSecs))
            {
                if (clock() >= _updateTime + nMilliSecs * 2)
                    return Update();
                _updateTime += nMilliSecs;
                return true;
            }
            return false;
        }

        public int GetRemain() { return _updateTime != 0 ? Calculations.CutRange(_interval - ((int) clock() - (int)_updateTime),0 ,_interval) : 0; }
        public int GetInterval() { return _interval; }
    }
}

I will provide commented code and examples later. ^_^
Hope it helps anyone #00

Almost forgot...
Calculations does contains this

Spoiler

Code:

public static long CutTrail(long x, long y) { return (x >= y) ? x : y; }
        public static long CutOverflow(long x, long y) { return (x <= y) ? x : y; }
        public static long CutRange(long n, long min, long max) { return (n < min) ? min : ((n > max) ? max : n); }

        public static int CutTrail(int x, int y) { return (x >= y) ? x : y; }
        public static int CutOverflow(int x, int y) { return (x <= y) ? x : y; }
        public static int CutRange(int n, int min, int max) { return (n < min) ? min : ((n > max) ? max : n); }

        public static short CutTrail(short x, short y) { return (x >= y) ? x : y; }
        public static short CutOverflow(short x, short y) { return (x <= y) ? x : y; }
        public static short CutRange(short n, short min, short max) { return (n < min) ? min : ((n > max) ? max : n); }

        public static ulong CutTrail(ulong x, ulong y) { return (x >= y) ? x : y; }
        public static ulong CutOverflow(ulong x, ulong y) { return (x <= y) ? x : y; }
        public static ulong CutRange(ulong n, ulong min, ulong max) { return (n < min) ? min : ((n > max) ? max : n); }

        public static uint CutTrail(uint x, uint y) { return (x >= y) ? x : y; }
        public static uint CutOverflow(uint x, uint y) { return (x <= y) ? x : y; }
        public static uint CutRange(uint n, uint min, uint max) { return (n < min) ? min : ((n > max) ? max : n); }

        public static ushort CutTrail(ushort x, ushort y) { return (x >= y) ? x : y; }
        public static ushort CutOverflow(ushort x, ushort y) { return (x <= y) ? x : y; }
        public static ushort CutRange(ushort n, ushort min, ushort max) { return (n < min) ? min : ((n > max) ? max : n); }

        public static byte CutTrail(byte x, byte y) { return (x >= y) ? x : y; }
        public static byte CutOverflow(byte x, byte y) { return (x <= y) ? x : y; }
        public static byte CutRange(byte n, byte min, byte max) { return (n < min) ? min : ((n > max) ? max : n); }

03/25/2015 01:30 pro4never#2

Unless I'm blind and missing something, all that code is just a fancy way of dealing with unix timestamps and has nothing to do with actually DELAYING an action.

There's no threading referenced and there's no actions.

Not saying it can't be useful but just seems like a needlessly large amount of code when it's not actually accomplishing something.

03/25/2015 08:52 Xio.#3

[Only registered and activated users can see links. Click Here To Register...]

I wrote that a few weeks ago. Take a look

03/25/2015 13:59 -impulse-#4

This code has a bit more overhead than is needed. Instead of using DateTime to get the Unix time you could use Environment.TickCount which gives you more resolution to work with (milliseconds instead of seconds). The only "issue" with using Environment.TickCount over Unix time is that every 43 or so days the tick count resets to 0.

03/25/2015 14:27 pintinho12#5

This does not have anything to do with Threading.
I have an OnTimer method on my classes that will need things handled.
The point is that i can use var tm = new TimeOut(5); and check elsewhere with .ToNextTime() or .IsTimeOut()
When I get back home tonight I will check the sugestions, tho, this class works pretty fine, since i use both on my Status handlers, for shackle, fog, etc
Ty for the feedback.

03/25/2015 14:37 Xio.#6

Quote:

Originally Posted by -impulse-

This code has a bit more overhead than is needed. Instead of using DateTime to get the Unix time you could use Environment.TickCount which gives you more resolution to work with (milliseconds instead of seconds). The only "issue" with using Environment.TickCount over Unix time is that every 43 or so days the tick count resets to 0.

Every 25 days and its a 100 ns increment not a ms increment. If you need more accuracy you can use the Stopwatch class.

03/25/2015 18:49 -impulse-#7

Quote:

Originally Posted by Xio.

Every 25 days and its a 100 ns increment not a ms increment. If you need more accuracy you can use the Stopwatch class.

1 ms.

[Only registered and activated users can see links. Click Here To Register...]

And if you use Environment.TickCount as an unsigned number you get 49.8 days.

03/25/2015 20:43 Xio.#8

Quote:

Originally Posted by -impulse-

1 ms.

[Only registered and activated users can see links. Click Here To Register...]

And if you use Environment.TickCount as an unsigned number you get 49.8 days.

Wow thanks, I thought Ticks is the same o_o

[Only registered and activated users can see links. Click Here To Register...]

03/26/2015 05:46 pintinho12#9

So, if i use that on this same function, i will save a lot of time then?

03/26/2015 13:11 -impulse-#10

Quote:

Originally Posted by pintinho12

So, if i use that on this same function, i will save a lot of time then?

Not "a lot" but that something adds up to a whole lot after a while. Yes, it's worthwhile changing your base (Unix timestamp) to the local TickCount. If you need stuff like day of the month you should use DateTime.UtcNow because it's a bit faster but for keeping stamps of seconds it's faster to use TickCount. Depends on the usage really.

03/26/2015 14:42 pintinho12#11

It's most used for methods that wont store more than a few minutes or hours, i believe the server wouldn't be more than a 2-3 days online without a restart, so i think that this will be great. I'll take a look at this tonight.

03/27/2015 01:08 U2_Caparzo#12

I checked your project, you are trying to make it the more similar possible to the EO source, so why not keep doing it that way, it may become a really useful resource for those who are much more familiar with C# than C++

Anyways, because of the topic i'm posting this :p , i coded a task scheduler few months ago as well, it was supposed to handle things like remove items from floor, effects, etc... i think that it's a decent one (except that the PriorityQueue is List based and insert should be far away from O(log n) ^^)

Use example:

Code:

        public static TaskScheduler TaskScheduler;
        static void Main(string[] args)
        {
            TaskScheduler = new TaskScheduling.TaskScheduler();
            ScheduledAction<string, string> delayedAction1 = new ScheduledAction<string, string>(Write, DateTime.Now.Second.ToString(), "This action is executed in the TaskScheduler thread");
            ScheduledAction<string, string> delayedAction2 = new ScheduledAction<string, string>(Write, DateTime.Now.Second.ToString(), "This action is executed in the ThreadPool");
            delayedAction2.ExecuteInThreadPool = true;  // default = false, false to execute the action in the TaskScheduler thread, or true to execute 
                                                        // in the ThreadPool, note that if the action takes too long to finish and is not executed
                                                        // in the ThreadPool, next actions may be executed with an extra delay
            TaskScheduler.Schedule(delayedAction1, 3000);
            TaskScheduler.Schedule(delayedAction2, 5000);
            Console.WriteLine("Actions added to the TaskScheduler at second " + DateTime.Now.Second);
            delayedAction2.Await();     // Blocks the thread untill the ScheduledAction has been executed
            Console.WriteLine("\ndelayed action 2 executed at second " + DateTime.Now.Second);
            TaskScheduler.Stop();
            Exit();
        }

        static void Exit()
        {
            Console.WriteLine("Press any key to exit...");
            Console.ReadKey();
        }

        static void Write(string value0, string value1)
        {
            Console.WriteLine("\n\t" + value1 + "\n");
            Console.WriteLine("\t\t[ThreadId=" + Thread.CurrentThread.ManagedThreadId + "] Original DateTime second: " + value0);
            Console.WriteLine("\t\t[ThreadId=" + Thread.CurrentThread.ManagedThreadId + "] Now DateTime second: " + DateTime.Now.Second);
        }

03/27/2015 01:43 pintinho12#13

Just came back from work and got some things to do, i will do a check on this later too, thanks. xD
I think that using while and Thread.Sleep() is awful, so those things might be useful to me.

03/27/2015 13:41 KraHen#14

Instead of Thread.Sleep(1) in a loop you can use WaitOne with a time parameter.

03/27/2015 20:59 -impulse-#15

Quote:

Originally Posted by KraHen

Instead of Thread.Sleep(1) in a loop you can use WaitOne with a time parameter.

It won't make any difference. Other than beautifying your code, maybe. Although if you use WaitOne/Sleep in a piece of code, that code shouldn't really appear in lots of places in the source, because you shouldn't Sleep your working threads anywhere.

Probably off-topic:
Depending on the OS, Windows in our case, every thread has a given time span to do its job then when it calls Sleep(...) it sleeps at least the rest of that time span. For Windows it's 20 ms (+/-), so even if you trigger the event you called for WaitOne, it will still wait until the 20 ms are done.

Even more weirder, is that calling something like Thread.Sleep(20) would return one time after 20 ms and one time after like 36 ms.
Anyway, you can't really have a task scheduler that works with millisecond values under like 40. Unless I am wrong and someone knows a way to go have more accuracy, in which case I beg you to show me how.

Page 1 of 2