Thanks BJ, your explanation that you linked to was very helpful. I am both
concerned with ease of coding (on my end) and response time (on the user
end).
Let me see if I understand this correctly: by invoking an action, a new
child is created, so the control gets passed to the new child
HI Pat,
when you are writing a widget which response to some event, it is possible
to cause other events. Action events (at present) are children - so the
control passes in the direction away from the root of the widget tree,
conversely messages travel in the other direction, toward the root,
Hi
For something I did recently, I used messages, which are cought and
processed by widgets surrounding the UI that implements the
functionality.
Andreas advice is good. TW allows you to add event properties via widget
attributes and then you can access them from within your handler code
Thank you Felix and Andreas. You've given me a lot to think about, and work
with.
On Saturday, March 7, 2015 at 4:02:45 PM UTC-5, Felix Küppers wrote:
Hi
For something I did recently, I used messages, which are cought and
processed by widgets surrounding the UI that implements the
Hi,
you almost got it: The action widget HAS to be present as a child
widget of your more complicated widget at parse time, which means, it
has to be in the wikitext.
Now you could create them on the fly in your widget, but that would be
complicated and since usually there is more than 1
