I have added 2 new features to the package and improved the documentation using CustomNavigator (because I had to read the code to understand how it worked).
First feature - resize the image based on its dominant axis.
I would like to change image size but rather than choose width or height, I will let the image size decide based on its dominant axis. Currently, if width set to 1024, and the image is portrait, the result will be 1024 x some number > 1024. If the image is landscape, the result will be 1024 x some number < 1024. This change ensures that 1024 will be applied to the largest dimension, thus the other dimension will always be smaller.
Second feature - select items that were previously selected.
The Settings optionally takes an array of items already selected and AssetsSelector selects those items (assuming they are found). The items are identified based on Asset.id. The client is responsible for saving the ids and passing them in on subsequent calls. It's common users will change their selection and they should be able to pick up where they left off instead of starting over.
I have added 2 new features to the package and improved the documentation using CustomNavigator (because I had to read the code to understand how it worked).
First feature - resize the image based on its dominant axis.
I would like to change image size but rather than choose width or height, I will let the image size decide based on its dominant axis. Currently, if width set to 1024, and the image is portrait, the result will be 1024 x some number > 1024. If the image is landscape, the result will be 1024 x some number < 1024. This change ensures that 1024 will be applied to the largest dimension, thus the other dimension will always be smaller.
Second feature - select items that were previously selected.
The Settings optionally takes an array of items already selected and AssetsSelector selects those items (assuming they are found). The items are identified based on Asset.id. The client is responsible for saving the ids and passing them in on subsequent calls. It's common users will change their selection and they should be able to pick up where they left off instead of starting over.