Thank you i did what i wanted to do

I'll get back to you on this @rdurbin and will pass on your comments.

@sys64738 the equation for pointing any direction based on a mid point x,y and an angle from straight up would be:

point = [] for i = 0 to 3 loop point[i]= {x + (length*sin(angle+(120*i))),y - (length*cos(angle+(120*i)))} repeat triangle (point[0],point[1],point[2],white,true)

Or at least something very similar.

@Martin Cheers for the stick update, the left stick and right stick press is exactly what I meant.
Ian

@kendog400 said in I'm interested in learning to program card game, any tips where I could start ?:

Its hard to any response from the Fuze Team

Although I'm not sure, I'm guessing by this you mean that your registration took a while to be approved, given this is your first post.

Please see this thread for more info on that process: https://fuzearena.com/forum/topic/24/community-approval-process

Particularly the 4th paragraph about our availability.

I've used that technique to Frankenstein two built-in sprite images together, so I can confirm that drawing a larger image onto a smaller one does work. Separate images is definitely the simpler solution, though.

Well done for sorting that one out by yourself, the team are spread a bit thin today!

@BarenDK said in Low level details of Fuze Basic:

floating point variables are not well suited for holding integer values. Strange results can occur, like 'x += 1 x -= 1'

It's loosely typed meaning things are automatically casted at the point of any operation. we don't store ints as floats for the same reason we don't store strings as ints.

There's no precision lost unless you cast things yourself to change the type too.

Saying that, if you can find an example of it not working as it should, please let me know so I can raise an issue internally for a future patch

Not yet! We're always looking at ways to improve the experience though.

Nevermind !
It was just a question, not a real need.

Oh yes !!
Thanks @MikeDX

I'll be working on adding this documentation to a future patch - it won't be in the one coming up, but the online help can and will be updated earlier.

I'd like to know more myself. I closest I got was something like: MovementX += (c.orientation[0][0] * c.velocity[0][0]) * speed

I tackle this differently (there's always more than one way to do stuff)

I maintain a 'debounce' struct. In the main loop I look for c.a == 1 and increment debounce.a. In the else (ie, the button is no longer pressed) I say if debounce.a > 0 then do whatever it was I wanted to do and also reset debounce.a to 0 ready for detecting the next keypress.

For me this solves the problem of only doing something once per press. If instead of performing an action on keyup you really do want keydown then you can say if debounce.a == 1 (or 2 or 3 or 10 or whatever you want). If you want auto repeat you can use debounce.a % 50 or something like that.

@poof92 I also shared the sample code now (as "Text Box Sample").

absolutely true here on many counts. the iteration is costly, the calculations are not.

we are already looking at ways to improve this!

I wasn't able to find a work around. If using Len() for something like for loops, I have to hard code the lengths in.

Thanks for the answer.
I will polish my game until the arrival of the fix, before sharing it.

sorry figured it out lolz

its not on the radar here but i can add it to the list for discussion