Quoting MrC <[EMAIL PROTECTED]>:
dean Wrote:
We should automatically trigger the rescan when the user makes a
change to a setting that requires it.
By "should", do you mean "currently are", or do you mean "to be
implemented"? Experience indicates the latter, or a bug.
some features to trigger one, like activating musicmagic, itunes,
moodlogic, or
changing the music folder. Its not hard to trigger a rescan in
reaction to the
pref change. The warning in text would be critical, so that users know
that IF
they change it they WILL cause a rescan. Some users will be upset anyway.
(just wait for the requests that all operations must have a
confirmation dialog
;)
That said, it would be even better to make all the options dynamic,
so rescanning can be a fond memory.
Agreed - that would be best. It seems like all these tags and metadata
should be scanned once, and carved-up as per user-settings on the fly.
some are easier than others. ideally, one scan would be great. but, how much
extra memory is then required to hold all the extra data 'just in case' a user
changes their prefs down the line. What about the users who just want to set
and forget without having to suffer the added resources to appease the
user who
wants to shift between grouped and multi-disks on a daily basis :)
There may be easy answers to this. I'm no db expert, so I can't say. I
tend to
just put up with however it works. Sometimes the annoyances go away (with or
without my help), sometimes I'm 'forced' to accept new ones (even writing code
doesn't mean I get everything the way I want). What does bother me is that
once a change is made, there will be those who will come out screaming if we
don't think about those questions ahead of time.
I am hesitant to say all of this, becuase there are those who will
claim to see
blame in all of this. I assure you all, there is none. These are general
concerns of mine that really address the entire project and not just this
specific topic. Case in point, slimserver used to be 'read on-the-fly' and
store everything in memory. Users complained and we now have a db. Now, you
start seeing requests to not have to be tied to a db and be able to
read on the
fly and store everything in memory. I'm over-simplifying to highlight the
symmetry :)
well, thats my rant. If I'm full of crap...just ignore me :)
-k
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
