Uptime On Your App

[Randy Walker]

GetTickCount_() doesn't work after 49.7 days of uptime, so it's not usable for this sort of thing. Microsoft says to use GetTickCount64() instead, but that's not immediately available in PureBasic as a single API command. Someone else here will surely step in and show how to use it.

Hi BarryG. once again you are quite correct. And yes someone did share the cetTickCount64() solution so I am posting the sample code here that I saved previously and leave it at that. Enough sample code here now for someone else to put the pieces together if they want it bad enough:

Code: Select all

EnableExplicit

Define Milliseconds
Define H
Define M
Define s

If OpenLibrary(0, "Kernel32.dll")
  Prototype GetTickCount64()
  Define GetTickCount64.GetTickCount64 = GetFunction(0, "GetTickCount64")
  CloseLibrary(0)
EndIf

Milliseconds = GetTickCount64()

H=Milliseconds/3600000
M=Milliseconds/60000-(H*60)
s=Milliseconds/1000-(H*3600+M*60)

Debug GetTickCount64()

[Randy Walker]

Also, shouldn't ElapsedMilliseconds() work too (and be cross platform)?

I could be wrong but I think it has the same limitation as GetTickCount_()
Otherwise, yes, You could substitute using ElapsedMilliseconds()

[Randy Walker]

Uptime = Time since PC started.
Runtime = How long the app has been running.

That's what my comments are based on.

Simantics Shimantics. Plenty tricks and tips came out of my original post so it's all good.

[BarryG]

Just read the first sentence Randy wrote. The uptime if his program. Period.

Okay. My bad.

I could be wrong but I think it has the same limitation as GetTickCount_()
Otherwise, yes, You could substitute using ElapsedMilliseconds()

ElapsedMilliseconds() is a Quad, so doesn't have the same 49.7 day limit as GetTickCount_(), which is a Word.

You can just use Date() like my previous post shows (viewtopic.php?p=643842#p643842), and avoid "Prototype GetTickCount64()" altogether. Why add extra code that isn't needed?

[Randy Walker]

Just read the first sentence Randy wrote. The uptime if his program. Period.

Okay. My bad.

I could be wrong but I think it has the same limitation as GetTickCount_()
Otherwise, yes, You could substitute using ElapsedMilliseconds()

ElapsedMilliseconds() is a Quad, so doesn't have the same 49.7 day limit as GetTickCount_(), which is a Word.

Well OK then. Good clarification.

You can just use Date() like my previous post shows (viewtopic.php?p=643842#p643842), and avoid "Prototype GetTickCount64()" altogether. Why add extra code that isn't needed?

You're right! Date() is also a great solution. Tips beget tips. Thank again BarrtG!!

[Randy Walker]

I wanted to be able to know how long my app was up and running.

Just use the value of Date() when your app starts, and keep calculating its runtime from that. To get you started:

Code: Select all

start.q=Date()

Repeat
  Sleep_(1000)
  Debug "App runtime is: "+FormatDate("%hh:%ii:%ss",Date()-start)
ForEver

Ok BarryG... Like I said at the start FormatDate failed me same as it does with your code, modified to in iclude %dd

Code: Select all

+FormatDate("%dd/%hh:%ii:%ss",Date()-start)

App runtime is: 01/00:00:01
App runtime is: 01/00:00:02
App runtime is: 01/00:00:03
App runtime is: 01/00:00:04
App runtime is: 01/00:00:05
App runtime is: 01/00:00:06
App runtime is: 01/00:00:07
App runtime is: 01/00:00:08
App runtime is: 01/00:00:09

It still is erroneously adding an extra day.

[Demivec]

Ok BarryG... Like I said at the start FormatDate failed me same as it does with your code, modified to in iclude %dd

Code: Select all

+FormatDate("%dd/%hh:%ii:%ss",Date()-start)

App runtime is: 01/00:00:01
App runtime is: 01/00:00:02
App runtime is: 01/00:00:03
App runtime is: 01/00:00:04
App runtime is: 01/00:00:05
App runtime is: 01/00:00:06
App runtime is: 01/00:00:07
App runtime is: 01/00:00:08
App runtime is: 01/00:00:09

It still is erroneously adding an extra day.

Date() Returns an accurate time in seconds that can be used as a start time value and also to calculate the time difference in seconds (timeDifference = currentTime - startTime).

FormatDate() is inadequate for displaying elapsed time because it is tailored for displaying dates. So days range from 1 - 31 and hours from 0 to 23, etc.

You have to use your own routine to display the time elapsed like others have shared earlier in this thread.

[HeX0R]

here is another one

Code: Select all

Procedure$ GetUpTime(Showms = #False)
	Protected ems.q, seconds.q, ms, days, hours, minutes, Result$

	ems     = ElapsedMilliseconds()
	seconds = ems / 1000
	ms      = ems - seconds * 1000
	days    = seconds / 86400
	seconds - days * 86400
	hours   = seconds / 3600
	seconds - hours * 3600
	minutes = seconds / 60
	seconds - minutes * 60
	Result$ = Str(days) + "/" + RSet(Str(hours), 2, "0") + ":" + RSet(Str(minutes), 2, "0") + ":" + RSet(Str(seconds), 2, "0")
	
	If Showms
		Result$ + "." + Left(Str(ms), 1)
	EndIf

	ProcedureReturn Result$
EndProcedure

Procedure TimerEvent()
	SetWindowTitle(0, "Up Time       " + GetUpTime(#True))
EndProcedure

;ElapsedMilliseconds() ;<- call once at the beginning, or just use GetUpTime() regularly, like in this example
OpenWindow(0, 0, 0, 300, 300, "Up Time", #PB_Window_SystemMenu | #PB_Window_ScreenCentered)
AddWindowTimer(0, 0, 80)
BindEvent(#PB_Event_Timer, @TimerEvent())


Repeat : Until WaitWindowEvent() = #PB_Event_CloseWindow

[Randy Walker]

here is another one

Uhhh, But for some reason yours is ahowing 4/ days plus the tick up. This wont work either.

[Randy Walker]

You have to use your own routine to display the time elapsed like others have shared earlier in this thread.

Yes, as I did in my OP.

[HeX0R]

here is another one

Uhhh, But for some reason yours is ahowing 4/ days plus the tick up. This wont work either.

The reason is, you are using an older PB version and your PC is since 4 days on.

[Randy Walker]

here is another one

Uhhh, But for some reason yours is ahowing 4/ days plus the tick up. This wont work either.

The reason is, you are using an older PB version and your PC is since 4 days on.

That's amazing how you deduce that, How? PC was up 4 days+ and I was testing on PB ver5.40

[Demivec]

here is another one

Uhhh, But for some reason yours is ahowing 4/ days plus the tick up. This wont work either.

The reason is, you are using an older PB version and your PC is since 4 days on.

That's amazing how you deduce that, How? PC was up 4 days+ and I was testing on PB ver5.40

Hexor is amazing but Sherlock would tell you that the deduction was an elementary process in light of the facts that prior to PureBasic v5.60, ElapsedMilliseconds() returned values based on the uptime of the computer. In v5.60 and later it, ElapsedMilliseconds() returned a value of zero on the first call and the elapsed time on subsequent calls.

Thus Hexor reached the only conclusion that was reachable given the time he posted the code sample and how soon you posted your results that exceed 4 days time.