after the first click, the system waits for a second before accepting the next click

Hi!

I'm making a puzzle game, which works by rotating square pieces by 90 degree.

I prepared a simple MMF project, which describes a problem.

Attachment 10393

At first everything looks OK. Square pieces seems to rotate as they should. But after a while player becomes more experienced and would like to speed up the game play by rotating pieces quicker (so he starts to clicking faster).

And then became quite annoying that after the first click, you will need to wait almost a second before the computer will accept the next click.

I know this doesn't look like a big problem, but after a several thousands clicks it became very noticeable and the game play became less fluent (and game looks poorly programmed).

I'm not sure if I explained well, so please download MFA file to see what I mean.

You will notice that the squares rotates much faster if you are moving mouse cursor slightly while quickly clicking (or when you quickly clicking at a different squares). So the problem doesn't occur when you moving the mouse! The pause accrues "only" between two clicks at the same spot.

I believe this has something to do with a double click (system needs to wait a second for a second click on the same spot). I was hoping that problem would be less noticeable on iOS since it's hard to tap at the exactly same spot twice in a row. But unfortunately the problem exists there also.

I'm sure some of more experienced user has already noticed (and solved) this problem. I would really appreciate any solution or idea or brainstorming how to solve this.

Thanks in advance :-)

Dušan

I changed a MFA project a little. Now the problem is more obvious.

Try this:
1. click as fast as you can at the same spot (without moving the mouse)
2. click as fast as you can while moving mouse (that's why I make objects a little bigger)

You will notice that the click response is much faster in the second case.

This is a partial solution. Very simple and obvious. Unfortunately it works good in this case, but I cannot implement it in my- slightly more complicated game :-(

I think you need to test for double click too... the second click in rapid succession registers as a double click and is ignored by single click.

Ryan, from my experience with "rapid clicking" double click acts very similar as a single click.
- With single click every second click is ignored (to be sure that it's not a double click)
- while with double click the first click is "ignored".

so in both ways one click is "wasted" :-)

I tried, but just cannot find a way to use them together...

This seems to be the best approach to detect both a single click and rapid clicks:

* User clicks with left button
OR
* Repeat while left mouse-key is pressed
+ Only one action when event loops

Popcorn, thank you very much! Works like a charm! This is exactly what I need.

I owe you one! :-)

Quote:

---

Originally Posted by Popcorn

This seems to be the best approach to detect both a single click and rapid clicks:

* User clicks with left button
OR
* Repeat while left mouse-key is pressed
+ Only one action when event loops

---

Wouldn't that result in detecting 'OnMouseDown'? Click only occurs when the mouse button comes back up.

I've always used

* User clicks with left button
OR
* User double clicks with left button

I've had no problems doing it that way.

Quote:

---

Originally Posted by Ryan

Wouldn't that result in detecting 'OnMouseDown'? Click only occurs when the mouse button comes back up.

---

No, it does indeed do the job.

Quote:

---

Originally Posted by Ryan

I've always used

* User clicks with left button
OR
* User double clicks with left button

I've had no problems doing it that way.

---

Thanks for the tip, sounds like that would do the job as well :)

Thank you both for the solutions.
I'm attaching both versions (maybe could help someone in the future). They work almost identically in this simple project.

You're right, they're identical... i don't know why I thought click requires mouse down & up... probably confusing it with Javascript which has a seperate OnClick, OnMouseDown and OnMouseUp events.