Hi
Could someone please help me with the following problem?
I would like to prepped the text field of *TiddlerX* to the text field of
*<>*. This happens programmatically from within another (a third)
tiddler.
Please notice that the tiddler title *<>* is temporarily created
and deleted on-dema
> <$tiddler tiddler=<>>
> <$button>
> COPY
> <$action-setfield $tiddler=<> $field="text" $value={{!!refs}}/>
>
>
>
It works. Thanks a lot, Jed.
Meanwhile I encountered another issue. I'm not sure if I have to open
another post. Anyway, I just go ahead and ask here first.
I would like to pre
The link was somehow broken at least for me. It's working now.
It's definitely nice and helpful to see new use cases. Your implementation
is neat as it is. Not cluttered. For creating new group/course/student, you
might be interested in wrapping your code inside a tiddler. You can find a
basic
Hi Gordon,
I tried to have a look, but this is where I ended up:
Best,
Mehdi
--
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...@googlegroup
Hi
I need to copy the *text field* of a tiddler into a specific field of
another tiddler. The tiddler titles are not known beforehand, because they
are temporarily created and deleted on-demand with almost arbitrary
(time-stamped) titles. So their names are passed through variables through
Set
> P.S. For complex regular expressions that include square brackets etc.,
> use can always use the set widget to prepare the expression (explained
> at tiddlywiki.com).
>
I'll remember it. Thanks.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" g
> ...
> From inside a widget tree you can access the dom elements but otherwise it
> is only possible by e.g. adding a unique class attribute to the button or
> similar.
> ...
> Macros are always called when the wiki changed and the parent widgets
> refresh their children. This may happen on e
Hi Felix,
...
> Maybe it is not suited for your case but I was refering to the "Accordion
> or Slider" in tiddlywiki.com/#RevealWidget which uses no match to create
> an if-else.
>
> ...
> Yes it does, but it doesn't wrap its children into a p element like the
> reveal widget. I mean, you are
to distinguish states in
> the reveal widget, better use type="nomatch" for the opposite. Also a
> reveal widget creates a dom element, maybe better to use the list element
> for if-else analogy in this case (yes, even though it is called list widget
> it can be used for if else
Hi everyone.
I would like to share with you some code. It consists of three interrelated
Tiddlers that:
1. Store and display Geo-position.
2. Prompt the user for changes, if she/he decides to.
3. Fill some default value upon a change request, if the value is empty.
Now this is simple t
his is my first post here. I have to thank everyone who has
>>> generously invested in this project. I very much appreciate it.
>>>
>>> Pleasure, glad you're enjoying TiddlyWiki, and thank you for taking the
>>> time to give feedback.
>>>
>>> >
Hi Alberto,
Thank you for pointing this out. That was a typo in the post. The issue,
nevertheless, stands. I already edited my post.
Mehdi
On Friday, March 20, 2015 at 12:05:38 PM UTC+1, Alberto Molina wrote:
>
> Hi,
>
> Your code lacks the opening < in the first line:
>
> <$scrollable etc.
Hi guys,
This is my first post here. I have to thank everyone who has generously
invested in this project. I very much appreciate it.
After upgrading from 5.0.13-beta to 5.1.7 I have been having problems with
making the ScrollableWidget work. Here is how I would reproduce the issue:
1) go to
13 matches
Mail list logo
