Hi Andreas,
See this thread:
https://groups.google.com/forum/?hl=en#!searchin/tiddlywiki/datetime/tiddlywiki/Ez2OwDXBwk8/t0ZKXYjmKJ4J
which refers to Stephan's dateTimeMacro here:
http://tiddlystuff.tiddlyspot.com/
Works really well for me!
cmari
On Monday, November 24, 2014 8:46:05 AM UTC-8, An
Hi cmari,
the dateTime module could be what I was searching for - thanks for this.
The usage is described like this:
The variable "tag" hold the current date.
<$set name="tag" value=<>>
One question I still have:
How do I get the resulting date from the variable "tag" into my field
t_duedate?
(
Hi Andreas,
> I have a field in a tiddler which holds a date (t_duedate: 2014-11-27).
> What I now want to do is to add seven days to this date by simply pressing
> a button.
>
> How can I add a value to a field?
> Is there a solution for adding days?
>
I think, eventually, this requires two t
Am Montag, 24. November 2014 18:07:38 UTC+1 schrieb Andreas:
>
> One question I still have:
> How do I get the resulting date from the variable "tag" into my field
> t_duedate?
> (Sorry if this question is to stupid...)
>
There is no automatic way to do that. You need to either use a button
an
Or you can write a widget that updates the tiddler on every refresh Anyway
he was asking about a button so the action widget should fit his use case.
Sadly the set field widget is only available in TW5.1.5 prerelease
--
You received this message because you are subscribed to the Google Gro
I'm sure others could do this far more efficiently, but in case it helps,
here's a minimalist version of what I cobbled together using both the
dateTime macro and Matabele's and widgets
(http://gwiz.tiddlyspot.com/#Widgets%20for%20Buttons:[[Widgets%20for%20Buttons]]).
In order to make this
Hi Tobias
>- a core awareness of field-types that can be defined somewhere
>
> Fields already have a type - look at the tiddler object definition in
boot.js.
But in practice I think that was a poor decision, and it makes more sense
for all fields to be strings and to be parsed to the require
Hi Andreas,
> But in practice I think that was a poor decision, and it makes more sense
> for all fields to be strings and to be parsed to the required data type as
> needed. Otherwise there are problems when different plugins want to
> specify a different type for the same field.
>
Actuall
>
> Hi Andreas,
Err, the last one was addressing Jeremy. ^^
--
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
9 matches
Mail list logo
