Clicking issue

[XbabylonX]

Hi,

I have a script with 2 states.

While in the default one and clicking the object leads to the second state where another clicking trigger leads back to the default one but the problem is that the latter works with 2 clicks and not with a single.

Any ideas why is this happening?

[ObviousAltIsObvious]

can only guess without seeing the script, but if you are switching states from inside a touch_start handler, don't do that because clicks can be lost.

the easiest workaround is to use touch_end when you need to change states on click.

[Ron Khondji]

It's a very old bug.
Something to do with touch_start event carrying over to the new state.
The sollution is to use touch_end events instead.

[steph Arnott]

Is it really needed to switch states?

[Nova Convair]

---

steph Arnott wrote:

Is it really needed to switch states?

---

It's a well known old bug. If you switch states you need to use touch_end.

 

[steph Arnott]

I meant does the OP really see the need to have two states rarther than just one. Added;: BTW Rolig Loon wrote this.

integer gON;default{    touch_start(integer num)    {        gON = !gON;  //  Here's the switch ...        if (gON)   //  So, let's test it ....        {            //  It's on.        }        else        {            //  It's not.        }    }}

[XbabylonX]

Touch end solved it!

Thank you a lot guys!

[Nova Convair]

Oh that - yes I never use states for this little things. For me that's just overhead.

I only use states if I need 2 different event handlers for the same event.

But thats a personal preference.