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

registerAnonymousEventHandler isn't obvious in GUI #2762

Closed
Kebap opened this issue Jul 11, 2019 · 3 comments
Closed

registerAnonymousEventHandler isn't obvious in GUI #2762

Kebap opened this issue Jul 11, 2019 · 3 comments

Comments

@Kebap
Copy link
Contributor

Kebap commented Jul 11, 2019

Brief summary of issue / Description of requested feature:

Status created via Lua should be reflected in GUI somehow

Steps to reproduce the issue / Reasons for adding feature:

  1. lua registerAnonymousEventHandler("my event", "my function")
  2. Whenever my event occurs, my function will be called. All is fine.
  3. There is no indication of said connection in the GUI nor a way to remove it without Lua

Error output / Expected result of feature

  1. The event should be listed at the function's script code, where it can be removed with -

Extra information, such as Mudlet version, operating system and ideas for how to solve / implement:

Problem is, all functions can be registered to an event via Lua, but in GUI only those functions can be, which have a same name as their parenting script. Also functions may be defined in other items than a "script", and triggers, aliases, etc. don't even list registered events at all.

@SlySven
Copy link
Member

SlySven commented Jul 12, 2019

I think that is one reason for the "Anonymous" in the Lua API function name. 😜

TBH I do not have any experience with this function as I always create my Event handlers in the (Script) Editor so I am not really in a position to comment...

@vadi2
Copy link
Member

vadi2 commented Jul 13, 2019

That is exactly the reason.

@vadi2
Copy link
Member

vadi2 commented Jul 13, 2019

Closing as it's working exactly as intended and nobody's having a problem with this as far as I know of.

@vadi2 vadi2 closed this as completed Jul 13, 2019
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

3 participants