The File History graph is an extremely cool and useful way to visualize the status of a hydrus repository. It currently has tools to fit the graph to x and y ranges, and has four hardcoded togglable lines it graphs: "all files", "inbox", "archive", and "deleted". There's also a tag search that layers searches on top of these filters, which are always "AND"ed with the builtin predicates. So adding the "system:inbox" predicate turns "archive" into "archive AND inbox", which is always 0.
Rather than have queries that are layered on these four built-in queries, it would be useful to be able to simply add lines to the graph. The hardcoded lines are already hydrus queries, and it would be useful to be able to add a line to see how many images have a given tag compared to the total count of files, which isn't currently possible.
The File History graph is an extremely cool and useful way to visualize the status of a hydrus repository. It currently has tools to fit the graph to x and y ranges, and has four hardcoded togglable lines it graphs: "all files", "inbox", "archive", and "deleted". There's also a tag search that layers searches on top of these filters, which are always "AND"ed with the builtin predicates. So adding the "system:inbox" predicate turns "archive" into "archive AND inbox", which is always 0.
Rather than have queries that are layered on these four built-in queries, it would be useful to be able to simply add lines to the graph. The hardcoded lines are already hydrus queries, and it would be useful to be able to add a line to see how many images have a given tag compared to the total count of files, which isn't currently possible.