Error Question

[J2Kbr]

Cool. Glad to see a comment in favor of FFB prefix! I liked it as well. It is simple and short, like the LED prefix.

Each FFB have two parameters: force and duration. The force feedback "signal" from steering wheels can be converted to this same parameters.

[Prototype]

OK like that with two parameters it's perfect.

[pablosscripts]

set_val is the only IO function that accepts fix32 and int as values. If an int is provided, it internally converts to fix32. I did this to make easy use int values to set the outputs without use type cast, or be forced to use 32bits variables where it is not needed.

Could you please elaborate on this, for someone who is not a programmer?

Does that mean set_val is the only one that accepts values like this:

Code: Select all

set_val(button, 100)

While every other function requires you to cast it first, like this:

Code: Select all

if((int) get_val(BUTTON)) > 100)

Also in what scenarios would I use fix32 vs. int? Is it just a matter of more precision?

[J2Kbr]

You are correct in your examples. And also on the scenarios, a int -100 to 100 has "only" 200 points of resolution, on the other hand, a fix32 -in the same range- have 13,333,333 points of resolution. For regular buttons this should not make any difference, but in case of mouse translation the extra resolution will have a significant positive impact.

[pablosscripts]

thanks for clarifying!