Timeline for Output each second
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 26, 2023 at 7:11 | comment | added | Dadsdy | Meta post posted | |
| Jun 26, 2023 at 7:04 | comment | added | Aiden Chow | @Dadsdy To be fair, while there is currently no consensus on scoring sliders (and many other things in Desmos, like graph settings, setting the colors of an expression, tables, and so on), you could potentially post a follow-up meta post of sorts to address these other cases, if you choose to. | |
| Jun 26, 2023 at 6:51 | comment | added | Dadsdy | That's fair. I just figured that since each slider is either running or not running, that would be one bit, and because there are four options for the slider that would be two bits, but yeah, I have no meta backing for those numbers. I just think that maybe using a running slider instead of a ticker could be promising. | |
| Jun 26, 2023 at 6:42 | comment | added | Aiden Chow | @Dadsdy How are you calculating that running a slider is one bit, and choosing a slider option is two more bits, and so on? I don't think any of these bit/byte measurements that you are coming up with have any meta consensus backing them up, while I am basing my byte calculations off of the meta post for scoring Desmos answers found here. Unless there is some kind of meta consensus regarding the scoring of sliders and such, I won't be changing my answer to include any of that. | |
| Jun 26, 2023 at 6:32 | comment | added | Dadsdy | You can do it with just a=0, a step of 1, and option 4 for the slider, and the slider running. Slider running is one bit, the four slider options are two more bits, step is one byte + one boundary byte, and a=0 is 3 more bytes (maybe + one boundary) for a total of 5.375 bytes or 6.375 bytes | |
| Jun 26, 2023 at 6:23 | history | answered | Aiden Chow | CC BY-SA 4.0 |