Welcome, Guest. Please Login
IMPORTANT MESSAGE! This forum has now been replaced by a new forum at http://forum.eastgate.com and no further posting or member registration is allowed. The forum is still accessible via read-only access for reference purposes. If you wish to discuss content here, please use the new forum. N.B. - posting in the new forum requires a fresh registration in the new forum (sorry - member data can't be ported).
Pages: 1
Send Topic Print
aTbRef - corrections re Time & seconds (Read 2465 times)
Mark Anderson
YaBB Administrator

User - not staff!

Posts: 5689
Southsea, UK
aTbRef - corrections re Time & seconds
Jan 9th, 2013, 6:02am
At some undocumented point (v5.0+?), TB shifted to coercing the seconds element to zero, i.e. '00'. This means that manually input seconds in date(string) inputs are ignored and that designators like 'today' set a date/time rounds to 00 seconds.

In TBX source code, some date date created in older TB versions, such as $Created, may still be stored with a non-zero seconds element. Whatever, within the current app, all dates are treated (and string-exported) as if seconds were always zero. Testing in v5.11.2, all Date data is created  with '00' seconds, even for designators like "now", i.e. current date/time.

Previously, some TB methods set actual seconds but as key attributes don't show seconds in date/times without altering the user's settings, this led to some confusion when comparing dates.

Anyway, aTbRef should reflect the status quo a bit better now. For new users the simple version is TB doesn't use time below minute level. Seconds aren't shown in date/times in the UI, are ignored in inputs, and always export (if needed by format) as 00.
Back to top
« Last Edit: Jan 09th, 2013, 6:11am by Mark Anderson »  

Mark Anderson
TB user and Wiki Gardener
aTbRef v6
(TB consulting - email me)
WWW shoantel   IP Logged
Pages: 1
Send Topic Print