Historique de la page

Indicates whether any data items in a specified format are available among the data concerned by the current drag and drop operation. The format can be either one predefined in Windows or one defined by the developer.

Note: This method is not implemented in Java and Mobile generation.

Erases any data stored in the object that could have been used for a drag and drop operation.

This method concerns the data previously created by the DD_WRITE_DATA method.

Notes:This method is not implemented in Java and Mobile generation.

Initiates a drag and drop operation between a source object and a destination object using the data stored in the source object by the DD_WRITE_DATA method.

The relevant data can be either copied or moved to the destination object.

The set formed by this data is identified by a format name. The format can be either one predefined in Windows or one defined by the developer.

Note: Where a predefined format is used, only the first data item written by the DD_WRITE_DATA method is taken into consideration.

Notes: This method is not implemented in Java and Mobile generation.

Reads the data transferred as part of the current drag and drop operation. This data is in fact a copy of the data written in the source object by the DD_WRITE_DATA method.

This method must be used in a loop to run through all the data for a given Adelia type.

All the data for a given type is read when the number of data items read is less than the number of data items to be read.

Notes:

• • Calling this method with an Adelia array containing x elements has the same effect as calling the method x times with an Adelia variable.
  • If the DD_WRITE_DATA method has been used to write x records each containing two ALPHA variables, the DD_READ_DATA method must be run twice, with the indexes (2x - 1) and 2x, in order to retrieve the strings in the nth record, or once with the index (2x-1) and an array capable of receiving two data items.
  • No distinction is made between packed and extended numerical variables, however long they are and however many decimal places they have. The values of numerical and extended variables may be truncated when they are read. With strings, the read operation will fail if the Adelia variable is too small to contain the string being read.

Notes:

• • This method is not implemented by the Java generator.
  • It is not available in Mobile generation.

Adds data (i.e. the contents of the Adelia variables) to the data to be transferred by a drag and drop operation. This data is stored in the object until the end of the drag and drop operation, and is then deleted automatically.

Notes:

• • Calling this method with an array containing x elements has the same effect as calling the method x times with a variable containing the individual array elements.
  • No distinction is made between the extended and packed numerical data types.

Note: This method is not implemented in Java and Mobile generation.

Exports the graphic into a bitmap file in the requested format. If the format is not indicated (*BLANK), it is deduced from the file extension.

The possible file formats are the same as for the function VaToolBxSaveBitmapEx: BMP, PCX, PNG, PPM, PGM, PBM, JPEG, TGA, GIF, TIFF, MNG and JP2.

In Adelia Cloud generation the available file formats are restricted to BMP, PNG, JPG, TIFF and GIF.

Attention: if the graphic has been determined using the LOAD_IMAGE_FROM_URL method, the export will only succeed if the URL is not secure and is accessible from the Cloud application server.

Note: This method is not implemented in Java and Mobile generation.

Exports the graphic into an image variable. The variable will contain the image data in the requested format.

The possible file formats are the same as for the function VaToolBxSaveBitmapEx: BMP, PCX, PNG, PPM, PGM, PBM, JPEG, TGA, GIF, TIFF, MNG and JP2.

In Adelia Cloud generation the available file formats are restricted to BMP, PNG, JPG, TIFF and GIF.

Attention: if the graphic has been determined using the LOAD_IMAGE_FROM_URL method, the export will only succeed if the URL is not secure and is accessible from the Cloud application server.

Note: This method is not implemented in Java and Mobile generation.

Displays the graphic stored in a Bitmap file inside the object.

(The following extensions are supported for the Bitmap file: bmp, cut, emf, eps, ico, gif, iff, jpg, jp2, mng, pbm, pcx, pgm, png, ppm, psp, tif, tga and wmf. With the Adelia Mobile runtime, the only formats allowed are: bmp, gif, jpg, png and ico.)

Example >>

Displays the graphic stored in an image variable inside the object.

The image variable must be the content of a file containing an image.

The following image file extensions are supported: bmp, cut, emf, eps, ico, gif, iff, jpg, jp2, mng, pbm, pcx, pgm, png, ppm, psp, tif, tga, wmf.

In Adelia Cloud generation, the variable content may also be an image in DIB (Device Independent Bitmap) format.

Caution: In Windows generation, the Image variable may be, for example, the result of the VaToolBxFileToImage function but must not be the BITMAP property of an IMAGE object or the result of the VaToolBxLoadBitmap function.

Note: This method is not implemented in Java and Mobile generation.

Displays the graphic situated at the URL address inside the object.

The following image file extensions are supported: bmp, cut, emf, eps, ico, gif, iff, jpg, jp2, mng, pbm, pcx, pgm, png, ppm, psp, tif, tga, wmf.

Note: This method is not implemented in Java and Mobile generation.