Jeremy or Evan - any follow up on this? I keep hitting cases where it would be useful. I believe a solution would also function as a kind of array, which should appeal to coders coming here.
Tobias' workaround IS an optoin but it's a bit contrived to explicitly add and deduct stuff for each item. Just generally, I reason that the items have a natural position in the provided filter output that one probably could take advantage of - alternatively; I assume the list widget runs through that number of iterations so some kind of counter could maybe follow along for each iteration... <:-) Jeremy Ruston wrote: > > Hi Evan > > Jeremy, would it be possible to get an *unoptimized* version of the list > widget as a basis for customization? As it is, it looks like the > optimization adds a lot of code complexity and it's a little hard to know > what to strip out without a strong understanding of TW's codebase. > > > I'll try to do it if I have a chance. To be honest, it may be easier to go > the other way: to take a generic widget and gradually add the list > functionality in bits and pieces. > > -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/12ea46f5-ac47-426b-9be7-d14da7ab9a24%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
