Bug 183024 - Okular forgets toolbar settings after full screen mode
Summary: Okular forgets toolbar settings after full screen mode
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.7.4
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-03 17:31 UTC by Claus Appel
Modified: 2011-06-19 18:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Claus Appel 2009-02-03 17:31:07 UTC
Version:           0.7.4 (using 4.1.4 (KDE 4.1.4), 4.1.4-2.fc9 Fedora)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.12-78.2.8.fc9.i686

Okular has a toolbar that can be switched on and off (Settings -> Show Toolbar). But sometimes, after switching to and from full screen mode (Settings -> Full Screen Mode), Okular forgets whether it is supposed to show the toolbar or not. 

The bug is reproducible like this: 

1. Open Okular, NOT in full screen mode. 
2. Enable toolbar. 
3. Go into full screen mode. (The toolbar will vanish as it is supposed to, but it will come back when you leave full screen mode.)
4. Close Okular while still in full screen mode. 
5. Open Okular again. It will remember to open in full screen mode. 
6. Leave full screen mode. 
7. The toolbar is now gone. (It can be re-enabled easily enough. It is just annoying that Okular forgets the setting.)
Comment 1 Pino Toscano 2009-02-07 11:25:09 UTC
Theorically it forgets nothing:
- you switch to fullscreen mode -> toolbars and menu bar are hidden
- you then quit the application -> the window state is saved automatically (by kdelibs routines, so no ad-hoc code), including visibility of toolbars and menu bar
Of course this is not expected, but then this requires to fight (again) the windowing code in kdelibs.
Comment 2 Albert Astals Cid 2011-06-19 18:38:06 UTC
This was fixed in some version, don't remeber which one. Works for sure in 4.6.3