These APIs are useful for other infrastructures, for example, acquiring extra reference
count for MlImage. However,
an App developer should avoid using the following APIs.
APIs inside are treated as internal APIs which are subject to change.
Acquires a reference on this MlImage.
This will increase the reference count by 1.
This method is more useful for image consumer to acquire a reference so image
resource will not be closed accidentally. As image creator, normal developer doesn't
need to call this method.
The reference count is 1 when MlImage is
created. Developer can call MlImage.close()
to indicate it doesn't need this MlImage
anymore.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-31 UTC."],[],["`MlImage.Internal` provides advanced, internal APIs for managing `MlImage` objects. It's advised that app developers avoid these APIs due to their potential to change. The key action is `acquire()`, which increments the reference count of an `MlImage`, preventing accidental closure of image resources. When an `MlImage` is created the reference count is 1. Developers should use `MlImage.close()` to release the image when finished. This `acquire` is useful for image consumers.\n"]]
