That takes up (2,048 * 10) / 100,000 = 20,480 / 100,000 = ~20% memory.
Plus the added effort of renaming every one.
That takes up (2,048 * 10) / 100,000 = 20,480 / 100,000 = ~20% memory.
Plus the added effort of renaming every one.
See?
Not unfeasable!
Yeah, 20% is a reasonable amount in this case, and there are sincere people on the Wix willing to help. Just add settings for the first property and copy that (11 copies)
Truly, this is the bad ending.
So this would work… but the block code limit strikes again
So these numbers store the data for my display, but they still have to be decrypted and turned into emojis. My current system for this is at 75/75 blocks, and adding another trigger to finish computing will cause the display to severely lag. (Like 30 seconds to render 4 rows).
What if you rename them?
oh shoot, I need 250+ properties JUST for the display
It says “property devices”, so I’m guessing renaming doesn’t matter.
224 for storing the data and and more for decrypting the data.
750 property limit would be really nice…
also get nolted lol
I know. I use these quite often when I want to turn something off after use.
Yeah, I thought this was very complex, and that is what the tag is for. I don’t think anyone will be solving this anytime soon.
Also there’s a max of 128 which makes this much, much harder.
Upon further reserach, I have found the following equations for bitwise operators:
The creator of the equations also said that “…I could not find any mathematical way of performing these operations without the use of modulus, floors, ceilings and the sequential additions.”
So, I’m not entirely sure if it’s even possible to remove the addsum now.