On Thu, 12 Apr 2018, Graeme Geldenhuys wrote:
On 2018-04-11 17:44, R0b0t1 wrote:
This is related to something I meant to propose a while ago related to
a cross platform timing and alarm API.
That already exists in the form of EpikTimer
(https://github.com/graemeg/epiktimer). That is the la
On 2018-04-11 17:44, R0b0t1 wrote:
> This is related to something I meant to propose a while ago related to
> a cross platform timing and alarm API.
That already exists in the form of EpikTimer
(https://github.com/graemeg/epiktimer). That is the latest
implementation with the permission of the or
Hi,
On Wed, 11 Apr 2018, Alexander Grotewohl wrote:
> Just to be clear, the 64 in GetTickCount64 has nothing to do with
> whether a machine is 32bit or 64bit.
The call itself, doesn't. Except, on a 32bit machine, when you have to do
64bit arithmetic/value handling, it's usually less optimal/more
El 11/04/18 a les 19:27, Alexander Grotewohl ha escrit:
It's deprecated by Microsoft.
It doesn't say anything about deprecation here
https://msdn.microsoft.com/en-us/library/windows/desktop/ms724408(v=vs.85).aspx
Bye
--
Luca
___
fpc-pascal maillist
Just to be clear, the 64 in GetTickCount64 has nothing to do with
whether a machine is 32bit or 64bit.
Alex
On 04/11/2018 01:23 PM, Karoly Balogh (Charlie/SGR) wrote:
Hi,
On Wed, 11 Apr 2018, Michael Van Canneyt wrote:
personally I use this 64 bit emulation:
For my purpose I'm perfectly h
On Wed, Apr 11, 2018 at 12:11 PM, Tomas Hajny wrote:
> On Wed, April 11, 2018 18:44, R0b0t1 wrote:
>
> .
> .
>> This is related to something I meant to propose a while
>> ago related to a cross platform timing and alarm API.
>> I do not think GetTickCount should ever be used;
>> instead, QueryPe
It's deprecated by Microsoft. If I had to guess, it's likely not going
anywhere until 32bit binary support in Windows is long gone.
Should you use GetTickCount on any Windows system that supports
(natively) GetTickCount64? NO, not in new code.
That's exactly what deprecated means.
IMO compil
Hi,
On Wed, 11 Apr 2018, Michael Van Canneyt wrote:
> >> personally I use this 64 bit emulation:
> >
> > For my purpose I'm perfectly happy with GetTickCount. I'd understand the
> > deprecation if GetTickCount64 would be a reliable substitute. It isn't.
>
> Only on XP. On all other platforms, it
On Wed, April 11, 2018 18:44, R0b0t1 wrote:
.
.
> This is related to something I meant to propose a while
> ago related to a cross platform timing and alarm API.
> I do not think GetTickCount should ever be used;
> instead, QueryPerformanceCounter makes more sense. It is
> higher resolution and
El 11/04/18 a les 18:42, Michael Van Canneyt ha escrit:
On Wed, 11 Apr 2018, Luca Olivetti wrote:
El 11/04/18 a les 13:59, Tobias Giesen ha escrit:
Hello,
personally I use this 64 bit emulation:
For my purpose I'm perfectly happy with GetTickCount. I'd understand
the deprecation if GetTi
On Wed, Apr 11, 2018 at 11:26 AM, Alexander Grotewohl wrote:
> The documentation seems fine. I can use it to approximate that a minute has
> elapsed, or to keep track of frames per second for a game, but I'm not going
> to use it to control complex machinery.
>
> The GetTickCount documentation off
On Wed, 11 Apr 2018, Luca Olivetti wrote:
El 11/04/18 a les 13:59, Tobias Giesen ha escrit:
Hello,
personally I use this 64 bit emulation:
For my purpose I'm perfectly happy with GetTickCount. I'd understand the
deprecation if GetTickCount64 would be a reliable substitute. It isn't.
Onl
The documentation seems fine. I can use it to approximate that a minute
has elapsed, or to keep track of frames per second for a game, but I'm
not going to use it to control complex machinery.
The GetTickCount documentation offers that most system timers are within
the 10 to 16 millisecond ran
El 11/04/18 a les 13:59, Tobias Giesen ha escrit:
Hello,
personally I use this 64 bit emulation:
For my purpose I'm perfectly happy with GetTickCount. I'd understand the
deprecation if GetTickCount64 would be a reliable substitute. It isn't.
Bye
--
Luca
_
El 11/04/18 a les 15:40, Paulo Costa ha escrit:
Unfortunate is the obscure wording you find on the documentation:
https://www.freepascal.org/docs-html/rtl/sysutils/gettickcount.html
Yes, you're right, but that's another issue.
When the documentation is vague and I need details I look at the
i
Unfortunate is the obscure wording you find on the documentation:
https://www.freepascal.org/docs-html/rtl/sysutils/gettickcount.html
"Description
GetTickCount returns an increasing clock tick count. It is useful for
time measurements, but no assumtions should be made as to the interval
betwee
On Sun, 8 Apr 2018 21:58:55 -0400
Ben Grasset wrote:
> I'm not at all getting why people think it's "kitten-like." Have you guys
> ever actually seen a kitten?
Sure, they look like this: https://tinyurl.com/y9hod4gg
> And a much better/more tasteful cheetah than that
> ancient, annoying "running
Hello,
personally I use this 64 bit emulation:
var CurrentIncrement:Int64=0;
LastTickCount:Int64=0;
function TGGetTickCount64:Int64;
begin
{$ifdef CPUX64}
Result:=GetTickCount64;
{$else}
Result:=GetTickCount+CurrentIncrement;
if Result wrote:
> El 11/04/18 a les 10:06, Luca Oliv
El 11/04/18 a les 10:06, Luca Olivetti ha escrit:
BEFORE (with gettickcount):
--
var PreviousTick:DWORD;
...
PreviousTick:=GetTickCount;
...
... if DWORD(GetTickCount-PreviousTick)>WaitTime then
BTW, the DWORD typeca
El 06/04/18 a les 00:06, wkitt...@windstream.net ha escrit:
On 04/05/2018 02:11 PM, Luca Olivetti wrote:
El 03/04/18 a les 13:14, Luca Olivetti ha escrit:
I was going to report a bug but I see it's already fixed
https://bugs.freepascal.org/view.php?id=30208
however it's still there in 3.0.4, re
GetTickCount has been deprecated in favor of GetTickCount64, which gives
a qword result and so it "solves" the wrap-arount to 0 of the tick after
49.7 days, so one doesn't have to worry that the expression
GetTickCount64-PreviousTick
will ever give a negative result, and
if GetTickCount6
21 matches
Mail list logo
