-
Notifications
You must be signed in to change notification settings - Fork 474
include_callback_query_chat_id doesn't seem to care about what seeder evaluates #433
Comments
I don't understand what this means. Nothing in delegation pattern returns None, as far as I can see. Regardless, one message triggering more than one pattern is what my design allows. All patterns work independently. Your reported behavior is what is intended. I am happy to see |
sorry for how i phrased the question it's just that am still learning english. i thought seeder functions like
from the handle method of DelegatorBot, calculate_seed is called to calculate the id and if the id is |
I have the same problem... i think the OP misunderstood delegator for seeder My DelegatorBot have two include_callback_query_chat_id with per_chat_id_in with different ids in it and after a callback both respond creating one more thread beyond the first. Using Lover example: bot = telepot.DelegatorBot(TOKEN, [
include_callback_query_chat_id(
pave_event_space())(
per_chat_id_in([group1],types=['private','group']), create_open, Lover, timeout=10),
include_callback_query_chat_id(
pave_event_space())(
per_chat_id_in([group2],types=['private','group']), create_open, Lover, timeout=10),
]) The bot respond twice to the same group after a callback Could you help? |
i have this two classes. What i would like to know is why do both Handlers get activated to handle a callback query even though the seeder function of the second delegation pattern returns None. Is this normal behavior or am missing something?
sample output of one inline button press
That happens even though i would expect only ""Class A handler" to be printed out.
The text was updated successfully, but these errors were encountered: