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

menuOnSit issue with seat button permissions against root menu #88

Open
HowardBaxton opened this issue Aug 24, 2016 · 1 comment
Open

Comments

@HowardBaxton
Copy link
Collaborator

Turn on menuOnSit and add a notecard named BTN{1}. When someone sits in seat 1, we would expect to receive the menu but they don't.

In V2.01, I've found that in AssignSlots() the menu request from the core is sent before the SeatUpdate. The effect is that the menu script does not yet know there is a new sitter and button permissions fail. I am working on the AssignSlots() function in the core to fix and completely understand this.

In Alpha V0.53c the menu does not even run the DOMENU so it isn't even getting to the button permissions before it fails.

Further details as troubleshooting progresses.

@HowardBaxton
Copy link
Collaborator Author

The above description of what's happening is correct. My fix in the core was at fault. I now understand the issue completely and works for both versions of the core.

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