-
Notifications
You must be signed in to change notification settings - Fork 72
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
trigger_info dosen't work. please help me. #120
Comments
It seems this feature stopped working 2 years ago when I refactored the codebase. I used to keep a
If you wanna fix it and send a pull request: put the lines back in to |
sorry, I don't know where should i change codes in |
I just ran into this same issue - grepping to no avail where self._syntax is set (and it isn't!) |
Here is my workaround (in my code, not in the rivescript code), which is probably faster because it uses a dict instead of a loop:
Then I call my own load_directory after called the rs one, then I use it like:
|
In version 2.0.0 the trigger_info from the documentation doesn't work yet (it always returns null). And the example mentioned by the other user I don't understand how to apply it, the same with parser.py I can't understand it. However, in the play.rivescript.com if I set the debug mode I can read the path of the trigger. How do I achieve that in my application in Python? |
Fixed in #144. |
I used example code in ex3.py
i use ver.1.14.9
and this works like this.
So, My question is why trigger_info doen't work properly?
Please answer me thanks.
The text was updated successfully, but these errors were encountered: