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) 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. On Thursday, May 23, 2013 11:04:52 PM UTC+10, PMario wrote: > > Try this one: https://gist.github.com/pmario/5635825. It should fix the > undefined field problem. ... but ... I'm not sure, if the filtering is > still done right. You'll need to test some combinations. > > NewTasks, that contain undefined fields will show up in any list as far as > I did test it. I thought this behaviour is OK, since all fields should be > defined, or the tiddler should not exist. > > @PhilHawksworth If you are interested in the fix I cold create a pull > request somewhere otherwise the plugin may live as a gist for the moment :) > > have fun! > mario > -- 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.
