After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 678271 - Touch screen click behaviour differs from mouse click
Touch screen click behaviour differs from mouse click
Status: RESOLVED FIXED
Product: gnome-mines
Classification: Applications
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: gnome-mines-maint
gnome-mines-maint
touch,ready
Depends on:
Blocks:
 
 
Reported: 2012-06-17 21:03 UTC by Kat
Modified: 2017-11-02 18:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kat 2012-06-17 21:03:33 UTC
While it is possible to hold down Ctrl and left click to set a flag (instead of right click), it is not possible to hold down Ctrl and touch the screen to set a flag.

Just tapping on its own (without the Ctrl key modifier) works fine, as does using a mouse with the Ctrl key.
Comment 1 Michael Catanzaro 2014-02-21 00:51:40 UTC
*** Bug 724824 has been marked as a duplicate of this bug. ***
Comment 2 Michael Catanzaro 2014-02-21 00:52:26 UTC
Comment I don't want to lose from Bug #724824:

"Also, when some way to set a flag is implemented, it should be mentioned in the
help - right now it just says to 'right click', which you can't do on a tablet."
Comment 3 Adam Williamson 2014-02-21 01:37:36 UTC
I don't believe 724824 is actually exactly a dupe. I did find this bug first, and read it. This appears to be describing something different: behaviour when you have both a mouse/keyboard and some kind of touch screen.
Comment 4 Michael Catanzaro 2014-02-21 02:32:58 UTC
(In reply to comment #3)
> I don't believe 724824 is actually exactly a dupe. I did find this bug first,
> and read it. This appears to be describing something different: behaviour when
> you have both a mouse/keyboard and some kind of touch screen.

I changed your bug to be a duplicate of Bug #678272 instead.  I agree this one is different.
Comment 5 Bastien Nocera 2014-08-29 17:34:53 UTC
(In reply to comment #3)
> I don't believe 724824 is actually exactly a dupe. I did find this bug first,
> and read it. This appears to be describing something different: behaviour when
> you have both a mouse/keyboard and some kind of touch screen.

Frankly, edge case.
Comment 6 Adam Williamson 2014-08-30 00:27:59 UTC
Do you mean the hardware's an edge case, or the interaction with Mines is an edge case?

If the former, I disagree: I think either a majority or a very large minority of new Windows laptops have touchscreens, and obviously everything in the 'convertible' class of large tablets with detachable keyboards does.

If the latter, that's more arguable, but obviously at least one person with such a device found that the natural thing to do when using it, or the bug report wouldn't exist.
Comment 7 Bastien Nocera 2014-09-01 13:12:37 UTC
(In reply to comment #6)
> Do you mean the hardware's an edge case, or the interaction with Mines is an
> edge case?

I mean using keyboard + touch at the same time.
Comment 8 Kat 2014-09-01 13:57:50 UTC
I was using a netbook with a touchscreen and a really small touchpad when I filed this bug. I find it natural to touch the screen for clicking instead of using a touchpad when using this device and am not in the habit of carrying a spare mouse around.

The workaround (although not really a solution) would be to add a way to set a flag using only a touchscreen which would work as quickly as using Ctrl+left click. Keeping in mind that the point of the game is to defuse a mine field as quickly as possible.
Comment 9 Robert Roth 2017-11-02 17:50:51 UTC
I have just tried Ctrl+touch on a touchscreen (Asus Transformerbook laptop), and it works perfectly for flagging mines, simply touch for "flipping" a field. Is this still a problem for you, Kat?
Comment 10 Kat 2017-11-02 18:29:24 UTC
Hi Robert, I haven't got access to my touchscreen device at the moment and no idea when I can get it back, so closing as resolved. Will re-open if I hit the problem again :)