I'm trying to convert the Cocoa timestamps to human-readable dates with time. For context, these numbers are coming from the history.db file within ~/Library/ for Safari. I can convert individual numbers with the awesome tool at epochconverter.com, but they do not offer a batch converter for Cocoa.
As an example, 638490901.575263 should convert to Friday, March 26, 2021 3:35:01 PM GMT-07:00. In Excel, I'm using:
=("cell reference"/86400000) + DATE(2001,1,1), but getting 1/8/01 9:21 AM. Looks like I need to add time for the Cocoa Epoch delta, but unsure how to do that.
Thanks for any help!
You have too many 0 in the formula, the number is the number of seconds since the start of 1/1/2001. There are 86400 seconds in a day. Then add the start date so we get the correct number of dates from 12/31/1899 which is what Excel uses. Then we need to subtract 7 hours to get the correct time zone difference.
=(A1/86400) + DATE(2001,1,1) - TIME(7,0,0)
How do I convert days back into hours when using a list?
I'm calculating a list of video lengths. Because the list is so long, it eventually adds up into days (time exceeding 24 hours). What I would like it to do is rather than push the overflow (of anything over 24 hours) into days, is just have it included in hours.
For example, rather than 27 hours being shown as "1:03:00" (1 day, 3 hours, 0 minutes) I want it to appear as "27:00". You can change the time format under the Format tab, however that doesn't actually change anything. All it does is not preview that time period, it doesn't roll it into the next slot. So changing the format from Days:Hours:Minutes to Hours:Minutes changes "1:03:00" to "3:00".
I didn't list code because I'm just using "=Sum(A:A)". Is there a different format I need to select or do I need to convert it manually? How would I go about doing that when I'm dealing with time values and not mathematical values like whole numbers and decimals?
The time values in the column are listed as 12:9:49 AM for a video that's 9:49 long, if that helps. No idea why it has to add 12 in front but that's the only way I could get it to read as a numerical value rather than a text string ('9:49).
Found it!
What I was looking for was an option called "Elapsed hours" under the Format tab. Sometimes it's there, sometimes it's not.
Another method is clicking custom format (rather than date/time) and inputting [hh]:mm:ss. The square brackets mean all hours accumulated will stay there. It won't roll over back to 0 and push the excess into the days slot. So 27 hours appears as 27 hours rather than 3 hours (with the 24 being counted as 1 day).
I'm trying to run a batch script using Robocopy but when I try to put in MinAge days of 10 years ago (for example 3653 days) it doesn't like it and I'm getting an 'Invalid switch' error. If I put in the date 20110101 it works perfectly. Just trying to figure out the maximum number of days I can use for the MinAge parameter.
I've looked on Microsoft support, here an elsewhere and I don't see this being addressed. Thank you in advance for your time and answers.
1899 is the maximum days you can put in for MinAge.
This question already has answers here:
How to convert YYYYMMDDHHMMSS to a date readable by `date`
(6 answers)
Closed 6 years ago.
I have a number, lets say it is 20160823130001 which stands for 2016 august 23rd 1300 hrs 1 second. But sometimes the date stamp will be 20160823125959.
From that number I need to add or subtract 10 mins and I cannot figure out how to do it in bash. This would be easy if it was 1330 hrs but since it is 1300 it needs to end up as 1240 and 1310. I could do some strange checks to subtract or add such as if 125959 then add 51 elseif 130000 add 10 but this seems clunky. How can I make this happen without strange checks using bash?
Thank you for any pointers.
Convert the string into a date first and then do the manipulation. Links on how to do that are in the comments section
What's a good web-based UI for capturing a time duration from the user.
Lets say that we want to capture a time duration in minutes.
But would like to present it such that the user can enter in hours and\or minutes.
Just use 2 textboxes for hrs\min?
Or a single textbox and let them type in "1hr 31min" or "91 min" ?
Or is there something better?
If you have two text boxes labelled hours and minutes then you need to deal with case where the user types into both of them.
3 into h and 35 into m => pretty clear. 3 hours 35 mins
nothing into h and 95 into m => 1 hour 35 mins (probably update the display to show that)
but what about
2 into h and then 95 into m => does that mean 3 h 35 or 1 hour 35
I've used too many annoying UIs where changing a field zaps other entries to be confident that I can devise an unastonishing set of behaviours.
Hence I would go for a single box into which we can type 3h or 1h 35m or 95m and have a separate read-only display of the interpretation.
There seems to be an opportunity for a nice widget to allow a mouse driven entry, in the same way as a calendar widget allows date entry. A little clock with dragable hands?
Thanks for all the feedback.
What I finally ended up doing was, having a single textbox that shows the time duration in the format "xxhrs yymin"
The user can edit it and when focus moves away from the textbox, it recalculates the duration and reformats the text into the canonical form.
The parser to interpret the text entered is fairly liberal.
It's a set of regular expressions to match any number followed by 'h' or 'm' or 'd' to represent hours, minutes and days.
If it doesn't find any 'unit' with a number in front of it, it assumes you have typed in a pure number as minutes and will interpret it as such.
So if the user types:
"1.5h", it will reformat to "1hr 30min" upon leaving the textbox.
"90 min" will also be reformatted as "1hr 30min"
The parser only looks at the first character following the number, which means you can enter "1 day, 7 hours and 19 minutes" and it will recognize it correctly.
Of course, it would also recognize "2 holes and 19 mice" as "2hrs and 19min".
I think I can live with that.
Just let them type the numbers only in a pre defined time format.
Place 2 textboxes for hour and minute without the hr or min.
Also you have to define whether it is a 24 hour system or 12 hour.
Well, separate hours and minutes fields is the safest but slower to use than a single field. You can default the hours to 0 if you don’t expect many durations over 1 hour.
Maybe it depends on your population, but I expect users will be able to handle hours and minutes in the same text box if you provide a prompt, such as “Time duration (hrs:min):”
With that prompt, accept any initial unbroken string of numbers as the hours and any subsequent unbroken string of numbers as minutes, so that all of the following input are treated as equivalent.
2:30
02:30
02:30:05
2.30 (or maybe not: while great for keypad entry, but you may want to make an exception for the decimal point to allow the user to enter fractional hours, such as 2.75 for 2 hrs 45 min.)
2 30
2 hrs 30 min
2 hours, 30 minutes
2jaQp 30!!!!
I see no reason to require that the minutes be less than 60. The user should also be able to express the time as:
:150
When the focus leaves the field, auto-correct whatever the users enter to the specified (hrs:min) format to feedback the interpretation you made.
If all you need for your purpose is a rough approximation of time (or your users are only estimating anyway), then consider option buttons or a dropdown list with ranges of duration (e.g., 0 to 5 minutes, 5 to 15 minutes, 15 min to 1 hour, Over an hour.). Or if there are definite bounds on the durations and the intervals are functionally linear, you can use a labeled slider.
Whatever input format or control you use, it should be compatible with the source of information. Where do users get this duration? What units, format, intervals, and degree of precision are used there? How do users think and talk about the time among themselves?
I think there should be no client side correction for the minutes greater than 60 as somebody suggested. It would only be confusing and generate unnecessary problems.
User entered the data so he should understand what he typed and there is no need to correct him.
I would leave these fields as filled by user. On the server side I would just calculate total minutes as:
$total_minutes = 60 * $_POST['hours'] + $_POST['minutes'];
I was just thinking about this and realized one familiar UI for this sort of thing is a microwave oven. For iPhone-like uses, a keypad may be better than the rolling scroller thing I often see.
In my case I think I'm going to go with a text field for "number" and a selectbox for "unit" (years, months, weeks, days, hours).
Sliders (jqueryui, html5) could be an option too, depending on what kind of range you're talking about.