Jim, Un-verified something like this
<$wikify name=new-date text="<View$ field="in-date" format="date" template= "YYYY0MM0DDhh0mm0ss0XXX"/> > <$list filter="[sameday:created<new-date>]"> </$list> </$wikify>> and if it gives you a different result template="[UTC]YYYY0MM0DDhh0mm0ss0XXX" In your case "in-date" may be "created" Using the aformentioned rpn or formulas plugin you could add or subtract the time zone. Regards Tony On Saturday, July 21, 2018 at 3:46:47 PM UTC+10, Jim Farrand wrote: > > > > On Friday, 20 July 2018 21:21:16 UTC-7, TonyM wrote: >> >> Jim, >> >> The other way around I would think, all dates utc and when you view them >> the local timezone offset is applied. Including daylight. >> >> This is nessasary for time zone shared wikis. I can say this since I live >> at +10 >> > > I agree, I think we are both suggesting the same thing. As far as I can > tell, the dates are already stored in UTC. It's 20180720 22:29 here in > PDT, and I just created a tiddler, and lookted at the timestamp in the file > on disk is 201807210529 which is the time in UTC. sameday needs to make > the corresponding conversion to UTC so that it's comparing like to like > (and as you say, display functions needs to convert either to local time, > or to an explicit timezone if thay are given one). > > Reading issue 2061, it seems that at least some people think that the > timezone should also be stored on disk. I disagree. But it's also > irrelevant because even if that change were to be made, we would still need > to fix sameday etc. Storing the timezone on disk is IMHO the wrong thing > to do, but I don't see how it fixes the problem by itself, and it seems > that no-one can be bothered to do it anyway. So we might as well just fix > sameday etc, which is easier, cleaner, and actually solves the problem. > > I guess I'm hoping that a dev will pipe up and either say "go ahead and > make this change, we'll probably accept the patch", OR... point out the > missing line of reasoning that explains why it isn't the right solution. > > >> The view widget has the template parameter with the utc option and you >> can format the same full date code to the micro second. Perhaps using the >> view widget with or without utc before you feed it into your sameday filter >> in a variable, will solve this issue? >> > > I'm not sure how that would work. What does the syntax look like to run a > filter on the result of the view widget? > > Regards, > Jim > > To me date field values are barly readable as they are so why not maintain >> them in utc and always filter and display them as local time. >> >> Evans formula plugin and the rpn maths plugins provide a little more in >> the date, Maths and the pickaday plugin is good for date selection with a >> popup calendar. >> >> Regards >> Tony >> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0784ce68-4635-44df-a044-3d85f4e49ac0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
