Struct telbot_types::message::SendAnimation[][src]

pub struct SendAnimation {
Show 13 fields pub chat_id: ChatId, pub animation: InputFileVariant, pub duration: Option<u32>, pub width: Option<u32>, pub height: Option<u32>, pub thumb: Option<InputFileVariant>, pub caption: Option<String>, pub parse_mode: Option<ParseMode>, pub caption_entities: Option<Vec<MessageEntity>>, pub disable_notification: Option<bool>, pub reply_to_message_id: Option<i64>, pub allow_sending_without_reply: Option<bool>, pub reply_markup: Option<ReplyMarkup>,
}
Expand description

Use this method to send animation files (GIF or H.264/MPEG-4 AVC video without sound). On success, the sent Message is returned. Bots can currently send video files of up to 50 MB in size, this limit may be changed in the future.

Fields

chat_id: ChatId

Unique identifier for the target chat or username of the target channel (in the format @channelusername)

animation: InputFileVariant

Animation to send. Pass a file_id as String to send an animation that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a video from the Internet, or upload a new video using multipart/form-data. More info on Sending Files »

duration: Option<u32>

Duration of sent animation in seconds

width: Option<u32>

Animation width

height: Option<u32>

Animation height

thumb: Option<InputFileVariant>

Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail’s width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can’t be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>.

caption: Option<String>

Video caption (may also be used when resending videos by file_id), 0-1024 characters after entities parsing

parse_mode: Option<ParseMode>

Mode for parsing entities in the message text. See formatting options for more details.

caption_entities: Option<Vec<MessageEntity>>

List of special entities that appear in the caption, which can be specified instead of parse_mode

disable_notification: Option<bool>

Sends the message silently. Users will receive a notification with no sound.

reply_to_message_id: Option<i64>

If the message is a reply, ID of the original message

allow_sending_without_reply: Option<bool>

Pass True, if the message should be sent even if the specified replied-to message is not found

reply_markup: Option<ReplyMarkup>

Additional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.

Implementations

Create a new sendAnimation request

Set duration

Set width

Set height

Set thumbnail

Set caption

Set parse mode

Set caption entities

Add one entity

Disable notification

Reply to message

Allow sending message even if the replying message isn’t present

Set reply markup

Trait Implementations

Serialize this value into the given Serde serializer. Read more

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more

Immutably borrows from an owned value. Read more

Mutably borrows from an owned value. Read more

Performs the conversion.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.