Hi Jeremy, > The order does matter for filters that work as "selectors" rather than > strict "filters". For example, the "indexes" operator selects all the data > indices present in the tiddlers whose titles are in the current list. >
In ... http://tiddlywiki.com/#FilterOperator%3A%20indexes What exactly is *{$:/palette}*... [{$:/palette}indexes[]sort[title]] interpreted as? ...being a text-reference. I presume it is translated as: take whatever is defined in *{$:/palette}* as a text-reference to a data-tiddler. What would happen with a construct like this: [[tag[foo]indexes[]sort[title]] ...assuming there were multiple data tiddlers tagged *foo*? Also, can any field of a tiddler be used as a DataField or does it always have to be the *text* field? As asked / indicated here <https://groups.google.com/d/msg/tiddlywiki/Yv7kdCbWtNo/crA7E7xWHSsJ>, I think it can prove beneficial to store related data entries at the exact tiddler to which they relate, yet not in its text-field. As for deleting indexes from a DataTiddler, here is one way to do it... Saving And Loading A History Snapshot @ tb5 <http://tb5.tiddlyspot.com/#Saving%20And%20Loading%20A%20History%20Snapshot> Look at *\define deleteSnapshot()* and notice how the index is *set* on button click, however with no *setTo* value being specified. This results in setting an undefined value, ergo deleting the index from the data. Best wishes, Tobias. -- 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.
