Bug 278346 - status bar is not preserved in full screen mode
Summary: status bar is not preserved in full screen mode
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Usability-FullScreen (show other bugs)
Version: 2.0.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-23 17:01 UTC by julien.t43+kde
Modified: 2019-08-13 12:10 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.3.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description julien.t43+kde 2011-07-23 17:01:14 UTC 
Version:           2.0.0 (using KDE 4.6.2) 
OS:                Linux

when switching on full screen, digikam doesn't keep status bar settings even if button in toolbar is always on.

Maybe it's better to make it disappear the first time, but if user enables it again, it should be kept.
Or either a setting should exist for which bar should be present or not in full mode (toolbar is always kept)


Reproducible: Always

Steps to Reproduce:
open digikam, display status bar if not enabled
go in full screen mode


Actual Results:  
no more status bar

Expected Results:  
at least, on the second retry, status bar should be present
Comment 1 Marcel Wiesweg 2011-08-06 14:00:15 UTC 
I guess the  status bar is hidden explicitly on purpose...
Comment 2 julien.t43+kde 2011-08-09 05:59:01 UTC 
maybe, but user should be able to override it (in preferences settings or elsewhere)
Comment 3 Tom Vincent 2011-09-04 13:44:20 UTC 
Additionally, status/tool bar settings are not preserved when *exiting* full screen mode.

For example:

1. Uncheck "show status bar" in Menu > Settings
2. Enter full screen mode
3. Exit full screen mode

Status bar is visible but still unchecked in the settings.
Comment 4 caulier.gilles 2011-12-18 10:17:59 UTC 
*** Bug 289260 has been marked as a duplicate of this bug. ***
Comment 5 caulier.gilles 2011-12-18 10:28:11 UTC 

*** This bug has been marked as a duplicate of bug 289262 ***
Comment 6 caulier.gilles 2019-08-13 12:10:31 UTC 
Fixed with bug #289262