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 original function is always called. This isn't always desirable, and with compound hooks there is currently no easy way around this.
One solution may be to create a singleton object, NOOP (no-op) which, when returned, will indicate to pymhf that the original function shouldn't be called.
The documentation should indicate that this value will have a profound affect on the hook and potentially the entire state of the program being hooked, as a function not returning some value may have large consequences on the game and should only be used with care.
The text was updated successfully, but these errors were encountered:
Currently the original function is always called. This isn't always desirable, and with compound hooks there is currently no easy way around this.
One solution may be to create a singleton object,
NOOP
(no-op) which, when returned, will indicate to pymhf that the original function shouldn't be called.The documentation should indicate that this value will have a profound affect on the hook and potentially the entire state of the program being hooked, as a function not returning some value may have large consequences on the game and should only be used with care.
The text was updated successfully, but these errors were encountered: