Hello,
Really loving this app as it uses way less resources on my Surface Pro 3.
I have an issue though that I haven't seen anyone else report so here goes...
When using the touch screen on my surface to select various options (e.g. 'My Library', 'New Releases', play album button, etc) more often than not the app does not respond. The input is being recognised as the menu item highlights but it takes a few taps before it works.
I know you probably didn't have touch in mind when developing this but I see no reason why this shouldn't work as the regular website works just fine. Interestingly scrolling is ok and I'm not seeing the same issue with the desktop settings popup.
Here's a video of me replicating the issue. Not the best quality but you can see where I'm tapping multiple times to access listen now - https://youtu.be/uFPm5lyiHKg
Device: Surface Pro 3 i5/4gb
OS: Windows 10
Version: 3.1.0
Thanks in advance, If this gets fixed I will donate!
Does this issue occur in chrome?
I think this is just because of how touch screens, they don't have a concept of "hover" so tapping once triggers the hover event.
Thanks for getting back to me so quickly!
Chrome behaves fine, I was using it briefly before I discovered your app. As I don't think the direct screen capture showed it off so well, I've recorded a video which shows a comparison between chrome and GPMDP.
When using the surface pen, the input is pretty much the same as using a mouse and works great. The pen seems to sense close proximity of the screen and so supports hovering over buttons, etc. Its just when I use my fingers when it doesn't work as expected.
Hope this helps, let me know if you need any more info
Cheers
@st33ly Can you please confirm this issue is present on 3.2.1
@st33ly Can you please confirm this is present on 3.2.4
Hi Sam,
Sorry it鈥檚 taken a while to get back to you. Prepare for a lengthy post...
I've reinstalled the latest version of GPMDP on my surface to check and I can report that there has been some improvement but overall it鈥檚 still not great on touchscreen.
Elements that work fine:
Media controls (play/pause next track, etc)
Thumbs up/down
Playlist button
Album art button
Desktop settings popup window
Track seek bar and volume sliders - the grab point on these seem to be above the actual UI element. I have to aim almost a centimetre above the orange dot to drag it successfully but otherwise works as expected. In chrome this works fine.
Elements that could be improved:
The back button doesn't always work when tapped. (On a side note, I love that you have included this but it鈥檚 not in an obvious place. I feel it would be better situated at the top left of the main window)
The burger menu button at the top left has improved but it seems like my thumb works better than fingers. It might be that I'm not hitting the sweet spot exactly but it鈥檚 hard to tell. It seems fine on chrome. Might be a long shot but if it鈥檚 possible to increase the touchable area of this button I think that might help?
The animation for the popout menu is a little sluggish on my surface pro 3 but is fine on my PC. This is possibly due to the graphics hardware of the surface but thought I鈥檇 let you know in case you can improve it?
The sidebar itself is still the same as before in that when I tap the options it will highlight but won鈥檛 actually switch over to that section. Scrolling works fine here.
Browse stations list works ok although there is slight graphical bug when scrolling where you can see a box outline. (Almost like when selecting icons on windows desktop)
Bad stuff:
I put this in a different section as I know it鈥檚 something that Google has changed for the worse which affects both chrome and GPMDP. In album and track lists, dragging my finger to scroll about now selects the album image and drags that instead. This is the same on the playlists window. I am constantly mis-scrolling or rearranging tracks by accident. I have to use the side of the window to scroll around instead.
There should really be a delay here to prevent it from happening like the android app but I guess it鈥檚 out with your control. It kinda sucks and is really bothering me. I鈥檓 guessing this behaviour changed when they revamped the logo.
So in conclusion, I can see you have been working hard on this app and I have been using it on my PC with no issue. Maybe the touchscreen support will get better in the future but I guess it depends a lot on how Google is designing the interface.
Thanks for looking into this for me. If you need any more info or testing just let me know :)
Hi Sam, I know this post is about a month old now but I found it by searching the issue. I have the exact same issue with my Surface Pro 3 when using only touch. Your app works perfectly when I use a mouse or the touchpad on the keyboard but when trying to just use touch on the screen itself I encounter the exact same issues as the poster above. Your app is awesome so it's not like I'm going to stop using it, but I just wanted to confirm what the above poster is experiencing.
Cheers,
Is this bug still existing in v.3.2.5?
@Bohne13 I have no idea 馃槅
No way to test it 馃槩
Hello,
So I've recently tested v3.2.5 and I'm pleased to say that the scrolling issue I mentioned above in my last post is gone which makes it a bit more usable.
Other than this, many of the same issues are still in this release:
all of these issues are not apparent when using GPM in chrome.
Of course the base GPM itself still has some issues with touch
I've been trying out players to see what works best. I used to use OutColdPlayer which was excellent but this was discontinued. The GMusic app works ok but has some bad UI decisions. So far I'm torn between using that and GPMDP with a mouse.
Its a shame that Google arent embracing desktop apps for their music service. Almost makes me want to switch over to Spotify.... :/
I'll continue to keep an eye on new releases and hopefully one of these days things will improve!
Cheers
I am using teamviewer for remote control app with touch interaction enabled on my Nexus 9 to test this on Windows 10 desktop using teamviewer 11 host. (this nearly perfectly emulates a lag free touchscreen when used over LAN so might be worth using for testing if dev has the hardware) I can confirm several of these issues in 3.2.5.
鈥rab points for volume and seek bar are slightly above bars
鈥crolling seems to work fine
鈥ack button does not always work (will work eventually if tapped repeatedly)
鈥ide menu opens and closes fine but entries do not always work (same as back button)
鈥ouble tapping to play song from main screen or jump to song in playlist does not work (this does work in chrome)
@st33ly @greatwroth Had a brainwave today, can you guys please try enabling "native window borders" in the Desktop Settings, I think I know why the touch points are offset
That seems to correct everything I mentioned except the double tapping issue.
@greatwroth Double tapping will be interpretted as a zoom command so I am not too worried about that.
I will raise this as an issue with electron, finally something I can explain that makes sense to me 馃槅
electron/electron#6308
@greatwroth Can you also try the latest windows build. This bug might have been fixed upstream in Chromium
That did it. With system window borders disabled the grab points are correct, the side menu items and back button work properly, and even double tapping is working.
@st33ly @greatwroth Great news, so it looks like a whole load of touch screen issues were fixed in Chromium 51.XXX which means we will get these fixes in 3.3.0 when I release 馃榿
@MarshallOfSound I came back from holiday to find this thread updated :)
Using system window borders has fixed most of the UI issues for me also! Looking forward to 3.3.0!
:smile: :smile: :smile:
Most helpful comment
@MarshallOfSound I came back from holiday to find this thread updated :)
Using system window borders has fixed most of the UI issues for me also! Looking forward to 3.3.0!
:smile: :smile: :smile: