The $action name definitely needs changing, it is a vestige of its original design, until I made the widget more generic keep forgetting to write it down though.
Okay, just tried something that changes the issue a bit. I just set a delay between the add tiddler and setting the field. It worked as expected. Is adding a tiddler async? I briefly thought about that originally but didn't test until now. On Thursday, April 9, 2015 at 1:29:23 PM UTC-5, Jeremy Ruston wrote: > > Hi Roma > > > I would appreciate any time someone took to look at this mess. > > Very happy to help if I can. Please could you list the exact actions that > are needed to reproduce the problem? Your code looks fine; I think this may > be a problem with the select widget. > > One minor point is that I'd advise against calling the widget "action". > All the widgets live in a global namespace, and "action" is quite a generic > word. Given that it's gsd specific, perhaps call it "gsd-action"? > > Best wishes > > Jeremy. > > > On Wed, Apr 8, 2015 at 3:42 AM, Roma Hicks <[email protected] > <javascript:>> wrote: > >> Hi. >> >> What I am attempting to do is set a field after the user has entered the >> title of a tiddler that was just created. >> >> 1. User presses modified $button widget. >> 2. When prompted, enters new tiddler's title. >> 3. Tiddler is created and stored. >> 4. The tiddler that holds the widget has it's value set to the new >> tiddler's title. >> 5. Related widgets update and refresh. (This is the breakdown) >> >> The block that adds this behaviour is a very simple setText call. >> >> https://github.com/roma0104/gsd5/blob/issue58/plugins/gsd5/core/modules/widgets/action.js#L94 >> >> This code mechanically sets everything correctly, it is just the redraw >> of the $select widget that does not happen. Actually, it does redraw but >> does not set the matching value for the field. If you close/edit the >> tiddler it redraws it shows the correct value. >> >> This seems to be a problem with widget outside the normal "content >> space". As the same widgets placed in the body of the tiddler behave >> correctly. You can play with an example here; the example is a partial >> implementation of creating a new Project. >> http://gsd5-playground.tiddlyspot.com/#In%20Body%20Example >> >> I would appreciate any time someone took to look at this mess. >> Debug help or tips. >> >> >> >> >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/tiddlywikidev. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywikidev/1fb23f05-fda7-4845-8acc-f72cd36f2ac3%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywikidev/1fb23f05-fda7-4845-8acc-f72cd36f2ac3%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Jeremy Ruston > mailto:[email protected] <javascript:> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/8e8d9254-251f-4f51-8fc9-3119d4156029%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
