MobileDeviceApplicationRun.ClipData
ClipData
Usage
Read and write.
Description
Type: MobileDeviceApplicationRunClipData, Undefined. Contains attached data related to this mobile application startup. Attached data in the startup is not used to refine the search for a mobile application. It is semantically similar to a property AdditionalData that is used to transfer additional data using MobileDeviceApplicationRun. The main difference of this property from the AdditionalData property is that the Intent.FLAG_GRANT_READ_URI_PERMISSION and Intent.FLAG_GRANT_WRITE_URI_PERMISSION system flags will be used for any items with references to resources included in attached data. These flags are always set to the MobileDeviceApplicationRun object. So, when you run a mobile application, you can transfer several references to resources with the "content:" schema, for which a recipient might not have a global permission to access the content vendor. If this property contains items that are the MobileDeviceApplicationRun objects, all set flags in these runs are ignored. Only flags of the main (top-level) {ссылка:Объекты; 2189; ЗапускПриложенияМобильногоУстройства} object are taken into account. They will be applied to all items with references to resources or to the MobileDeviceApplicationRun objects in AttachedData (or under AttachedData items). A MIME type, label, and icon in the AttachedData property are not used by the MobileDeviceApplicationRun object directly. In general, applications must take into account a MIME type of the MobileDeviceApplicationRun object, not attached data content. To transfer the MobileDeviceApplicationRun object, create the MobileDeviceApplicationRunClipData object with the "*/*" MIME type. It is similar to the setClipData and getClipData methods for the Intent class in Android.
Availability
Mobile client, mobile application (client).
Note
Default value: Undefined.
No comments to display
No comments to display