Talk:Menu System 2 (Second Life)

From Grigbertz

Revision as of 16:23, 22 November 2008 (view source) Grigbertz (Talk | contribs) (New page: === conditional button texts === "?:" operand in button names === rlv conditional === isRlv conditional if rlv package reports === more than 12 buttons in menu === automatic '< Prev', ...) ← Previous diff		Current revision (15:24, 11 July 2009) (view source) Grigbertz (Talk | contribs) (Changed priorities)
(4 intermediate revisions not shown.)
Line 1:		Line 1:
-	=== conditional button texts ===	+	== Feature Requests ==
-	"?:" operand in button names	+	=== Public role ===
		+	Priority just above 'other' TRUE if conditional 'isPublic' is set.
-	=== rlv conditional ===	+	=== Button names from Variables ===
-	isRlv conditional if rlv package reports	+	Is this reasonably doable?
		+	[${leashbutton}$}]
-	=== more than 12 buttons in menu ===	+	===Conditionals as Menu Roles ===
		+	Either this or the feature below would be good
		+	---Main locked---
-	automatic '< Prev', 'Next >' or '<<', '>>'	+	===Menu Roles qualified by Conditionals ===
		+	---Main owner locked---
		+
		+	=== More than 12 buttons in menu ===
		+	Adds automatic '>' after the first 11.
		+
		+	== Lower Prio Feature Requests ==
		+	=== Menu buttons accessible by scripts ===
		+	# Last clicked menu button sets variable
		+	# Send button click specified by: Menu name, Button number (1-12)
		+
		+	=== Conditional Button Texts ===
		+	"?:" operand in button names
		+	== Note ==
		+	The priorities is just my preference right now. Maybe we should have a 'voting' system :) ''--Scarlett''

---

Current revision

Contents 1 Feature Requests 1.1 Public role 1.2 Button names from Variables 1.3 Conditionals as Menu Roles 1.4 Menu Roles qualified by Conditionals 1.5 More than 12 buttons in menu 2 Lower Prio Feature Requests 2.1 Menu buttons accessible by scripts 2.2 Conditional Button Texts 3 Note

Feature Requests

Public role

Priority just above 'other' TRUE if conditional 'isPublic' is set.

Button names from Variables

Is this reasonably doable?

[${leashbutton}$}]

Conditionals as Menu Roles

Either this or the feature below would be good

---Main locked---

Menu Roles qualified by Conditionals

---Main owner locked---

More than 12 buttons in menu

Adds automatic '>' after the first 11.

Lower Prio Feature Requests

Menu buttons accessible by scripts

1. Last clicked menu button sets variable
2. Send button click specified by: Menu name, Button number (1-12)

Conditional Button Texts

"?:" operand in button names

Note

The priorities is just my preference right now. Maybe we should have a 'voting' system :) --Scarlett