IMSDK
IM features a comprehensive suite of solutions including global access, one-to-one chat, group chat, message push, profile and relationship chain hosting, and account authentication. It also provides complete app access and backend management APIs.
V2TIMImageElem

Instance Methods

(V2TIMElem *) - nextElem
 
(void) - appendElem:
 

Properties

NSString * path
 
NSArray< V2TIMImage * > * imageList
 

Method Documentation

◆ nextElem()

- (V2TIMElem *) nextElem

Get the next Elem. If your message has multiple Elems, you can get the next Elem object from the current Elem. If the return value is nil, it means the Elem acquisition is over. For detailed usage, please refer to the document Message sending and receiving

◆ appendElem:()

- (void) appendElem: (V2TIMElem *)  elem

Add the next element
To configure multiple elements, after creating a Message object, you can add the next element via the element object of Message. The following is the sample code for creating V2TIMTextElem and V2TIMCustomElem:

    V2TIMMessage *msg = [[V2TIMManager sharedInstance] createTextMessage:"text"];
    V2TIMCustomElem *customElem = [[V2TIMCustomElem alloc] init];
    customElem.data = ["自定义消息" dataUsingEncoding:NSUTF8StringEncoding];
    [msg.textElem appendElem:customElem];
Attention
  • This API can be called only by elements of a Message object created via createMessage.
  • This API can be used to add V2TIMTextElem, V2TIMCustomElem, V2TIMFaceElem, or V2TIMLocationElem.

Property Documentation

◆ path

- (NSString*) path
readnonatomicstrong

Local file path of the original image. This is valid only for the message sender.

◆ imageList

- (NSArray<V2TIMImage *>*) imageList
readnonatomicstrong

When receiving a picture message, this field will save all the specifications of the picture. Currently, it contains at most three specifications: original picture, large picture, and thumbnail. Each specification is stored in a V2TIMImage object.