You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while creating a new image(ui.resource.image) using the constructor, it is given in the documentation that the source can be either a url or a base64 encoded uri(url {string} —A URL or a base64 encoded image string.) .
This is working as expected in the browser(tested with both local file path and with base64 encoded image string). But when trying to load the image using a base64 encoded image uri(actually a screen shot of the screen captured using the line( GC.app.__root._ctx.canvas.toDataURL();) it takes the content(base64 encoded image string) as the path to load instead of considering it as data (IN ANDROID DEVICE).
I am also unable to save the screen shot(base64 data) in to local disk as a file.Is there a workaround to load actual data in to image object in NATIVE ANDROID.
The text was updated successfully, but these errors were encountered:
jeeva1803
changed the title
ui.resource.image not working as given in documentation in native android
ui.resource.image not loading base64 data in native android
Mar 16, 2015
while creating a new image(ui.resource.image) using the constructor, it is given in the documentation that the source can be either a url or a base64 encoded uri(url {string} —A URL or a base64 encoded image string.) .
This is working as expected in the browser(tested with both local file path and with base64 encoded image string). But when trying to load the image using a base64 encoded image uri(actually a screen shot of the screen captured using the line( GC.app.__root._ctx.canvas.toDataURL();) it takes the content(base64 encoded image string) as the path to load instead of considering it as data (IN ANDROID DEVICE).
I am also unable to save the screen shot(base64 data) in to local disk as a file.Is there a workaround to load actual data in to image object in NATIVE ANDROID.
The text was updated successfully, but these errors were encountered: