U hS5@sdddlZddlZddlmZmZmZddlmZddlm Z m Z ddl m Z eGdd d eZ dS) N) EventBuilder EventCommonname_inner_event)utils)types functions) SenderGettercsVeZdZdZd dddddfdd ZedddZd d ZGd d d ee Z Z S) CallbackQuerya Occurs whenever you sign in as a bot and a user clicks one of the inline buttons on your messages. Note that the `chats` parameter will **not** work with normal IDs or peers if the clicked inline button comes from a "via bot" message. The `chats` parameter also supports checking against the `chat_instance` which should be used for inline callbacks. Args: data (`bytes`, `str`, `callable`, optional): If set, the inline button payload data must match this data. A UTF-8 string can also be given, a regex or a callable. For instance, to check against ``'data_1'`` and ``'data_2'`` you can use ``re.compile(b'data_')``. pattern (`bytes`, `str`, `callable`, `Pattern`, optional): If set, only buttons with payload matching this pattern will be handled. You can specify a regex-like string which will be matched against the payload data, a callable function that returns `True` if a the payload data is acceptable, or a compiled regex pattern. Example .. code-block:: python from telethon import events, Button # Handle all callback queries and check data inside the handler @client.on(events.CallbackQuery) async def handler(event): if event.data == b'yes': await event.answer('Correct answer!') # Handle only callback queries with data being b'no' @client.on(events.CallbackQuery(data=b'no')) async def handler(event): # Pop-up message with alert await event.answer('Wrong answer!', alert=True) # Send a message with buttons users can click async def main(): await client.send_message(user, 'Yes or no?', buttons=[ Button.inline('Yes!', b'yes'), Button.inline('Nope', b'no') ]) NF)blacklist_chatsfuncdatapatterncstj|||d|r"|r"tdt|tr6|d}t|trJ|d}|rR|n|}t|trx|rh|n t|j |_ nj|rt |r||_ nVt |drt |j rtt |ddtst|j d|jtj@}|j |_ ntdtdd |j|j|j fD|_dS) N)r r z*Only pass either data or pattern not both.zutf-8matchrz"Invalid data or pattern type givencss|]}|dkVqdSN).0xrrA/tmp/pip-unpacked-wheel-c81u5j2r/telethon/events/callbackquery.py Usz)CallbackQuery.__init__..)super__init__ ValueError isinstancestrencodebytesrecompilercallablehasattrgetattrrflagsUNICODE TypeErrorallchatsr _no_check)selfr(r r rrr __class__rrr:s0         zCallbackQuery.__init__cCsvt|tjr|||j|jSt|tjrrtdt d|jj \}}|dkrZt | nt |}||||SdS)Nz`, since the message object is normally not present. N) rOr\r]rZrr:r/rInputBotInlineMessageIDInputBotInlineMessageID64Z edit_messagerNr_rrredit+s"  zCallbackQuery.Event.editcs\|jj|t|jjtjtj fr0t d|jj | IdH|jjgf||IdHS)a Deletes the message. Shorthand for `telethon.client.messages.MessageMethods.delete_messages` with ``entity`` and ``message_ids`` already set. If you need to delete more than one message at once, don't use this `delete` method. Use a `telethon.client.telegramclient.TelegramClient` instance directly. This method also creates a task to `answer` the callback. This method will likely fail if `via_inline` is `True`. zOInline messages cannot be deleted as there is no API request available to do soN) rOr\r]rZrr:r/rrdrer&Zdelete_messagesrNr_rrrdeleteFs zCallbackQuery.Event.delete)Nr)__name__ __module__ __qualname____doc__rrBpropertyr4rLrr;rPrTrZr[rbrcrfrg __classcell__rrr+rr-~s2      $ r-)N)NN) rhrirjrkr classmethodr9r?rr r-rmrrr+rr s/ r )rr1commonrrrrtlrr Ztl.custom.sendergetterr r rrrrs