VB - OnTheClock

A simple app really. Just threw it together to keep track of how long I've been working on something so I knew how much to bill a client for coding time, documentation time, etc. One could always add "always on top" code should it be desired.

Didn't make allowances for going past 24 hours because, regardless of how intense anyone is, they wouldn't need this app if they were at something that long, they'd need their head examined! :cool: [obviously the code could be amended to do that should you really need it]

Here's the code and a screen shot (ID labels added to screenshot so you can tie back to the code; obviously actual form wouldn't have these ID's displayed):

http://www.vbforums.com/attachment.php?postid=1439045

VB Code:

'****************************************************
'*
'* Simple application employing the use of a Timer to
'* determine what time an application started, keep track
'* of the current time, and use those two pieces of info
'* to determine how long the application has been running.
'*
'* Primary purpose for developing this application was to
'* have a tool to keep track of how long I've been coding
'* an application for billing purposes.
'*
'****************************************************
 
Option Explicit
Dim startHour As String
Dim startMinute As String
Dim startSecond As String
Dim startTotal As Long
Dim currentHour As String
Dim currentMinute As String
Dim currentSecond As String
Dim currentTotal As Long
Dim elapsedHour As Long
Dim elapsedMinute As Long
Dim elapsedSecond As Long
Dim elapsedTotal As Long
Dim startAmPm As String
Dim currentAmPm As String
Dim ampmFlag As Boolean
 
Private Sub cmdUpdateRunTime_Click()
Dim length As Long
    
    currentAmPm = Mid(Time, Len(Time) - 1, 2)
 
    'Set flag
    If (startAmPm = "AM" And currentAmPm = "AM") Or (startAmPm = "PM" And currentAmPm = "PM") Then
        ampmFlag = False
    Else
        ampmFlag = True
    End If
 
    length = HowLong(startHour, startMinute, startSecond)
    lblElapsedHours.Caption = elapsedHour
    lblElapsedMinutes.Caption = elapsedMinute
    lblElapsedSeconds.Caption = elapsedSecond
End Sub
 
Private Sub Form_Load()
Dim a As String
 
    Timer1.Interval = 1
    lblStartTime.Caption = Time
    startSecond = Mid$(lblStartTime.Caption, Len(lblStartTime.Caption) - 4, 2)
    startMinute = Mid$(lblStartTime.Caption, Len(lblStartTime.Caption) - 7, 2)
    If Len(lblStartTime.Caption) > 10 Then
        startHour = Mid$(lblStartTime.Caption, Len(lblStartTime.Caption) - 10, 2)
    Else
        startHour = Mid$(lblStartTime.Caption, Len(lblStartTime.Caption) - 9, 1)
    End If
    
    'Because of the way elapsed time is calculated, must keep
    'track of AM/PM portion of Start time for comparison when
    'elapsed time is eventually calculated
    startAmPm = Mid$(lblStartTime.Caption, Len(lblStartTime.Caption) - 1, 2)
 
End Sub
 
Private Sub Timer1_Timer()
    lblCurrentTime.Caption = Time
End Sub
Public Function HowLong(ByVal startHour As String, ByVal startMinute As String, ByVal startSecond As String) As Long
 
currentSecond = Mid$(Time, Len(Time) - 4, 2)
currentMinute = Mid$(Time, Len(Time) - 7, 2)
If Len(Time) > 10 Then
    currentHour = Mid$(Time, Len(Time) - 10, 2)
Else
    currentHour = Mid$(Time, Len(Time) - 9, 1)
End If
 
If ampmFlag = True And currentHour <> 12 Then
    currentHour = currentHour + 12
End If
    
startTotal = (startHour * 3600) + (startMinute * 60) + startSecond
currentTotal = (currentHour * 3600) + (currentMinute * 60) + currentSecond
elapsedTotal = currentTotal - startTotal
 
'Application is active less than 1 minute
If elapsedTotal < 60 Then
    elapsedHour = 0
    elapsedMinute = 0
    elapsedSecond = elapsedTotal
End If
 
'Application is active for more than 1 minute
'but less than 1 hour
If elapsedTotal >= 60 And elapsedTotal < 3600 Then
    elapsedHour = 0
    elapsedSecond = elapsedTotal Mod 60
    elapsedMinute = (elapsedTotal - elapsedSecond) / 60
End If
 
'Application is active for 1 hour or more
If elapsedTotal >= 3600 Then
    elapsedHour = (elapsedTotal - (elapsedTotal Mod 3600)) / 3600
    elapsedSecond = (elapsedTotal - (elapsedHour * 3600)) Mod 60
    elapsedMinute = (elapsedTotal - (elapsedHour * 3600) - elapsedSecond) / 60
End If
 
End Function

i do remember something from a book that would be of some concern to you, doofusboy. if memory serves right, it is from the black book of vb programming. i wont be able to put the exact sam phrase here but i can put the sense right, if you know what i mean.

Quote:

---

while using a timer control may be a very easy way to calculate the time interval of anything, it can also be unpredictable as it gives more preference to other processes running in the system than itself. this infers that if the interval of a timer is set for 60,000 (i.e., 1 min=60 sec), and the computer is going thru some stressful calculations like rendering some 3D pic or animation, or some games, the timer may show your time to be 1 minute but in reality it will exceed the 1 minute mark. so it is not recommended to put all your faith in the timer control if being used for long durations in stressful environments.

---

mebhas,

of this I was aware, but doesn't generally apply in my case for the development work that I do. but it's a good "heads up" for those that aren't aware of it! :)

i am now working on a project based on your clock. i will make the project of three categories; single user, medium user and the massive user. single user, of course, for a single computer. medium user for a lan based workgroup. the massive user will be for a multiple users working with the same project from all around the world. i will have to make a separate server for the multi user support of course.

i am telling this as the closk was your idea and i am building on it. is it okay???

Sure it's OK ! :) I posted it in hopes it might help someone. Glad you found a use for it !

(keep in mind that I did NOT make allowances for this application to be running for more than 24 hours; although I'm sure it could be enhanced with logic to handle that eventuality)

Perhaps you'll be as kind to share with us what you come up with too ?

I think this was the paragraph you were referring to...

Quote:

---

From VB Black Book You shouldn’t count on a timer too closely if your task execution is dependent on exact intervals; if the system is busy executing long loops, intensive calculations, or drive, network, or port access (in which case software routinely disables the timer interrupt), your application may not get Timer events as often as the Interval property specifies. That is to say, Timer events are not guaranteed to happen exactly on time. If you need to be sure, your software should check the system clock when it needs to (using, for example, the Visual Basic Time$ function), rather than try to keep track of time internally.

---

I was thinking of simply checking Now() at the beginning and end of your app usage to determine the start/end times, as you can see, this text recommends the same thing (but using Time$)...

Quote:

---

From VB Black Book You shouldn’t count on a timer too closely if your task execution is dependent on exact intervals; if the system is busy executing long loops, intensive calculations, or drive, network, or port access (in which case software routinely disables the timer interrupt), your application may not get Timer events as often as the Interval property specifies. That is to say, Timer events are not guaranteed to happen exactly on time. If you need to be sure, your software should check the system clock when it needs to (using, for example, the Visual Basic Time$ function), rather than try to keep track of time internally.

---

Don't think that is an issue here.

Seems to me that in this case it is more important to let the application get on with its job than to have exactly accurate times - therefore this is a very appropriate use of a timer as it wil do just exactly that.

Quote:

---

Don't think that is an issue here....it is more important to let the application get on with its job than to have exactly accurate times - therefore this is a very appropriate use of a timer as it wil do just exactly that.

---

How is it not an issue? The "job" of the app is to determine how long itself has been running...why would accurate times not be important? Why is the original program coded to determine SECONDS if this is not important?

I am not sure WHY you would use a Timer to (accurately) determine elapsed time or to keep the current time unless you can be sure no other processes will not interfere with the Timer (but why take the chance?)
???????????????????????????????????????????

IMO the system clock and a simple Datediff would do the trick with much less to-do...

...lol...i use a notepad to keep track of my hours (to the nearest 15 minutes...not seconds) but whatever works for ya... :p

Using the Date data type would be easier, faster and shorter. You can use the DateDiff function to compare times and Format() to output formatted time dates...

Quote:

---

Originally posted by Bean
[B]How is it not an issue? The "job" of the app is to determine how long itself has been running...

---

If you re-read the original post, you will see that the intent is to measure how long he has been working on the application for billing purposes. Not something that needs great accuracy.

Even if he WAS trying to time the app, then using a methiod which itself interferes with the timing would not be appropriate and DateDiff would be better, as you say. But for what he is doing, the timer is fine. Horses for courses.

WOW! :eek: Had no idea posting such a SIMPLE app would create such an uproar [operative word being 'simple' as stated in original post].

For those concerned about accuracy, please reread the code I used. The system time IS used when measuring elapsed time. The ONLY thing the Timer control is used for in this application is to display a running current time on the form [and yes, there are other ways to do that, using a boolean for example].

Perhaps it was the wording used in my comments at the beginning of the code that confused some of you. Sorry about that. Hope the above clarifies things for you.

I will go back and edit the comment section of the code once I figure out less confusing wording.

By the way, using the DateDiff function can cause some inconsistent 'rounding' problems when trying to determine how many hours, minutes, seconds have elapsed. When I tested it, it was sometimes rounding minutes when only 25 seconds had elapsed and at other times took as long as 42 seconds before the rounding issue arose.

Just to keep everybody happy, I removed the Timer control from the form, modified the code to keep displaying the current time without the timer and modified the starting comments. Everything else still works fine. :)

VB Code:

'********************************************************
'* Simple application to determine what time an
'* application started, keep track of the current time,
'* and use those two pieces of info to determine how
'* long the application has been running.
'*
'* Primary purpose for developing this application was to
'* have a tool to keep track of how long I've been coding
'* an application for billing purposes.
'********************************************************
 
Option Explicit
Dim showTime As Boolean
Dim startHour As String
Dim startMinute As String
Dim startSecond As String
Dim startTotal As Long
Dim currentHour As String
Dim currentMinute As String
Dim currentSecond As String
Dim currentTotal As Long
Dim elapsedHour As Long
Dim elapsedMinute As Long
Dim elapsedSecond As Long
Dim elapsedTotal As Long
Dim startAmPm As String
Dim currentAmPm As String
Dim ampmFlag As Boolean
 
Private Sub cmdUpdateRunTime_Click()
Dim length As Long
    
    currentAmPm = Mid(Time, Len(Time) - 1, 2)
 
    'Set flag
    If (startAmPm = "AM" And currentAmPm = "AM") Or (startAmPm = "PM" And currentAmPm = "PM") Then
        ampmFlag = False
    Else
        ampmFlag = True
    End If
 
    length = HowLong(startHour, startMinute, startSecond)
    lblElapsedHours.Caption = elapsedHour
    lblElapsedMinutes.Caption = elapsedMinute
    lblElapsedSeconds.Caption = elapsedSecond
End Sub
 
Private Sub Form_Load()
 
    lblStartTime.Caption = Time
    startSecond = Mid$(lblStartTime.Caption, Len(lblStartTime.Caption) - 4, 2)
    startMinute = Mid$(lblStartTime.Caption, Len(lblStartTime.Caption) - 7, 2)
    If Len(lblStartTime.Caption) > 10 Then
        startHour = Mid$(lblStartTime.Caption, Len(lblStartTime.Caption) - 10, 2)
    Else
        startHour = Mid$(lblStartTime.Caption, Len(lblStartTime.Caption) - 9, 1)
    End If
    
    'Because of the way elapsed time is calculated, must keep
    'track of AM/PM portion of Start time for comparison when
    'elapsed time is eventually calculated
    startAmPm = Mid$(lblStartTime.Caption, Len(lblStartTime.Caption) - 1, 2)
    Me.Show
    DisplayTime
    
End Sub
 
Public Function HowLong(ByVal startHour As String, ByVal startMinute As String, ByVal startSecond As String) As Long
 
currentSecond = Mid$(Time, Len(Time) - 4, 2)
currentMinute = Mid$(Time, Len(Time) - 7, 2)
If Len(Time) > 10 Then
    currentHour = Mid$(Time, Len(Time) - 10, 2)
Else
    currentHour = Mid$(Time, Len(Time) - 9, 1)
End If
 
If ampmFlag = True And currentHour <> 12 Then
    currentHour = currentHour + 12
End If
    
startTotal = (startHour * 3600) + (startMinute * 60) + startSecond
currentTotal = (currentHour * 3600) + (currentMinute * 60) + currentSecond
elapsedTotal = currentTotal - startTotal
 
'Application is active less than 1 minute
If elapsedTotal < 60 Then
    elapsedHour = 0
    elapsedMinute = 0
    elapsedSecond = elapsedTotal
End If
 
'Application is active for more than 1 minute
'but less than 1 hour
If elapsedTotal >= 60 And elapsedTotal < 3600 Then
    elapsedHour = 0
    elapsedSecond = elapsedTotal Mod 60
    elapsedMinute = (elapsedTotal - elapsedSecond) / 60
End If
 
'Application is active for 1 hour or more
If elapsedTotal >= 3600 Then
    elapsedHour = (elapsedTotal - (elapsedTotal Mod 3600)) / 3600
    elapsedSecond = (elapsedTotal - (elapsedHour * 3600)) Mod 60
    elapsedMinute = (elapsedTotal - (elapsedHour * 3600) - elapsedSecond) / 60
End If
 
End Function
 
Private Sub DisplayTime()
Do While showTime = False
    lblCurrentTime = Time
    DoEvents
Loop
    
End Sub
 
Private Sub Form_Unload(Cancel As Integer)
    showTime = True
End Sub