— <b>Menu IDs: Peculiarities and Automated Handling</b>

<big>A</big>n empty string is considered a valid menu ID. Like any other menu ID, it must be unique.

Kickshaw ensures that all menu IDs are unique. Any new default menu ID it suggests is therefore guaranteed not to conflict. If preferred, you can let Kickshaw auto-generate all menu IDs. In addition, the Menu ID column can be hidden. The same applies to the 'Execute' column if pipe menus are not needed.

— <b>Drag and Drop vs. Editable Cells</b>

Menu elements can be rearranged by drag and drop: simply select an element and drag it from any position. However, since some tree view cells are editable, a user may occasionally activate editing by accident instead of starting a drag. A safe way to avoid this is to initiate the drag from the 'Type' column, as its cells are never editable.

— <b>Options</b>

Several options can be set from the application menu:
<span size="3000"> </span>
<b>1<span size="2000"> </span>a)</b> Create Backup Before Overwriting Menu File (enabled by default)
<b>1<span size="2000"> </span>b)</b> Use Tabs for Indentations in Saved Menu File (enabled by default)
<span background="#cccccc"> </span>  If disabled, XML tags are indented using four spaces per level.
<b>1<span size="2000"> </span>c)</b> Keep Root Menu Separate in Saved Menu File (enabled by default)
<span background="#cccccc"> </span>  If enabled, the root menu will contain only links to menus,  
<span background="#cccccc"> </span>  while the menus themselves are listed above the root menu, 
<span background="#cccccc"> </span>  as in the following example:
<span background="#cccccc"> </span>
<span background="#cccccc"> </span>  <tt>&lt;openbox_menu&gt;</tt>
<span background="#cccccc"> </span>
<span background="#cccccc"> </span>  <tt>  &lt;menu id="menu1" label="Menu1"&gt;</tt>
<span background="#cccccc"> </span>  <tt>    &lt;item label="item"/&gt;</tt>
<span background="#cccccc"> </span>  <tt>  &lt;/menu&gt;</tt>
<span background="#cccccc"> </span>
<span background="#cccccc"> </span>  <tt>  &lt;menu id="root-menu"&gt;</tt>
<span background="#cccccc"> </span>  <tt>    &lt;menu id="menu1"/&gt;</tt>
<span background="#cccccc"> </span>  <tt>  &lt;/menu&gt;</tt>
<span background="#cccccc"> </span>
<span background="#cccccc"> </span>  <tt>&lt;/openbox_menu&gt;</tt>
<span background="#cccccc"> </span>
<span background="#cccccc"> </span>  If disabled, everything is placed directly inside the root menu:
<span background="#cccccc"> </span>
<span background="#cccccc"> </span>  <tt>&lt;openbox_menu&gt;</tt>
<span background="#cccccc"> </span>
<span background="#cccccc"> </span>  <tt>  &lt;menu id="root-menu"&gt;</tt>
<span background="#cccccc"> </span>  <tt>    &lt;menu id="menu1" label="Menu1"&gt;</tt>
<span background="#cccccc"> </span>  <tt>      &lt;item label="item"/&gt;</tt>
<span background="#cccccc"> </span>  <tt>    &lt;/menu&gt;</tt>
<span background="#cccccc"> </span>  <tt>  &lt;/menu&gt;</tt>
<span background="#cccccc"> </span>
<span background="#cccccc"> </span>  <tt>&lt;/openbox_menu&gt;</tt>
<span background="#cccccc"> </span>
<b>2<span size="2000"> </span>a)</b> Sort Execute/Startupnotify Options (disabled by default)
<span size="3000"> </span>
<span background="#cccccc"> </span>  This ensures a uniform order of the menu's options.
<span background="#cccccc"> </span>  "<u>E</u>xecute options" refer to the options of an Execute action<sup> </sup>
<span background="#cccccc"> </span>  (not to be confused with the deprecated "<u>e</u>xecute" options).
<span background="#cccccc"> </span>  The arrangement follows this pattern:<sup> </sup>
<span background="#cccccc"> </span><tt> - prompt</tt><sup> </sup>
<span background="#cccccc"> </span><tt> - command</tt>
<span background="#cccccc"> </span><tt> - startupnotify</tt>
<span background="#cccccc"> </span><tt>   - enabled</tt>
<span background="#cccccc"> </span><tt>   - name</tt>
<span background="#cccccc"> </span><tt>   - wmclass</tt>
<span background="#cccccc"> </span><tt>   - icon</tt>
<span background="#cccccc"> </span>  When this setting is active, options can no longer be reordered.<sup> </sup>
<b>2<span size="2000"> </span>b)</b> Always Notify About Execute Option Conversions (enabled by default)<sup> </sup>
<span size="3000"> </span>
<span background="#cccccc"> </span>  <tt>'execute'</tt> options are deprecated.
<span background="#cccccc"> </span>  <tt>'Execute'</tt> actions remain valid.
<span background="#cccccc"> </span>  Deprecated 'execute' options are automatically converted to 'command' options.
<span background="#cccccc"> </span>  A message is displayed when such a conversion has taken place.
<span size="3000"> </span>
<b>3<span size="2000"> </span>a)</b> Use Client-Side Decorations (disabled by default; change requires restart)
<b>3<span size="2000"> </span>b)</b> Show Menu Button Instead of Menubar (enabled by default; change requires restart)

— <b>Shortcuts Acting as 'Switches'</b>

The 'Find' grid can be shown or hidden with the same shortcut. The same applies to the 'Find and Replace', 'Shortcuts', and 'Hints' windows.

<tt>Find:           CTRL + F
Find &amp; Replace: CTRL + H
Shortcuts:      CTRL + L
Hints:          F1</tt>

These windows can also be closed by pressing the Escape key.

— <b>Deactivation of Built-in Interactive Search</b>

GTK’s built-in interactive search, which is enabled by default in tree views, has been disabled in Kickshaw. This is because Kickshaw provides its own search functionality, and the built-in search does not work properly in this context.
