Definition Query Icon in Table of Contents
@KoryKramer , thanks for the reply and explaining the thought process behind implementing this or not.
I have found a workaround where I add an * asterisk in layer layers headers in the TOC that have a filter or def query, as a marker. It's not an issue when I collapse groups or nested groups. I never have to "hunt" for these "markers", as I only need them to remind me or others that the layer has a def query or filter on it.
Adding a badge or icon in the TOC to indicate that the dataset has a filter, any filter, would be super useful, and not that complex...
I don't necessarily need a reminder when I am running a tool (although the new tooltip is really cool), rather, when looking at the data, I need to know if the whole dataset is being displayed, or if it's being filtered.
I am surprised (and slightly disappointed) at the fact that new ideas that are well supported/useful to users would not be implemented for fear of adding more complexity to the UI...I have been using ArcGIS for a long time, and have learned to ignore functionality that I don't need for my workflows. Adding subtle complexity is important for the tools to be more and more useful.
@PaulHoefflerGISSand @Marie_Ducharme agreed. I know the idea originator made a statement about definition queries specifically, but one simple multipurpose icon would be fine, because I agree with you @KoryKramer , a bunch of different icons could get messy quick. Maybe on hover it tells you what kind of filter(s) are active? I wouldn't find that overly complex. Having to wonder whether a filter is on and then shuffling around with those filters (which only address definition queries), checking layer properties, or having to open a GP tool - that is overly complex. If the goal really is to reduce complexity in the user interface, then we should favor feature-rich and intuitive UI elements over those complicated workarounds. Pro has a lot of room for improvement in that department. Hopefully the commentary here outlines the need for that at-a-glance, no input required filter warning.
For the nesting issue, I think we're giving up too easy, and @PaulHoefflerGISS is onto something. It is possible (and common) for UIs to differentiate between groups and contents intuitively. For example, in some areas, checkboxes turn into blocks when some but not all child components are checked.
In the case of charms, this probably wouldn't work as there are already checkboxes in the TOC that do something different, but a similar concept would. Several Adobe apps use size to differentiate between properties of groups and child content. Even if the group Vector were collapsed, you'd still see the small red square, which tells you something within that group is selected. Big red square means it's this exact object or group that is selected. It makes it pretty easy to drill down whether the nested object is visible or not - it literally lights up a trail for you to follow. Much less hunting and pecking thanks to the small red square.
In ArcGIS Pro, I could see 'small dot' to indicate something within this group has a filter, and 'big dot' to indicate the layer or group directly. That would keep things simple.
The flag on the GP tools is very, very much appreciated, but again - it does not provide the information at a glance, which is the core of the request.