On 15 Mar 2002 14:14:23 +0100, Dominik Vogt wrote: > > On Fri, Mar 15, 2002 at 11:51:33AM +0000, Mikhael Goikhman wrote: > > > > I like this patch, but can we delay it until we solve the problem of > > specifying more than one action for the menu item? This will make it > > possible to specify "Grayed" option just like "CommandOnMouse 2" option. > > How about dumping that whole screwed up method to specify options > for individual menu items and doing it from scratch? E.g. > > NewAddToMenu menu_name item_name [(item_options)] ItemAction > NewAddToMenu menu_name (menu_options)
This is almost exactly what I had in my mind. I though about: + item_name [item_default_action] [(item_options)] The default action may probably be included in option, it is for backward compatibility. For example, separators don't have default action. > and > > + item_name [(item_options)] ItemAction > + (menu_options) > > The item_options and menu_options are enclosed in parentheses and > can be omitted. > > Menu options: > DynamicPopupAction > DynamicPopdownAction > MissingSubmenuFunc > SidePicture > SideColor > (did I forget anything?) > > Item options: > Greyed > Hotkey > Picture > > The mini icons should stay parts of the labels because they are > formatted like the text. They may, but should not really stay parts of the labels. They cause excaping problems with '&' and several other symbols. There are currently problems/inconsistencies with how fvwm escapes '&', if there is underline in the item, '&' should be escaped as "\&", otherwise as "&&"! This is a real problem for menu autogenerating scripts. I think we should only support this in the old compatibility syntax when the default action is specified as-is and not as an option. But I don't want to make syntax less usable, so more thoughts are needed. > The proposed syntax is almost completely compatible with the old. > Only items that have a name enclosed in parentheses but no action > or items that have an action beginning with a left parenthesis > are interpreted differently. I can't hink of any reason why > someone would want that. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
