Bug 154971

Summary:	Closed menu-bar and toolbar can only be re-activated in config-file.
Product:	[Applications] digikam	Reporter:	Yellowshark <digikam.20.yellowshark>
Component:	Usability-Menus	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	caulier.gilles
Priority:	NOR
Version:	0.9.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:	8.4.0
Sentry Crash Report:

Description Yellowshark 2008-01-02 14:41:39 UTC

Version:           0.9.1 (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
OS:                Linux

There is a related - but not the same bug - with the menubar!

Open Digikam in standard view.
Click right at toolbar to open context menu "toolbar menu".
Click "Hide toolbar"

the toolbar is now gone and only to be reactivated by going to 
.kde/share/config/digikamrc 

[MainWindow Toolbar ToolBar]
Hidden=true

I somehow hid the menubar, too. No idea how. This could be the related bug mentioned above which I solved by changing the config file value for

MenuBar=Disabled

I guess there should at least be a method to right click and activate the bars again.

How relevant? The problem was posted in some forums as http://forum.ubuntuusers.de/topic/96786/?highlight=digikam+menubar

Cheers! 
Thanks!
I like Digikam anyway ;o)

Comment 1 Arnd Baecker 2008-01-02 15:23:18 UTC

"Settings/Show Toolbar" works for me to regain the toolbar.

About the menubar: this is discussed in 
http://bugs.kde.org/show_bug.cgi?id=147771

Comment 2 Yellowshark 2008-01-03 13:18:32 UTC

Hello Arnd,

yes, the more I test it the more I realize that Bug #147771  is the main Problem. The Toolbar Problem is a secondary problem that appears if the menubar is gone as there is no "Settings/Show Toolbar" anymore to choose. Simply because there is no menu bar. Ergo: Bug #147771

I guess this Bug is to be closed then, huh?
Cheers, 
Yellowshark

Comment 3 Arnd Baecker 2008-01-03 13:48:11 UTC

Hi Yellowshark, 
thanks for the feedback. I am closing this bug as you suggest.
The other bug seems, unfortunately, more complicated to fix ...
Best, Arnd