Allocation

The Allocation will be used as the source of shader constants by one or more programs. This was deprecated in API level 16.

The Allocation will be used as a target for offscreen rendering This was deprecated in API level 16.

The Allocation will be used as a texture source by one or more graphics programs.

The Allocation will be used as a graphics mesh. This was deprecated in API level 16.

The Allocation will be used as a SurfaceTexture consumer. This usage will cause the Allocation to be created as read-only.

The Allocation will be used as a SurfaceTexture producer. The dimensions and format of the SurfaceTexture will be forced to those of the Allocation.

The Allocation will be bound to and accessed by scripts.

The Allocation's backing store will be inherited from another object (usually a Bitmap); copying to or from the original source Bitmap will cause a synchronization rather than a full copy. syncAll(int) may also be used to synchronize the Allocation and the source Bitmap.

This is set by default for allocations created with createFromBitmap(RenderScript, Bitmap) in API version 18 and higher.

Copy an array into part of this Allocation. This variant is type checked and will generate exceptions if the Allocation type is not a 32 bit float type.

Copy part of an Allocation into this Allocation.

Copy an array into part of this Allocation. This variant is type checked and will generate exceptions if the Allocation type is not a 16 bit integer type.

Copy an array into part of this Allocation. This variant is type checked and will generate exceptions if the Allocation type is not a 32 bit integer type.

Copy an array into part of this Allocation. This variant is type checked and will generate exceptions if the Allocation type is not an 8 bit integer type.

Copy an array into part of this Allocation. This method does not guarantee that the Allocation is compatible with the input buffer.

Copy an array into part of this Allocation. This method does not guarantee that the Allocation is compatible with the input buffer.

Copy an array into part of this Allocation. This method does not guarantee that the Allocation is compatible with the input buffer.

Copy an array into part of this Allocation. This method does not guarantee that the Allocation is compatible with the input buffer.

Copy from an array into a rectangular region in this Allocation. The array is assumed to be tightly packed.

Copy from an array into a rectangular region in this Allocation. The array is assumed to be tightly packed.

Copy from an array into a rectangular region in this Allocation. The array is assumed to be tightly packed.

Copy from an array into a rectangular region in this Allocation. The array is assumed to be tightly packed.

Copy a Bitmap into an Allocation. The height and width of the update will use the height and width of the Bitmap.

Copy a rectangular region from an Allocation into a rectangular region in this Allocation.

Copy an array of RS objects to the Allocation.

Copy into this Allocation from an array. This variant is type checked and will generate exceptions if the Allocation's Element is not an 8 bit integer type.

Copy an Allocation from an Allocation. The types of both allocations must be identical.

Copy into this Allocation from an array. This variant is type checked and will generate exceptions if the Allocation's Element is not a 32 bit integer type.

Copy into this Allocation from an array. This variant is type checked and will generate exceptions if the Allocation's Element is not a 32 bit float type.

Copy into an Allocation from a Bitmap. The height, width, and format of the bitmap must match the existing allocation.

If the Bitmap is the same as the Bitmap used to create the Allocation with createFromBitmap(RenderScript, Bitmap) and USAGE_SHARED is set on the Allocation, this will synchronize the Allocation with the latest data from the Bitmap, potentially avoiding the actual copy.

Copy into this Allocation from an array. This variant is type checked and will generate exceptions if the Allocation's Element is not a 16 bit integer type.

Copy into this Allocation from an array. This method does not guarantee that the Allocation is compatible with the input buffer; it copies memory without reinterpretation.

Copy into this Allocation from an array. This method does not guarantee that the Allocation is compatible with the input buffer; it copies memory without reinterpretation.

Copy into this Allocation from an array. This method does not guarantee that the Allocation is compatible with the input buffer; it copies memory without reinterpretation.

Copy into this Allocation from an array. This method does not guarantee that the Allocation is compatible with the input buffer; it copies memory without reinterpretation.

Copy from the Allocation into a byte array. The array must be at least as large as the Allocation. The allocation must be of an 8 bit integer Element type.

Copy from the Allocation into a int array. The array must be at least as large as the Allocation. The allocation must be of an 32 bit integer Element type.

Copy from the Allocation into a float array. The array must be at least as large as the Allocation. The allocation must be of an 32 bit float Element type.

Copy from the Allocation into a short array. The array must be at least as large as the Allocation. The allocation must be of an 16 bit integer Element type.

Copy from the Allocation into a Bitmap. The bitmap must match the dimensions of the Allocation.

Creates a cubemap Allocation from a Bitmap containing the horizontal list of cube faces. Each face must be a square, have the same size as all other faces, and have a width that is a power of 2.

Creates a non-mipmapped cubemap Allocation for use as a graphics texture from a Bitmap containing the horizontal list of cube faces. Each face must be a square, have the same size as all other faces, and have a width that is a power of 2.

Creates a non-mipmapped cubemap Allocation for use as a sampler input from 6 Bitmap objects containing the cube faces. Each face must be a square, have the same size as all other faces, and have a width that is a power of 2.

Creates a cubemap Allocation from 6 Bitmap objects containing the cube faces. Each face must be a square, have the same size as all other faces, and have a width that is a power of 2.

Creates an Allocation from a Bitmap.

With target API version 18 or greater, this Allocation will be created with USAGE_SHARED, USAGE_SCRIPT, and USAGE_GRAPHICS_TEXTURE. With target API version 17 or lower, this Allocation will be created with USAGE_GRAPHICS_TEXTURE.

Creates an Allocation from a Bitmap.

Creates a non-mipmapped Allocation to use as a graphics texture from the Bitmap referenced by resource ID.

With target API version 18 or greater, this allocation will be created with USAGE_SCRIPT and USAGE_GRAPHICS_TEXTURE. With target API version 17 or lower, this allocation will be created with USAGE_GRAPHICS_TEXTURE.

Creates an Allocation from the Bitmap referenced by resource ID.

Creates an Allocation containing string data encoded in UTF-8 format.

Creates an Allocation with a specified number of given elements

Creates an Allocation with a specified number of given elements

Creates an Allocation for use by scripts with a given Type and no mipmaps

Creates an Allocation with the size specified by the type and no mipmaps generated by default

Creates a new Allocation with the given Type, mipmap flag, and usage flags.

Generate a mipmap chain. This is only valid if the Type of the Allocation includes mipmaps.

This function will generate a complete set of mipmaps from the top level LOD and place them into the script memory space.

If the Allocation is also using other memory spaces, a call to syncAll(Allocation.USAGE_SCRIPT) is required.

Get the size of the Allocation in bytes.

Get the Element of the Type of the Allocation.

Returns the handle to a raw buffer that is being managed by the screen compositor. This operation is only valid for Allocations with USAGE_IO_INPUT.

Get the Type of the Allocation.

Get the usage flags of the Allocation.

Receive the latest input into the Allocation. This operation is only valid if USAGE_IO_INPUT is set on the Allocation.

Send a buffer to the output stream. The contents of the Allocation will be undefined after this operation. This operation is only valid if USAGE_IO_OUTPUT is set on the Allocation.

Resize a 1D allocation. The contents of the allocation are preserved. If new elements are allocated objects are created with null contents and the new region is otherwise undefined.

If the new region is smaller the references of any objects outside the new region will be released.

A new type will be created with the new dimension.

This is only intended to be used by auto-generated code reflected from the RenderScript script files and should not be used by developers.

This is only intended to be used by auto-generated code reflected from the RenderScript script files.

Set a notification handler for USAGE_IO_INPUT.

Associate a Surface with this Allocation. This operation is only valid for Allocations with USAGE_IO_OUTPUT.

Propagate changes from one usage of the Allocation to the other usages of the Allocation.

Invoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.

Note that objects that override finalize are significantly more expensive than objects that don't. Finalizers may be run a long time after the object is no longer reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup. Note also that finalizers are run on a single VM-wide finalizer thread, so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary for a class that has a native peer and needs to call a native method to destroy that peer. Even then, it's better to provide an explicit close method (and implement Closeable), and insist that callers manually dispose of instances. This works well for something like files, but less well for something like a BigInteger where typical calling code would have to deal with lots of temporaries. Unfortunately, code that creates lots of temporaries is the worst kind of code from the point of view of the single finalizer thread.

If you must use finalizers, consider at least providing your own ReferenceQueue and having your own thread process that queue.

Unlike constructors, finalizers are not automatically chained. You are responsible for calling super.finalize() yourself.

Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.