Bug 365410

Summary: Fullscreen only shows one image - no way to navigate.
Product: [Applications] digikam Reporter: Bizy <koen.bizy>
Component: Usability-FullScreenAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, erin-kde, koen.bizy, russell.every
Priority: NOR    
Version: 5.0.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In: 5.1.0

Description Bizy 2016-07-11 19:55:50 UTC
Presentation mode is fine, but when changing from preview mode to full screen mode, the navigation doesn't work.  No way to go to the previous or next image.

Reproducible: Always

Steps to Reproduce:
1. Go from preview mode to Fullscreen mode
2.
3.

Actual Results:  
No navigation possible

Expected Results:  
Navigation 

64-version (5.0.2) on Windows 7
Comment 1 Bizy 2016-07-11 20:29:54 UTC
PS:  via icon menu in preview mode  (when going to fullscreen mode by right clicking on the picture in preview mode:  that works fine!)
Comment 2 caulier.gilles 2016-07-12 04:04:10 UTC
In Setup dialog, you can customize the visible element while fullscreen.

Giles Caulier
Comment 3 Bizy 2016-07-12 07:36:50 UTC
Yes, I know... but unless I got you wrong, that's not the problem... The problem is that navigating is impossible. Nor with tab, nor with arrows, nor with the navigation buttons in the low left corner.
Comment 4 Maik Qualmann 2016-07-12 19:57:09 UTC
Git commit a19047f3eaf37b9993104a340f3217621326380b by Maik Qualmann.
Committed on 12/07/2016 at 19:56.
Pushed by mqualmann into branch 'master'.

fix navigation in slideshow toolbar under Windows and polish
FIXED-IN: 5.1.0

M  +2    -1    NEWS
M  +2    -3    utilities/slideshow/slideosd.cpp
M  +3    -3    utilities/slideshow/slideshow.cpp

http://commits.kde.org/digikam/a19047f3eaf37b9993104a340f3217621326380b
Comment 5 Maik Qualmann 2016-07-21 21:33:11 UTC
*** Bug 365919 has been marked as a duplicate of this bug. ***
Comment 6 Maik Qualmann 2016-07-25 21:39:16 UTC
*** Bug 366109 has been marked as a duplicate of this bug. ***