I want to "draw" a sound graph out of the audio being played in my game. In order to achieve this, I want to use the method described in this post https://www.construct.net but I don't seem to find any audio expression to get the loudness of the audio being currently played .

Thank you in advance! :)

ivall I don't understand what you mean. If you are looking for alternatives to PhoneGap, you could use Cordova CLI (for experts) or Cocoon.io. I never used any of them, so I couldn't help you if you wanted to test them.

You need to sign your APK with your Android keystore in order to publish to Google Play. Otherwise, PhoneGap creates a "Debugging APK" which cannot be submitted to the Play Store.

Hi Nandynho! How are you going?

Sorry that I answer that late, I've been very busy... Yes, if you right click the input, nothing happens, no contextmenu is shown at all! This happens in Chrome and NW.js preview as well as in Android apk.

I guess it's this part of the code in "sweetalert2.js":

  document.body.appendChild(sweetContainer);
  $("#sweetalert2").bind('contextmenu', function(e){ return false; });
[/code:1nntjdbl]
but I don't know how to change this.

Hi Nandynho!

Do you know why there is no "Copy" and "Paste" option in SweetAlert inputs? This option simply doesn't appear!

BTW, do you recommend switching to your new Sweet Alert II Plugin? It looks amazing!

You're right, I didn't think of that. This isn't a bug, so I'm closing the topic. It's only that I felt I was being ignored which annoyed me. Everything cleared

I solved it!!! You have to put "touch-action: none;" in the HTML element's style properties. Anyway, I still think this is a Construct 2 bug and I'm really angry because Scirra didn't even read my bug report (and they had time). Now that I know how easy the solution is, I'm sure they could have found it very quickly (and I needed about 20 days and very much research on other forums). But they didn't even answer, and it's very frustrating.

Please Scirra, could you take a look at it? I'm holding an update for my app because I need this issue to be solved.

Please Scirra don't quit Construct 2 support... The last time Scirra answered a C2 bug report was already 13 days ago...

Problem Description

If you touch an HTML element and move your finger, condition "Touch -> Is in touch" becomes false.

Attach a Capx

capx

Description of Capx

There is a Text Box (HTML element) and the touch Plugin, so you can test it yourself.

Steps to Reproduce Bug

• Run the project in Chrome
• Hit F12 (developer tools)
• Hit Ctrl + Shift + M (to simulate touch on a mobile phone)

Observed Result

"Is in touch" becomes false although you are still touching.

Expected Result

"Is in touch" should be true.

Affected Browsers

• Chrome: (YES)
• Android Devices: (YES)

Operating System and Service Pack

Windows 10

Construct 2 Version ID

r246 beta release

Now I'm really clueless. This is the problem (you don't need neither the capx posted above nor any Plugin): in my Project, there is an HTML element. If you touch that HTML element, everything is fine as long as you don't move your finger. At the moment you move your finger just one pixel, "Touch -> Is in touch" condition will stop triggering, and I need this to be true (because it actually is!).

If you want to check this by yourself, you can do it with TextBoxes or Buttons (as they both are HTML elements too): put a big TextBox and a black sprite next to it. If "Touch -> Is in touch" -> "Sprite -> Rotate 1 degree clockwise". You will notice the sprite will stop rotating as soon as you move your finger in the TextBox area. You can simulate touches in Chrome by hitting F12 and then Ctrl + Shift + M, otherwise you won't see the bug.

Is there any walkaround or do I have to report it as a bug?

Thank you for your help!

Ok after many tests I figured out that the problem is that JavaScript touch events have preference over Construct 2 touch events (which I don't understand, as Construct 2 is JavaScript!). Is there any way to avoid this "preference"?

If you disable pointer-events, you can swipe as expected, but then you can't scroll or touch any button inside the HTML element... Any clue?