On Friday, May 24, 2013 12:26:15 AM UTC+2, cflow wrote: > > Looks like you added a condition to clarify the values, but I am not sure > how that improves things exactly.
Was the intention to address the TTReportView error (where the error > actually displays in the tiddler when a field type has not been described > correctly or is not valid) > IMO plugins should not blow up, if any parameter is missing. They should do something usefull, even if information is missing. > or the secondary error where all works as expected except on the task, > when you change the value on the field on the task the displayed value on > the field does not change? > > > Any new task tiddler does get created correctly, but does not have the > fields in the HTML for the tiddler until you change them (for the first > time) to have a value. I was wondering if setting those on creation to a > valid base value would eliminate the TTReportView error. > > If anyone can suggest a way to view what javascript gets called when > changing a field on a task I would probably be able to work out the > secondary issue. > ValueSwitcherPlugin should be the plugin, that adjusts the field values. You can try to adjust the MainMenu tiddler to initialize new tasks. This should tell you how: http://tiddlywiki.org/#newTiddler But imo it won't solve the problem, if you need new custom fields, because you'll need a newXYZ button for every combination. -m -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
