Hi all,
The documentation for ActionWidgets on tiddlywiki.com describes the
<$button> widget as an example of a widget that can trigger an action
widget. Am I right in thinking that currently it is the *only* way to
trigger an action? I was hoping to be able to use a <$select> widget to
trig
Hi Neil
> The documentation for ActionWidgets on tiddlywiki.com describes the
<$button> widget as an example of a widget that can trigger an action
widget. Am I right in thinking that currently it is the only way to
trigger an action?
That's correct, only the button widget triggers action widget
Thanks Jeremy. I'll have a delve when I get a moment.
On Sunday, 4 January 2015 10:08:25 UTC, Jeremy Ruston wrote:
>
> Hi Neil
>
> > The documentation for ActionWidgets on tiddlywiki.com describes the
> <$button> widget as an example of a widget that can trigger an action
> widget. Am I right
> It would be fairly straightforward. In the handleChangeEvent handler of
> the select widget we need to call self.invokeActions(event).
> There are a few other widgets that should be enabled, too: link, checkbox,
> radio and maybe keyboard, edit-*, dropzone.
>
I often thought about this. It
Coming back to the original subject of this thread, after a fair bit of
poking around I managed to figure out how things work sufficiently to get
triggering from a select widget working. It was a bit more complicated
than just adding this.invokeActions(event) to handleChangeEvent because (I
ev
> the contents of the select widget are buried at the grandchild level
rather than being immediate children
Why is that happening? The action widgets are supposed to be the immediate
children of the triggering widget. There is a proposal to extend things so
that all descendent action widgets are
On Sunday, 11 January 2015 09:05:32 UTC, Jeremy Ruston wrote:
>
> > the contents of the select widget are buried at the grandchild level
> rather than being immediate children
>
> Why is that happening? The action widgets are supposed to be the immediate
> children of the triggering widget. Th
Hi Neil
I'll see if I can figure out how to do that. However, for my application,
> which is a bit more complicated than my demo tiddler, I think this might
> not be adequate. I might try to write a new bespoke select widget that
> also does what I am currently doing with a js macro and the acti
On Sunday, January 11, 2015 at 3:05:32 AM UTC-6, Jeremy Ruston wrote:
>
> > the contents of the select widget are buried at the grandchild level
> rather than being immediate children
>
> Why is that happening? The action widgets are supposed to be the immediate
> children of the triggering wi
Hi Codacoder
You’re correct about the extraneous paragraph tags but I don’t think it’s the
problem here: shortly after the message below we changed the core so that
action widgets do not have to be an immediate child of the triggering widget:
https://github.com/Jermolene/TiddlyWiki5/commit/f9c4
Well, it's hard to say unless Neil comes back to clarify. All we have is
his original statement:
> the contents of the select widget are buried at the grandchild level
rather than being immediate children
which led me down the path of P tags.
On Wednesday, June 29, 2016 at 2:21:31 AM UTC-5, J
11 matches
Mail list logo
