Add "TiledBackground destroy" to your "On Right Button clicked" event
After the name is entered - TextInput Set Unfocused. Or destroy.
This should in theory close the keyboard, but you need to test.
Have you tried unfocusing/destroying the text input?
Do you have this particles object on the layout? Create an empty layout "Assets" and move it there.
If it doesn't fix the problem, then the mistake must be in your events.
Run the project in Debug mode, check if there are double instances of these text objects. Maybe one is on a global layer.
newt This is a much better solution, thanks!
CurrentValue and "Compare current value" condition can only be used inside of "For each key" loop.
So to check if the dictionary has "apple" you need to do this:
Dictionary For each key Compare current value =carsOut.Text
I remember sending you a demo with this code:
It helps to prevent getting stuck in corners.
Also, you should not use "Wait" inside "Player is dirChange" event. If you change the direction quickly several times, delayed "waits" from previous direction changes will mess the things up. Use Timer behavior - restart the Timer on every direction change.
You can convert coordinates from layer B to A using these monstrous expressions:
CanvasToLayerX("A", LayerToCanvasX("B", x, y), LayerToCanvasY("B", x, y))
CanvasToLayerY("A", LayerToCanvasX("B", x, y), LayerToCanvasY("B", x, y))
Can you just add a constant variable? E=2.7182818284
You can set particles time scale to 10, wait a second and restore their time scale. To hide this initial stage, cover the whole screen with a black sprite with fade out behavior.
Develop games in your browser. Powerful, performant & highly capable.
I believe you can add a script to the webpage, and call methods in this script from construct game.
Here is a demo:
dropbox.com/s/1im9m3usr05vgqc/GunRecoil.capx
Simply compare LevelNumber=5 -> Go To Layout "DifferentCutscene"
Usually this is caused by the collision polygon or origin image point location on the enemy sprite. When it collides with the marker and turns, it immediately collides the second time and turns again. To avoid this issue, make sure the collision polygon is rectangular and origin point is in the middle.
Also, you can add a cooldown - for example, after turning, don't allow to turn again for 1 second. Use Timer behavior for this.