There's a bug with Multiple Touch object where "A new touch on object has started" gives a "double click" on a string, I didn't tested on my device but it happens on Windows runtime.
Printable View
There's a bug with Multiple Touch object where "A new touch on object has started" gives a "double click" on a string, I didn't tested on my device but it happens on Windows runtime.
Does child events has been changed? I have a lot of issues with child events not triggering correctly in this version, for example, this event trigger only one of both actions:
Code:* NOT mask_spartan-foe animation Disappearing is playing
+ Enemy life of mask_spartan-foe <= 0
+ Pick one of mask_spartan-foe
mask_spartan-foe : Set Flag 10 off
mask_spartan-foe : Change animation sequence to Disappearing
+ Killed by of mask_spartan-foe = 0
counters_all : Add 1 to medals_multikills
counters_all : Add 1 to medals_killingspree
counters_all : Add 1 to ct_frags
+ val_gamemode <> 16
OR
+ val_gamemode = 16
+ zombie round of counters_all = 0
+ set_team = 2
OR
+ val_gamemode = 16
+ zombie round of counters_all = 2
+ set_team = 2
OR
+ val_gamemode = 16
+ zombie round of counters_all = 1
+ set_team = 1
counters_all : Add 10 to ct_xp
check-xp : Subtract 10 from Counter
Seems not to be related to this build as reverting to 293.5 or 293.1 doesn't change anything. (or the MFA is broken?)
But if i let the child event with its OR it trigger only the last action of the list. If i remove the OR, it trigger both actions.
I've fpound the issue, here is a MFA that reproduce it:
Attachment 30395
Pressing SPACE BAR should add 1 to counter 2 and add 1 to Alterable Value O of Active 2.
The add 1 to Alterable Value O of Active 2 action is ignored.
My bad, just figured out it was the normal behavior of OR when adding an object in the condition. As it scope for this particular object and ignore it if is not scoped in one of the OR. (case of my example)
So i should use "OR (logical)" here to make the example to work.
PS: why is the 'edit post' button still missing?
Another bug on mobile: Set position of Layer causes touch/mouse input to be misaligned. I'm not sure if this also happens with set Scrolling.
so far you should understand that values are megabyte of memory, you can get more information in gradle documentation https://docs.gradle.org/current/user...ing_jvm_memory