-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File Path #11
Comments
Hi, @mole84 I expect to get path like the demo code on the README. https://github.com/thedoritos/unimgpicker/blob/master/README.md Could you provide more information? Such as...
Thank you. |
There is no error any more, but if I use your example (without changing something), and I ulpoad something from my C:/ it returns me the following path in Debug.Log: But i uploaded the file from "C:/" , so the path is wrong. How do i get the path with filename? by the way, the image is shown correctly on the cube. |
Thanks for the info. Currently, Unimgpicker doesn't have a feature to get the original image path. This is a security problem on iOS/Android. The path is abstracted on these platform and you can't read the file directly from the path. As a workaround, Unimgpicker copies the image to the app data directory where your app can read/write. I assume you want the original filename. If you really need it, I would try! But it seems that we have to switch the image picking framework (for iOS), and it'll take a little more than a few days. Thank you. |
Hi thedoritos, thank you for reply. Do you have an idea? |
Hi, @mole84 There is a workaround.
Note that the image Unimgpicker returns is not the original one. It is a copy as I mentioned above. And it may be downscaled according to the If you pass a large number, you may get a high quality copy but it probably causes an OutOfMemory error. Thank you. |
Hi thedoritos, how to copy the image?
|
I did it that way and it is working: `using UnityEngine; namespace Kakera
}` |
Hi,
how can I get the file path of the selected picture ? Its always the same path in the debug log
The text was updated successfully, but these errors were encountered: