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
Currently, when a user imports an OBF board that contains embedded images, we save those images in the cloud and we replace the tile image by a reference to the file in the cloud. That affects to the offline users as the cloud images won't be displayed.
The initial solution would be to simply keep embedded images in such format data:image/... but I am open to any other suggestion.
The text was updated successfully, but these errors were encountered:
This commit updates the export logic to use an ObjectId as an image
identifier and to solve two issues:
1. We no longer have an extremely long id when the `image` property
is a data URI like `data:image/png;base64,iVBORw0K`.
2. We now have consistent image ids between `manifest.json` and the
OBF files, as required by the Open Board Format.
Currently, when a user imports an OBF board that contains embedded images, we save those images in the cloud and we replace the tile image by a reference to the file in the cloud. That affects to the offline users as the cloud images won't be displayed.
The initial solution would be to simply keep embedded images in such format
data:image/...
but I am open to any other suggestion.The text was updated successfully, but these errors were encountered: