Hi Stephan > > Yes! I tend to be a bit of a nuisance from time to time. >
Not at all, this dialogue is very helpful for others reading along, and you're continually bringing up issues and perspectives that I need to understand. And of course your willingness to invest time and energy in contributing to the project is much appreciated. I just get worried that you'll get dispirited by the process. > > The only problem is the fact, that the HTML could be rerendered while the > handler is running because I can't find my "other" radio buttons then.But > the underlying problem I have is, and you haven't offered a solution yet: > How can I find, when <$tagselect> is parsed all the other <$tagselects> > which are already parsed or might be parsed? I think that's not possible. > But maybe there is a way for the widgets eventhandler to find in the tree > of widget objects, all those residing in the same tiddler, being a > tagselect object and sharing the same group name. If that's possible, I'd > love to use that and not rely on the DOM to get my (static!) tag values. > > The expected approach is that a <$tagselect> instance would never need to locate other instances in the widget tree or the DOM, instead it would update the tiddler store in response to the user action, and that that update would cause a refresh cycle which causes the other widgets to adjust themselves. One approach would be for your 'group' attribute to identify a tiddler that is used to store the state of the tagselect group. (It could be used with the <<qualify>> macro when needed). Best wishes Jeremy -- Jeremy Ruston mailto:[email protected] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/groups/opt_out.
