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 165598 - Keyboard shortcuts don't work in fullscreen
Keyboard shortcuts don't work in fullscreen
Status: RESOLVED FIXED
Product: eog
Classification: Core
Component: image viewer
2.12.x
Other All
: Normal normal
: ---
Assigned To: EOG Maintainers
EOG Maintainers
eog-ng
: 322010 331567 338825 420857 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-01-29 12:01 UTC by Per Cederberg
Modified: 2007-03-22 11:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Per Cederberg 2005-01-29 12:01:58 UTC
The delete button work well when in normal collection view, displaying many
images at once. Once the application is switched to fullscreen mode, the delete
button stops responding which is annoying and hard to understand for a
non-technical user.

Other information:
Comment 1 Teppo Turtiainen 2005-06-26 10:03:28 UTC
Confirmed with 2.10.0.
Comment 2 Sergej Kotliar 2005-12-03 15:25:47 UTC
In fact, no keyboard shortcuts seem to work in fullscreen, except three
shortcuts that close the fullscreen view: Esc, Ctrl-W, F11. 

Changing the title of this bug to reflect this.
Comment 3 Sergej Kotliar 2005-12-03 15:28:24 UTC
*** Bug 322010 has been marked as a duplicate of this bug. ***
Comment 4 Lucas Rocha 2006-01-10 03:00:52 UTC
All keyboard shortcuts work fine in fullscreen but the Del one in EOG 2.13.3.
Comment 5 Lucas Rocha 2006-02-27 19:39:59 UTC
*** Bug 331567 has been marked as a duplicate of this bug. ***
Comment 6 petrosyan 2006-03-23 13:10:39 UTC
Ctrl+0 shortcut doesn't work in fullscreen mode anymore, while Ctrl+- and Ctrl++ work just fine.
Comment 7 petrosyan 2006-03-23 13:11:02 UTC
this is in eog-2.14.0
Comment 8 Sergej Kotliar 2006-04-17 21:46:38 UTC
*** Bug 338825 has been marked as a duplicate of this bug. ***
Comment 9 Jaap A. Haitsma 2006-04-20 21:08:57 UTC
IMHO the most nasty shortcut that is missing is the one for rotation. If I show a set of pictures to friends I usually do this in fullscreen mode, but then I can't rotate the pictures I took in portrait mode :-(


I've looked into the code a bit. There are basically three files where shortcuts are defined

/shell/eog-window.c
This contains all the shortcuts you'll see in the menu and these are executed when we see the eog window. handles: zooming, rotation, image deletion, fullscreen, prev/next image

/libeog/eog-scroll-view.c
has shortcuts for scrolling the image up down left right when there are scrollbars and also handles zooming

/libeog/eog-full-screen.c
defines shortcuts for leaving fullscreen, prev/next image and the shortcuts defined in eog-window.c do not when we are in this mode.

So in order to have some shortcuts working in fullscreen we should add code to 
/libeog/eog-full-screen.c, but it's not clear to me (yet) how I for example can do rotation overthere.

But this brings me to another question. Currently shortcuts for the same operation are defined at multiple places in the code and this ofcourse leads to inconsistencies (e.g. the Ctrl+0 shortcut not working in fullscreen, while it works while there is a window)

Isn't there a way we can get all these shortcuts defined in one place?
Comment 10 Lucas Rocha 2006-04-21 05:12:31 UTC
Hey Jaap, actually, in eog-ng branch I plan to remove this separate fullscreen implementation (which has lots of duplicated code) and make full screen a mode of eog-window. This would solve this problem.
Comment 11 Jaap A. Haitsma 2006-04-21 09:01:16 UTC
Cool!!

Are you already hacking in the eog-ng branch??
Is eog-ng planned for 2.16??
Comment 12 Lucas Rocha 2007-03-18 00:02:37 UTC
eog-ng branch, which has a full rewrite of eog's core, has been merged into trunk as part of 2.19/2.20 development cycle. Therefore this bug is fixed now. Thanks for the report!
Comment 13 Felix Riemann 2007-03-22 11:29:33 UTC
*** Bug 420857 has been marked as a duplicate of this bug. ***