Bugzilla – Bug 2409
Settings help text should indicate dynamic behavior vs. rescan required
Last modified: 2009-09-08 09:29:21 UTC
It is not very clear to me which settings under Server Settings are dynamic and which ones require a rescan of the library. And for those that require a rescan, which type of rescan will be sufficient. It would be useful to indicate when the settings take affect along with the descriptive help text for each setting. Discussion: http://forums.slimdevices.com/showthread.php?t=17575
Server Settings->Behavior: Articles To Ignore When Sorting (full rescan required) Group Disc (already triggers rescan when changed, but needs text) should ignored articles also automaticall trigger a scan? it doesn't curently.
Yes.
kdf - do you have this one?
sure. I'll take care of what's noted so far. Any other prefs that require scan, let me know and I'll do them too.
committed to trunk at change 5025 let me know if more settings require rescan if the list is complete,I will merge to 6.2.1
Whoa. I don't like the idea of automatically triggering a scan at all. This can be very much a non-trivial operation for most installations. Are you safe when someone changes one setting that triggers a scan, then a minute or two changes another? Isn't this really just a call for better Help? See enhancement request #2487.
It does trigger an immediate rescan. I don't know what happens when you select another immediate-rescan setting. Does it restart, abort, or ignore the next change?
a new scan will stop an existing one and start over. running a rescan has been something that several settings already do when required. old argument, done too much. dan. i'm no longer doing this one. Jim, feel free to put forth some code any time.
lets resolve this in the trunk for the 6.5 release.
This wil be part of the Settings rework.
*** Bug 2548 has been marked as a duplicate of this bug. ***
Settings rework isn't going to make it for 6.5...
Brian, Dean asks that you keep in mind this behavior and make sure the help text is clear where applicable.
This bug appears to have been fixed in the latest release! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look. Make sure to include the version number of the software you are seeing the error with.
Can you please point out how this problem has been fixed. It is not in the notes and I do not see it in the latest release. Thank you.