idk, but wasn't the limit 10mb?
If so, why is it letting me save over 10mb?
(10mb = 10000kb)
maybe it's 10 mib instead of 10 mb?
It's probably not exactly 10 mib (10 * 2^20), but it's right around there, and I think we allowed a tiny bit of extra just to make sure nothing unexpectedly is blocked.
I dont get it 10102 kb is 10.102 mb so it is letting him save over 10 mb. And is snap supposed to switch from saying kb to mb after a certain kb number?
I think the absolute maximum is 10200 kb, or 10.2 mb.
I think it's good to know that there is actually a different storage unit called a mebibyte (not a megabyte), which is what @cycomachead mentioned in his post (mib). It isn't exactly just kb / 1000. A mebibyte is actually 1048576 bytes or 2^{20}. I'm pretty sure this what snap is using to measure file sizes rather than just regular megabytes.
No, I can confirm that in the editor, if you try to save something over the limit, it says "10 mb", not "10 mib".
Alright, I've looked at the source code to verify everything.
Snap checks to see if the project is over (10 * 1024 * 1024) (10485760) bytes, or 10 MIB.
What it shows in the message is (project_size_in_bytes / 1024), which is in KIB, not KB (despite what it says).
Your project is actually less than 10 MIB because 10 MIB = 10240 KIB, and your project is 10102 KIB, so it's perfectly valid.
Basically, snap is showing KB even though it's calculating KIB, same with what it says is the max file size. I don't blame snap for doing this though, windows does this as well, it says KB when it's really calculating KIB.
Yes, while it's a little teeny bit "inaccurate" no one distinguishes between the two in common language, and often, people who do know something about computers assume a kilo/mega SI prefixes are just "renamed" versions of of 2^10 rather than actual powers of 10... To the extent anyone cares about the specific number of bytes, I do think KiB would be more confusing to even more users.
I mean, it wasn't in 1999 there was even an attempt at standardizing things, LOL.
I agree, but I had to explain what is actually going on to clear up the confusion the OP had.
I know about a mebibyte bust snap doesn’t use that because in the edited it switches from kb to mb not mib. And snap wont let you save over 10 MB not 10 mib.
Since you clearly don't understand
Here's the specific parts of the snap code that show that it is indeed MIB, not MB.
Just because snap says it's MB doesn't mean that it is MB, because what snap says is literally just static text. Heck, I could change it to say that the max is 10 bytes and it wouldn't change anything.
Oh so sorry i didnt see that post i just was barely reading the first sentence of every post and read the full thing if it replayed to me. Sorry
I get it now.
Also to be very clear, this is all just JS...which you can edit and mess with yourself. (But then you'd get different server errors.)
We tell people it's a megabyte because that's the term most users are comfortable with. The message in kb is I think is a bit old, but gives more detail in case you are trying trim down space.
Isn’t it morphic JS?
That's the javascript framework that jens made for snap, morphic.js is written in javascript so you can do anything that you can do in javascript.
I do know what morphic.js is.
Morphic is a library for JavaScript - much like, say, the "Iteration, composition" library in Snap!. Using the "Iteration, composition" library does not stop it from being Snap! - and, in fact, not all of your code will be made out of blocks from the library. Similarly, while Snap! is built off of Morphic, not all of the code involved is necessarily - or even likely - to be using functions provided by the library.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.