Refactor Context Menus and make them use XAML & stylesheets (#4768)
* XAML verb menu * fix ghost FOV * spacing * rename missed "ContextMenu"->"EntityMenu" instances * move visibility checks to verb system * update comment * Remove CanSeeContainerCheck * use ScrollContainer measure option * MaxWidth / texxt line wrapping * verb category default Now when you click on a verb category, it should default to running the first member of that category. This makes it much more convenient to eject/insert when there is only a single option * only apply style to first verb category entry * Use new visibility flags * FoV -> Fov * Revert "only apply style to first verb category entry" This reverts commit 9a6a17dba600e3ae0421caed59fcab145c260c99. * make all entity menu visibility checks clientside * Fix empty unbuckle category * fix merge
This commit is contained in:
@@ -16,7 +16,8 @@ namespace Content.Shared.Verbs
|
||||
public readonly SpriteSpecifier? Icon;
|
||||
|
||||
/// <summary>
|
||||
/// If true, this verb category is shown in the context menu as a row of icons without any text.
|
||||
/// If true, the members of this verb category will be shown in the context menu as a row of icons without
|
||||
/// any text.
|
||||
/// </summary>
|
||||
/// <remarks>
|
||||
/// For example, the 'Rotate' category simply shows two icons for rotating left and right.
|
||||
|
||||
Reference in New Issue
Block a user