Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

beauty blank space in the menus #42

Closed
LeonaMorro opened this issue Aug 19, 2015 · 6 comments
Closed

beauty blank space in the menus #42

LeonaMorro opened this issue Aug 19, 2015 · 6 comments

Comments

@LeonaMorro
Copy link
Member

[01:07:20] Grey Mars: Before I fall asleep, one last question. Is there a way to define an empty button with the new menu order stuff? Nonfunctional, just a empty space for layout reasons between other buttons.
[01:11:35] Leona (slmember1): I guess not a Nonfunctional one ... Did you try a button with spaces as the button name?
[01:13:42] Grey Mars: I did not, as I assumed it might cause issues. if I remember right, .change menu order will in fact let you define buttons for cards that don't even exist. I'll experiment tomorrow, see if it will break anything to do that
[01:21:39] Leona (slmember1): Nods .. currently .change menu order don't check if there is a corresponding NC. For me thats no problem. In an earlier version I remember that Howard did check the existent of the corresponding card. There is also an entry for a "Sanity checker plugin" on the issues/ToDo list
[01:24:44] Leona (slmember1): May I add this conversation on the github website as a riminder?
[01:25:47] Grey Mars: Please do, I never remember. Perhaps also mention that a future feature to easily add a beauty blank space in the menus would be appreciated?

@LeonaMorro
Copy link
Member Author

This may also be releated to #32

@HowardBaxton
Copy link
Collaborator

In thinking a bit, there is a way to add a blank button to the menu. If .Change Menu Order will pick it up, then this one is covered.

Add a double colon in the NC name: BTN:Submenu::

@HowardBaxton
Copy link
Collaborator

The .Change Menu Order doesn't seem to pick up the double colon, I tested this.

@LeonaMorro
Copy link
Member Author

To be honest (without reading a single line of code):
A double colon at the end isn't covered by "naming convention" of a NC.
NCType:Path(separated by a colon):ButtonName
I see some ways that would be covered by the specification:

  1. BTN:Submenu: but I guess that this will also not find the way into the menu system. (This would be my favorit, because it straight-line follows the specification)

  2. BTN:Submenu: with one or more trailing blanks

  3. BTN:Submenu:A_KEYWORDfor example BTN:Submenu:BLANK

@HowardBaxton
Copy link
Collaborator

I attempted to use the double colon in .Change Menu Order with no luck. This little egg no longer works. I did however create a button with some not-so-noticable text.

BTN:SEQUENCES:<>
BTN:SEQUENCES:HOLD
BTN:SEQUENCES:--
BTN:SEQUENCES:RESUME
BTN:SEQUENCES:loopall
BTN:SEQUENCES:looplast
BTN:SEQUENCES:loopto

I vote we close this issue.

@LeonaMorro
Copy link
Member Author

Summary: there are ways to add (almost) blank buttons to nPose V2. In nPose V3 you may also use the Button Comments to achieve this (even if both isn't straightforward).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants