Keld J�rn Simonsen posted <[EMAIL PROTECTED]>, excerpted
below,  on Thu, 09 Oct 2003 17:40:13 +0200:

> On Thu, Oct 09, 2003 at 12:23:51PM +0200, Buchan Milne wrote:
>> 
>> Keld J�rn Simonsen wrote:
>> 
>> > Also I then noticed in the kde control center that there was a looknfeel
>> > section with a panel editing posibility, but that did not include
>> > editing this item. I find it strange that the kde control module is not
>> > available from the kde control center.
>> 
>> It is there, KDE Control Center->LookNFeel->Panels->Menus (tab)
> 
> I cant find it there, I looked all over again. Current cooker.
> There is no menus tab under panels (or the one that is there, is only
> for setting the background for the menus.)

Here, it's under KControl, LookNFeel, Panel, Menus (tab).  That's a
separate entry from Panels, which as you note, is for setting menu item
background only, and has only a single tab.

However, at some point in Cooker, there was a complication with the menus
that I had to resolve manually.  I'm guessing this is where the issue is.

Mandrake's menu system is based on the Debian menu package.  KDE packages
are adapted to use the Debian global menu system, which then recreates the
KDE menu, including non-KDE Mandrake applications in it that wouldn't be
included in the official "non-distrib-ified" KDE product.

KDE as installed here now includes both a "panels" and a "panel" menu
entry.  However, as in the Mandrake/Debian menu package, both entries are
listed with the "panel" name, which obviously creates a conflict with KDE,
since it uses separate *.desktop files for each entry, and there can't be
two "panel.desktop" files in the same LookNFeel dir.

I suspect that one of these entries is for an old version, and that either
the current KDE only includes one of them, or has a different name for the
other one.  However, somewhere in the untold updates I've done to my
Cooker KDE packages, the one wasn't renamed or removed as it would be in
the current packages, thus, I ended up with duplicate names, which meant
when the menu was created during install, the last one to be created
overwrote the previous one.

Once I realized functionality was missing, and saw from menudrake that
there was supposed to be a second menu entry that I was missing, I went to
found the appropriate *.mnu entry in /usr/lib/menu and copied it to
/etc/menu (where the local sysadmin overrides live), then changed it as
appropriate so it wasn't stomping on the other entry, by adding an "s" to
the "panel" that was the former KDE file name used.  After rebuilding the
menus, I had both entries once again, with all the functionality I was
used to, and I was once again a happy camper.

Note 1: I could have managed the change directly from menudrake, but
that I find menudrake a bit limiting and it's single override file
solution a bit less than robust, so any changes I make to my menu system I
now make manually, to the core *.mnu text files, as appropriate.  I only
use menudrake for read-only checking the menu, as I did in the example
above.

Note 2:  This Mandrake/Debian menu system solution is why the KDE 3.2
alpha2 packages Laurent put out don't integrate with the standard Mdk
menus, having only the KDE original menus, because they  haven't been
patched for the Mdk solution, yet.

Note 3:  This missing kcontrol entry is a bug.  However, I haven't filed
it as such, because I've customized my menus to the point I'm not certain
whether it would exist on a normal system or not.  IOW, I wasn't certain
whether it was my customization at fault, or Mandrake's.

Anyway, the functionality is there, but it may be missing from your
version (as it was from mine until I fixed it), due to the missing entry,
due to the file naming conflict between the two kcontrol applets.

-- 
Duncan - List replies preferred.   No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin



Reply via email to