You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In views where there is an expandable hierarchy, particularly in the result list for an Analysis query, it would be useful to have an option to expand all (and collapse all) groups. At present, to see the contexts in which the phrase I searched for occurs, I need to click separately on the minuscule "expand" triangle for each result. (Also, at least in Firefox under Windows 10, clicking on that triangle once only brings it into focus, and a second click is needed to execute the expansion.)
The text was updated successfully, but these errors were encountered:
Hi @danbalogh, in the result list of the Analysis query this could have serious performance implications. Actually the KWIC visualization is designed especially for this use case, when you want to examine the contexts. Other hierarchical views may be less problematic though, like resource overview of the Documents & Annotations in the Project section. We could add it for these less problematic cases.
Thanks, if this is technically troublesome, then of course it is not essential. I'm afraid I no longer recall why I would have preferred to be able to expand the search results rather than feed all of them to a KWIC. Possibly just to save a couple of clicks. At any rate, "expand all/collapse all" would I think be a good idea wherever feasible.
In views where there is an expandable hierarchy, particularly in the result list for an Analysis query, it would be useful to have an option to expand all (and collapse all) groups. At present, to see the contexts in which the phrase I searched for occurs, I need to click separately on the minuscule "expand" triangle for each result. (Also, at least in Firefox under Windows 10, clicking on that triangle once only brings it into focus, and a second click is needed to execute the expansion.)
The text was updated successfully, but these errors were encountered: