After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 359003 - alacarte should not enable inlining when displaying menu and should create entries with disabled inlining
alacarte should not enable inlining when displaying menu and should create en...
Status: RESOLVED FIXED
Product: alacarte
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Alacarte Maintainer(s)
Alacarte Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-10-02 13:57 UTC by Frederic Crozat
Modified: 2006-10-02 23:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
hack to disable inlining (2.04 KB, patch)
2006-10-02 17:30 UTC, Frederic Crozat 		none Details | Review

Description Frederic Crozat 2006-10-02 13:57:57 UTC 
Menu file in Mandriva Linux are using inlining to prevent sub menu proliferation like this :

  <DefaultLayout inline="true" inline_limit="1" inline_header="false">
    <Merge type="menus"/>
    <Merge type="files"/>
  </DefaultLayout>

Unfortunately, inlining is also applied when creating a submenu : when you create a single entry in a submenu, it will be merged immediatly in the parent submenu, which is very disturbing for end users.

I suggest adding inline="false" to new created submenu entry to prevent this problem, by adding a DefaultLayout node to their <Menu> node.

Another possible addition would be to control inlining properties in submenu property dialog but that is another story ;)
Comment 1 Frederic Crozat 2006-10-02 17:30:48 UTC 
Created attachment 73870 [details] [review]
hack to disable inlining

ugly hack (but it works) to disable inlining for new created menu.

I haven't used Layout node to do that because it would require more invasive changes in the code.
Comment 2 Travis Watkins 2006-10-02 23:39:19 UTC 
Applied, thanks.