Quote:
Originally Posted by BetterRed
Must have been some inter-galactic mind-reading going on.
|
The changes were related to an @ownedbycats enhancement request -- use checkboxes in look&feel to set category order. Hierarchy and categorization followed naturally
Quote:
|
Has Hierarchy always been per library, I somehow ended up with custom column names in that list for Library A that have never existed in Library A.
|
Yes, but because it was a manually typed list you could put anything you wanted there. Columns in the list but not in the library were ignored.
Quote:
 be good to have a visual clue to differentiates global and per library settings - e.g underline per library field labels - might be hard to enforce though.
BR
|
The goal is to eventually move anything that references columns (usually via lookup names) or other specific library data to a per-library setting (a db setting). Things that are "general" UI settings, for example line spacing, remain as user-level settings. And yes, I recognize that the choice of where to put a setting is sometimes not obvious.
Also yes, marking db vs user settings would be a can of worms. First problem is figuring out which is what. Second problem would be maintaining the UI as the settings migrate. I don't want to go there.