Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[zybex]

Hi @Matt, Happy New Year!

I think it would be nice to support Epoch timestamps (seconds since 1970) without having to do math:

- Add a mode to Now():
   mode 0 = current format, default
   mode 1 = epoch timestamp (for current timezone/location)
   mode 2 = epoch timestamp in milliseconds (for current timezone/location)

- Small change to FormatDate() and CompareDates() so that any DateValue larger than 86400 is interpreted as an Epoch timestamp. 86400 is reasonable as it corresponds to about 236 years in the normal MC date format, but just one day in epoch calendar.

[Matt]

Sure thing.

Next build:
NEW: Added a mode to the Now expression to return the seconds since 1970 instead of days since 1900.

[zybex]

Thanks!
Will FormatDate() also work with epoch values?

[Matt]

Not yet. It seems like a parameter might be better than trying to figure it out automatically?

[zybex]

Your call, but I think inference is fine as Epoch values are so high that they don't really make any sense as a standard MC timestamp.
A mode makes sense if more formats are to be added, like:
mode 0 = MC time
mode 1 = epoch time
mode 2 = epoch time with milliseconds

[SkGe]

Hey Matt any chance for an option in how to show the date format? Instead to have the default d/M/yyyy hh:mm:ss pm/am? Something like excel does. You can select different way to show the date. Right now to achive this is to use different expression fields.

[zybex]

You can use FormatDate() to display a date in any format you want. The default display format is defined by your Windows Regional settings.

[Matt]

Your call, but I think inference is fine as Epoch values are so high that they don't really make any sense as a standard MC timestamp.
A mode makes sense if more formats are to be added, like:
mode 0 = MC time
mode 1 = epoch time
mode 2 = epoch time with milliseconds

Next build also:
Changed: Made FormatDate and CompareDates interpret any number over 86400 as a time value instead of days since 1900.

Thanks.

[SkGe]

@zybex.
I know that formatdate() you can set the time whatever you want. I'm talking when using a custom date field it uses the default d/M/yyyy hh:mm:ss pm/am. That one you can't change or can be change in windows? I can try to see if the way my regional settings are in windows.

[zybex]

Yes, you can change the default format in Windows settings - it's a bit hidden though.

For any standard Date field like [Date], [Date Imported], [Date Modified], etc, you can always get the underlying numeric/raw value and then format it with FormatDate():

formatDate([Date Imported, 0], dd-MM-yyyy HH:mm)

[SkGe]

I really don't want to go windows way and modify date and time just to be shown in MC, It can mess with other settings in my windows and I don't want it.
Maybe a way to be able to do in MC as an option as a feature request.
Only Matt and team can say if they think or not about it (finger cross )

[HPBEME]

Unfortunately this change messed up an expression I have been using in the status bar and the player bar.  If([Last Played,0], CompareDates([Last Played,0], Now()) ago, Never) 

I copied it from a post by lepa I think, but I can't remember for sure. It used to return time elapsed since a track was last played and automagically appended the appropriate units, whether that was minutes, hours, days, or years.  Now it only shows 0.00.

I have been experimenting using zybex's Zelda expression evaluator, but I unable to make it to show what it used to.  I'm not particularly skilled with expressions, so if somebody could a help me figure it out, I would greatly appreciate it.

[zybex]

Yes, looks like CompareDates() is now broken for normal date values. Don't change your expression, this needs to be fixed on a next build.

@Matt, looks like it's working for Epoch values but not for values < 86400.

[Matt]

Thanks. CompareDates will be sorted next build.