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

Event Callbacks #1

Closed
squattingmonk opened this issue Jan 2, 2019 · 1 comment
Closed

Event Callbacks #1

squattingmonk opened this issue Jan 2, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@squattingmonk
Copy link
Owner

Currently, the system is set up so that all the information about the dialog is cached at initialization. After this, other scripts are only run if there are conditions or actions on the nodes or pages. I can envision instances where this could be too constricting, especially if you want to add or delete node lists on the fly.

A callback to the dialog script could be sent for several events:

  • dialog init
  • page init
  • node condition
  • node action
  • end
  • abort

Users should have the option of not using this and just using the cached data to run the dialog.

@squattingmonk squattingmonk added the enhancement New feature or request label Jan 2, 2019
@squattingmonk squattingmonk self-assigned this Jan 2, 2019
This was referenced Jan 2, 2019
@squattingmonk
Copy link
Owner Author

Closed with 80d5eb0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant