You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
Users should have the option of not using this and just using the cached data to run the dialog.
The text was updated successfully, but these errors were encountered: