Please see the announcements category for information about the issue with sharing

https://fuzearena.com/forum/topic/442/issue-with-shares

I believe this was fixed in this most recent patch. Yay!

I don't think i've ever plugged headphones into my switch so you're not alone :D

This is already a known issue but thanks for reporting it.

I stumbled across it early on because I am used to adding JavaDoc to programs.

The only way the multiline comments work at the moment is if the end is simply */

So this will work:

/***** * * */

But this will not:

/**** * * ****/

Thank you - we'll look into this!

Hi @Nisse5, thanks for the report. This is a known issue resulting from "tan" being both a function as well as a color constant. It's on our to-do list!

Hi @SenteDescin, thanks for your report. I've looked into this and you are correct, the time parameter is not being used correctly in this case. It is indeed using the default delta time instead. A fix for this will be released in a future patch!

As you mentioned, it's possible to work around this for now by calling the list version of updateSprites or the singular updateSprite. I've verified that those use the supplied time parameter properly.

updateSprites(my_sprite_list, speed) updateSprite(sprite, speed)

Thank you for the report!

Thanks for reporting - this is a known bug that has already been fixed in the next release.

No the report here is correct. The documentation is incorrect and it should say it is a counter from 0 to 9 and not 0 to 10

@turtleStew said in true/false=1/0 not explained:

that's true (hehehe) in most languages. In some, I think C too, a boolean type takes a whole byte of memory so all the bits are dedicated to it. If a boolean is true, then all bits are high, the opposite is true if it's false. Using an integer value to represent this also works; just make it 0 or >0. However, signed integers can also be used to return negative values which are less than zero. This is often used to tell if an error occurred. But why use boolean types anyways? I think the best reasons to do so involve making the code somewhat more readable when there's no need for error handling

that's how it works in c, flase is only produced by 0, all the other values are considered true, even with signed values, but some other languages implements boolean types using enumarative types or custom classes, that's to give more restrictive and specifiec usages to boolean types, or just to optimize the compilers for the usage of those values

I agree, may be something like that : http://codyssea.com/downloads/f4ns/joystick.png ?

'You should change the while loop too so the program stops when you reach a certain number of sweets.'
==> so the loop exits when you reach a certain number of sweets
(the program will stop later)