Server Version#: v1.32.6.7468-07e0d4a7e
Player Version#: 4.8.3
Hi.
Some inconsistencies I’ve noticed with navigating Search in Plexamp on a Mac.
In short:
-
Search screen interface behaves inconsistently, at least when used on desktop.
-
Activate Search Global Keyboard Shortcut doesn’t act exactly like clicking the Search screen’s button.
I appreciate that Global Keyboard Shortcuts are a feature “for the real pros” but think this one’s a bugbear of mine and might actually be a full-on bug because in effect it’s more of a long way round than a shortcut
In more depth:
1A) When I click the Search navigation button/icon (I’m going to call it a button henceforth) or press the Global Keyboard Shortcut (mine is shift-F4) from another Plexamp screen (eg. Home, Library,) the initial Search screen is brought up and the input box is activated.
This is expected behaviour, no problem here.
1B) Pressing the Search button when an item tree has been browsed to (I’m no longer on the initial results page) returns me to the results page. A second click activates the search input box.
This is almost the expected behaviour although I personally would expect the input box to be activated in one click as above, if your view is that that screen’s primary function is entering a search.
1C) When I’m in another Plexamp screen and an item tree has been browsed to, pressing the Search button takes me back to that item tree from which I can navigate elsewhere including to the initial search page via various methods, but I need to perform another click to run a new search.
Not completely expected behaviour if you take the view I describe in 1B.
2A) Pressing the Global Keyboard Shortcut for Search when an item tree has been browsed to (whether or not the Search screen is already open) focuses the app and activates the Search screen.
Repeated presses of the shortcut do nothing and I have to pick up the mouse or press esc to go anywhere else.
I expect the result of 1B. The keyboard shortcut ought to act exactly like its equivalent button.
2B) This is an edge case but I think once you test and replicate this it will illustrate my issue with the feature:
Using the Global Keyboard Shortcut for search after having navigated to the initial Search page focuses the app and activates the search input box.
How I think the keyboard shortcut specifically ought to work:
When I press the keyboard shortcut, whether the app has focus or not, then depending on the context of which part of Search I’m currently in
a) the actual search input box should be activated or
b) the initial page of the Search screen should appear, with a second press or click of the navigation button activating the search input box.
