Hi Neil Jeremy: am I interpreting correctly that your bullet list indicates the > order in which the features are processed, but last first in your list? > Thus, the transclusion is only processed after the non-widget <<>> style > macro invocation? >
No, not at all. The layers I was describing are conceptual groupings of features that can be progressively taught to users. > My problem is that I am trying to use a macro to generate an > <$action-setfield> widget, where the $value parameter is calculated by my > macro. If I put my macro inside a <$button> widget, the action doesn't get > activated by the button, which makes sense if widgets are processed before > macros. The odd thing is that if I also ask the macro to generate the > <$button> widget, the action *does* get activated in the way I intended > when I click the button. Since I am trying to generate many $action > widgets inside the same $button, it would be much neater if the first > method worked, to avoid having to write out lots of repeated widget text or > pass dozens of parameters to the single macro. Is there a way round this? > The issue here is that action widgets need to be immediate children of the widget that triggers them. If you generate the action widgets within a macro then the macro will be wrapped around the action widget, meaning that the trigger widget won't see it. We have discussed lifting this restriction. it would be particularly useful to be able to generate action widgets with the list widget. Best wishes Jeremy > > Thanks, > > Neil. > -- Jeremy Ruston mailto:[email protected] -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
