Yeah, if this were working, one could implement "sticky collections" as a background task:
- get active sources
- assure sticky collection is one of them
- set active source that include the sticky collection, if not already set...
Although, as long as it returns the correct source for most situations, it may not be too bad...
Probably not a good solution for sticky privacy collections, since there would be a moment when it becomes unstuck.
Anyway, just brainstorming...
I was interested in something related: The ability to undo and redo source and filter selections. A background task would capture the current state of sources and filters every second, for use by the Undo and Redo commands. My unfinished prototype works well, except for the fact that getActiveSources() doesn't capture all the sources.
So does this mean the prototype will never make it to production? Or, it will be produced, but with limitations...
I'm not planning on doing any more work until if/when the bug and limitation are fixed. If get/setActiveSources can't replicate user actions (e.g. knowing that the current source is set to the previous import), then it's much less useful to me.