Hi Kolya, One reason why I didn't want to hide buttons was that I didn't want to have them jump around, i.e. you click one button at one place and then see that very button jump 100 pixels to the left ...obviously not cool. So greying-out and deactivating seems the way to go.
So, this seems a two step process. Currently I am not even restricting the initial interface to the configuration... which is independent from greying out filter buttons for which there were no results. The problem is that - codewise - I have been creating the interface before knowing what would really end up being relevant... so that's obvioulsy not good (enough) and needs change. I had implemented it that way, because I was too lazy to think of ways to refactor the code which retrieves the matching tiddlers such that I woulnd't have to duplicate it in the section when the interface initially displays. I had done so, because I wanted to use the same loops to actually draw the interface and create the result set. But now I am rather thinking that the plugin needs a kind of "redraw filters" function, running at the end of each action. So, I should probably grab a pen and paper and make a lovely flowchart, containing... 1) get initial result set (only at the beginning) 2) setup filter buttons (only at the beginning) 3) get result set (whenever redrawn, depending on active filter buttons) 4) (de)activate filter buttons (whenever redrawn, depending on the current result set) As for the timeframe parameter, that sounds like a reasonable addition. So, it's in the todos. However, just as as 4) would not, deactivating the buttons for future months would not be top priority right now. Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
