View Single Post
Old 02-28-2020, 08:19 AM   #3
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,691
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
As for the second suggestion, it's not a question of how easily it could be implemented. It's a question of how best to explain to users with extensive Saved Search libraries that we broke them. Introducing new fields would be next to impossible to do while maintaining backward compatibility with existing SS libraries. Meaning we run the risk of potentially damaging existing libraries (at the extreme), or at the very least, tell users that they need to manually massage their existing preference files to work with the new format that will be required to store more fields per saved-search entry.

I'm sure that some ways around the backward compatibility issue could be found, but the point is that it's a huge factor when considering how to implement such a feature expansion.

Last edited by DiapDealer; 02-28-2020 at 08:59 AM.
DiapDealer is online now   Reply With Quote