Hi Måns, I was not totally clear in my last post, so I edited it:
*If I use my own "start" and "end" fields instead of "created" and "modified" with "YYYYMMDDHHMMSSmmm" I get the same errors.* Normally I use "YYYYMMDD" which works (so I did not have any errors). Strange that 2 of your tiddlers were accepted. Do they have special date/time strings in comparison with the others? Cheers, Ton On Tuesday, May 12, 2015 at 10:15:41 PM UTC+2, Måns wrote: > > @Ton > > Have you tried to use this format: YYYY-MM-DD for your own start end > fields? > It seems to work ok for me. > > Still I would love to be able to make it show the span of time from a > tiddler was created untill it was last modified > > Maybe a macro could do the conversion from YYYYMMDDHHMMSSmmm to YYYY-MM-DD > and input the result as start end parameters in the timeline macro call?? > > Cheers Måns Mårtensson > > Den tirsdag den 12. maj 2015 kl. 21.19.49 UTC+2 skrev Ton Gerner: >> >> Hi kixam & Måns, >> >> The format "YYYYMMDD" works but "YYYYMMDDHHMMSSmmm" (the format used by >> "created" and "modified") does not work. >> Since "created" and "modified" are standard fields of a tiddler, I >> thought it should work. >> >> Striking is: there are only errors for startDate and *not* for endDate in >> Måns image of the error messages (except when end date is before start >> date). Or maybe when encountering an error in startDate is does not check >> endDate anymore? >> >> If I use my own "start" and "end" fields instead of "created" and >> "modified" I get the same errors. So I think it has nothing to do with the >> "created" and "modified" fields. >> >> Maybe a mismatch between the time-date formats of TW5 and moments.js? >> >> Cheers, >> >> Ton >> >> >> On Tuesday, May 12, 2015 at 6:17:03 PM UTC+2, kixam wrote: >>> >>> Hi Måns, >>> >>> On Tuesday, May 12, 2015 at 7:25:20 AM UTC+2, Måns wrote: >>>> >>>> This: <$visjstimeline filter="[tag[note]]" startDateField="created" >>>> endDateField="modified" format="YYYYMMDDHHMMSSmmm"/> >>>> sort of works - There are however some errors even if some tiddlers are >>>> rendered as elements on the timeline. >>>> >>>> Can't I use created date as a startDateField and modified as >>>> endDateField to capture when a tiddler (tagged with "note") was created >>>> and >>>> modified? >>>> Is the problem that some tiddlers that were created may not have a >>>> modified date - because they haven't been modified yet? >>>> >>>> >>> I found that the timeline widget is very sensitive regarding start and >>> end dates. Like you, I had problems when I tried to create a timeline using >>> a end date field that did not exist in all filtered tiddlers. My solution >>> was to create end fields for those tiddlers, and duplicate the start field >>> value into the end field. It is not enough that both start and end fields >>> exist for all filtered tiddlers, they must also contain a valid date at the >>> specified format, and the end date must be the same or later than the start >>> date, otherwise you get error messages. >>> >>> I do not know if the "modified" field is created with the tiddler, or if >>> it contains the creation date initially. >>> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/5bb129f3-bd23-4ead-8fa5-408e3ec7d629%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
