[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [PATCH] kmenuedit enhancment
From:       David Faure <david () mandrakesoft ! com>
Date:       2002-02-09 16:15:06
[Download RAW message or body]

On Sat, 9 Feb 2002, Raffaele Sandrini wrote:

> > Maybe it should use NoDisplay to hide an entry from the menu ?
> > That is, maybe deleting can still use Hidden, but hiding could use
> > NoDisplay (I know, the naming is confusing).
> > What difference does it make? Well, when an app uses the .desktop filename
> > of another app to start it (e.g. when kfmclient starts konqueror), it needs
> > the .desktop file to exist as far as ksycoca is concerned, i.e. Hidden=true
> > *breaks* this.
> > NoDisplay simply hides from the menu, but still makes the information in
> > the .desktop file available to other apps which want to programmatically
> > start it.
> >
> > Since moving a .desktop file has to delete the old one by adding
> > Hidden=true, this should remain that way though, otherwise there would be
> > two versions of the .desktop file in ksycoca.
> >
> > Hidden=true should really have been named Deleted=true......
>
> Ohh. I didn't even know about a NoDisplay tag... Hide can of course use it...
> What is important to me is to say the user wich items are made by root ->
> therefore the Dialogue wich tells him that a specific item can't be deleted.

!? It _can_ be "deleted", that's what Hidden=true is for. The effect is
the same as deleting the item: it won't appear in the menu, ksycoca won't
know about it... Don't tell the user that an item can't be deleted, that's
not true.

David.

[prev in list] [next in list] [prev in thread] [next in thread]