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
With 10.0 giving us the gift of automated API documentation for script object APIs, it'd be helpful if this were additionally extended to also document the signatures of script handlers such as OnHyperlinkEnter or OnTextChanged.
Currently, the only reliable way for us to determine what arguments are supplied to script handlers is through inspection of an debuglocals dump within a replaced global error handler.
As an example, given the following XML and Lua fragments we can use the debuglocals API to determine the names of the parameters generated for an OnHyperlinkEnter XML script handler chunk. While this will get us the magic names of parameters within generated XML script handlers, we can't automatically infer typing information for the individual parameters.
With 10.0 giving us the gift of automated API documentation for script object APIs, it'd be helpful if this were additionally extended to also document the signatures of script handlers such as OnHyperlinkEnter or OnTextChanged.
Currently, the only reliable way for us to determine what arguments are supplied to script handlers is through inspection of an debuglocals dump within a replaced global error handler.
As an example, given the following XML and Lua fragments we can use the debuglocals API to determine the names of the parameters generated for an OnHyperlinkEnter XML script handler chunk. While this will get us the magic names of parameters within generated XML script handlers, we can't automatically infer typing information for the individual parameters.
This would output the following:
The text was updated successfully, but these errors were encountered: