[DTownSMR]

As far as persisting the filters when editing setlists, that brings up a couple of issues that I would need feedback on:

1) The screen that is used for editing setlists is basically the same screen that is used for editing any group of songs. Would the filters be persisted for all group types or just setlists?
2) Should the filters be maintained and persisted separately for every group type? Furthermore, if you set filters for one setlist and then edit a different setlist, should those same filters be applied? Or do I have to persist filters per setlist as well, as that would significantly drive up the amount of data I have to store.  Or do I just reset the filters if a different setlist is edited?

In this case, I'm just talking about persisting them across screens in the app. Are you also wanting these persisted between loads of the application? With all of the different supported filters, I'm probably going to need to add a new database table to store everything.

As I stated, I only have one use case and that would lead me to answer that the filter is:

• a single object
  
• persisted everywhere the same
  
• no different per group type
  
• not tied to a setlist
  
• persisted across loads of the application
  

It would be nice for folks that use filters to chime in with their use cases. I think that would help a lot.

Some of what you're asking could be supported with the notion of named filters. The name could be a setlist or a group type and could auto-magically be applied upon name match. If no match found, use one named "default" or some such. If no one chimes in other use cases it might still be beneficial to add the name support to make future feature requests trivial.