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
I have a stack that displays the symptom but am not sure of the bug that led to the state.
When opening the stack a JavaScript error message appears, saying "length mismatch, expected, got", and then the dimensions.
The text was updated successfully, but these errors were encountered:
My hunch is that Base64 encoding of (compressed) image data, using JavaScript's btoa() and atob() would be less fragile, if somewhat larger. This would also help a JSON saved stack file survive editing outside ViperCard.
The serialization is coming directly from the browser's JSON.serialize, and so I don't think that is the source of this problem. In the repro stack, the image data is valid and can be decompressed, but just has different dimensions than expected. A serialization problem would result in data that couldn't be decompressed.
Mentioned by erico on twitter.
I have a stack that displays the symptom but am not sure of the bug that led to the state.
When opening the stack a JavaScript error message appears, saying "length mismatch, expected, got", and then the dimensions.
The text was updated successfully, but these errors were encountered: