I that a qube in the background? It might be a reflection you're seeing...

So my latest finding on this problem is that this seems to work fine:

oldc = controls(0) loop play() repeat function play() clear() c = controls(0) if c.a and !oldc.a then print("hello") endif update() oldc = c return void

I tested this and there are limits to fontsize when using the L/R buttons, but it appears that using the touch controls for fontsize gets around the limits!

I see, well thank you for updating me, I appreciate it.

@PB____ I don't believe there are any errors in my code, but it does a lot of swapping of data. It would previously in earlier builds of F4NS call the error of a stack overflow to a random line way out of scope (including a negative line), but more recent patches just have it crash the entire program instead. Technically speaking, it shouldn't crash at all, but developing a programming language is a bit more sophisticated because there are many different routes that could be taken by the end user that perhaps the programmers didn't take into account. Still, we're over 6 months since F4NS had been released, and this is one of the things that still plagues it.

So, this thread has two issues in it - but the one about creating images larger than the screen size is corrected in the next version. More specifically, the concept of being able to create an image that is 720 x 1280 (so vertical) and use native co-ordinates on it, then during the final render you rotate it and offset it giving you the ability to rotate the switch into vertical mode. That will be perfectly do-able in the next release.

Mind you, congrats on getting free memory down to 32MB. I had no idea that was possible as I've never seen it drop by much :)

It looks like a few things have wrong filenames in the search database, thanks for bringing it to our attention

@Dave wohooo, thank you so much! Let me know if I can be "even more"😁 helpful.

Yep, same here. good spot!

Ok, didn't find an existing report of it, good to know that there is awareness :)

Please note that the title may be misleading. Sometimes you get errors on random lines (I've seen that too). This is different from that. This is a specific and reproducible scenario. (I don't think this is the same bug as https://fuzearena.com/forum/topic/204/error-1180137048/2 for example)

@Retrocade_media I agree that it should be fixed.

I'd probably rate fixing the color picker as a "medium" priority bug-- not some kind of critical issue, but it does materially impact the use of the tool.

Plus, it's probably a really easy bug fix, so it might be one of those "low hanging fruit" situations.

@mario-bodemann Thanks for that I will get this changed

@Retrocade_media thanks for bringing this up. Will take a look.

Sorry I am not sure what you mean. Please could you do a screenshot