QB64/QB64-PE
QB64/QB64-PE
1
1
Fork 0
mirror of https://github.com/QB64-Phoenix-Edition/QB64pe.git synced 2024-06-03 01:50:14 +00:00
Code Issues Releases Wiki Activity
QB64-PE/internal/c/libqb/include/datetime.h

33 lines
684 B
C
Raw Normal View History

Replace time() with std::chrono, fix startup delay Currently main() includes logic that is intended to sync time() with GetTicks() for the purpose of using GetTicks() to get millisecond accuracy with time(), which only has second accuracy. Unfortunately, the 'syncing' up of these time sources results in an average of a half second delay in starting a QB64-PE program. This logic is easly replaced with std::chrono, which provides a real time clock which is also millisecond accurate. That removes the need to use time() and GetTicks() together to get millisecond accuracy, and means the delay syncing them is no longer necessary. I also separated most of the "delay" and "time" related functions into datetime.cpp, and included the new std::chrono code into that file. Since I needed to call some of the rounding functions in datetime.cpp I also moved that stuff out into its own .cpp and header files to clean things up a bit. Fixes: #282
2023-01-08 07:41:54 +00:00
#ifndef INCLUDE_LIBQB_DATETIME_H
#define INCLUDE_LIBQB_DATETIME_H
Move more date/time functions
2024-02-13 06:07:07 +00:00
#include <stdint.h>
#include "qbs.h"
Make Linux GetTicks() start from zero Since the GetTicks() is visible in the logging, it's useful to have it start from zero rather than an arbitrary number.
2024-03-11 16:53:42 +00:00
#ifdef QB64_LINUX
// Initializes the clock returned by 'GetTicks()' so that it starts from zero
// Should be called at the very beginning of the program
void clock_init();
#else
static inline void clock_init() { }
#endif
Replace time() with std::chrono, fix startup delay Currently main() includes logic that is intended to sync time() with GetTicks() for the purpose of using GetTicks() to get millisecond accuracy with time(), which only has second accuracy. Unfortunately, the 'syncing' up of these time sources results in an average of a half second delay in starting a QB64-PE program. This logic is easly replaced with std::chrono, which provides a real time clock which is also millisecond accurate. That removes the need to use time() and GetTicks() together to get millisecond accuracy, and means the delay syncing them is no longer necessary. I also separated most of the "delay" and "time" related functions into datetime.cpp, and included the new std::chrono code into that file. Since I needed to call some of the rounding functions in datetime.cpp I also moved that stuff out into its own .cpp and header files to clean things up a bit. Fixes: #282
2023-01-08 07:41:54 +00:00
int64_t GetTicks();
double func_timer(double accuracy, int32_t passed);
void sub__delay(double seconds);
void sub__limit(double fps);
// We provide a 'Sleep()' function for non-Windows platforms
#ifndef QB64_WINDOWS
void Sleep(uint32_t milliseconds);
#endif
Move more date/time functions
2024-02-13 06:07:07 +00:00
qbs *func_time();
void sub_time(qbs *str);
qbs *func_date();
void sub_date(qbs *date);
Replace time() with std::chrono, fix startup delay Currently main() includes logic that is intended to sync time() with GetTicks() for the purpose of using GetTicks() to get millisecond accuracy with time(), which only has second accuracy. Unfortunately, the 'syncing' up of these time sources results in an average of a half second delay in starting a QB64-PE program. This logic is easly replaced with std::chrono, which provides a real time clock which is also millisecond accurate. That removes the need to use time() and GetTicks() together to get millisecond accuracy, and means the delay syncing them is no longer necessary. I also separated most of the "delay" and "time" related functions into datetime.cpp, and included the new std::chrono code into that file. Since I needed to call some of the rounding functions in datetime.cpp I also moved that stuff out into its own .cpp and header files to clean things up a bit. Fixes: #282
2023-01-08 07:41:54 +00:00
#endif
Copy permalink