OS X desktop client of plexamp is used here.
I think it would be best that if the space bar is used music should be paused. At the moment it goes to the next song. I’d use right and left arrow maybe for navigation.
Also when entering search mode it would be great if you could start typing immediately. At this time you have to move over the search field and click on it.
Great improvement over version 1.0. This is by far the best player I have used so far.
On windows the space bar does whatever you last did with the mouse - click pause and play and from then on the spacebar will pause and play. Click next track and spacebar reverts to next track. No idea if the same for you but may be…
I’m finding the spacebar behavior to be unpredictable even inside what’s described above. For instance:
(I’m on OSX)
Song playing, I mouse over and click on the plex window.
Click in the plex window again because the transport controls don’t show when I hover. (why?)
Mouse over the album art till the transport controls pop up.
Click pause.
Spacebar now toggles play/pause as long as I keep focus on the plexamp window.
Now, if I click out of the window to desktop then click back in the window and hit spacebar it pops up the up next list.
I’m not a fan of this unpredictable behavior at all. Most audio apps do a static binding of spacebar to play/pause.
It would be nice if plexamp would respond to a spacebar for play/pause just by mousing over the window too. I can mouse over the window and scroll without having to click the window so using this same focus detection system to capture and interpret key presses would be great.
I assume Plexamp doesn’t use any specific key bindings, but that we simply see the operating system in action. Being able to scroll in hovered windows is normal behavior, as is that the focused element, like the last button you clicked, can be triggered by pressing space. (At least on Windows, I’ll assume it’s the same on OSX.)
Adding key bindings would be possible, to bind space to a specific action, but you’ll most likely never see this happening without the window being in focus, as that could lead to unexpected and potentially undesirable behavior.