One click counts as two?

[kons]

Hi,

following problem:

On click on an object, I activate three zones to click in (I select a card in the game which appears a lot bigger to make the three clickable actions better to read). It might well be that the three clickable zones appear on the object. So if I click the card on a spot that will become a clickable zone, I immediately execute the action bound to the zone.

It seems that Fusion doesn't react on mouse button release (which is afaik normal), but really on the push.

I could workaround by making the actions on the clickable zones only happen on double-click, but that sucks from a user point of view.

Any hints on how to overcome that obstacle?

Thanks,

kons

[Decal]

You could try this:

---------------------
Only One action if the event loops +
Negate: Repeate while mouse button is pressed
---------------------

This should only activate when you release the mouse button

[King_Cool]

A 'on mouse click' Condition is true for the entire Game Frame/ the entire Event Editor, meaning if you have 'multiple Events' checking for mouse clicks, all those Events will trigger and not just one of them.
This can seems illogical and confusing, as you expect only 1 mose click to our at any given time.

There is also a noticeable "lag" in between each mouse click getting registered/ triggered ( meaning you can physicall press mouse button multiple times, but only a few of these will be registered.

...
What I like to do to bypass these problems is to make a Flag0 represent if mouse is clicked or not, and base mouse clicks on Flag0 instead of the 'on mouse clicks condition':

+ If mouse left is helt down
-> Set Flag0 ON

+ If mouse overlapping ObjX
+ Flag0 ON
-> Action
-> Set Flag0 OFF


+ If mouse overlapping ObjY
+ Flag0 ON
-> Action
-> Set Flag0 OFF

+ If mouse left is NOT helt down
-> Set Flag0 OFF

^ The above will bypass the click lag, and make sure only 1 mouse click is allowed for each Game Frame ( only 1 click will be registered on each iteration of the Event Editor List, so multiple 'on click' Events won't register simultaneously ).
Think of it as taking "manual controll" of the mouse input.

[Patrice]

Easy tips about that : https://www.dropbox.com/s/z2cp6gsbcw...pteur.mfa?dl=0

[kons]

Thanks all you guys for your input!

What first seemed unlogical from a user point of view (sometimes need only 1 click, sometimes 2) turned out as a feature: One click triggers always reversable actions (e. g. showing the content of the card) while double-clicking always triggers a non-reversable action (e. g. spending commodities or playing a card).

I still learned a lot about the behavior of Fusion, which is always great!

[casleziro]

King_Cool's method will work great.

Sometimes if your mouse is old or if your computer stutters/lags you can get double input a frame or so apart. A simple way to prevent this is to give your mouse (or each individual button) a cooldown timer that is always counting down, and don't register clicks until that timer = 0. I usually set each of my button timers to 5 on click. This is big enough to catch error inputs but small enough to be unnoticeable for rapid clicks.

A simple way to count down to 0 (and remain at 0 once it's reached, instead of going below it) is to use an Always event that sets each value or counter to:

Max(value of counter - 1, 0)

You can count up towards a value and not go beyond it also, using Min(value of counter + 1, target value).

Just some tips.