Touch Event fires on both pressed and released

Hey everyone,

There seems to be some weird issue with toggles on touch screens, when using a touch display ( laptop and stand alone display tested, not mobile ) a single touch turns this toggle on and then back off. The video below shows what is happening, interestingly when the button is held down for an amount of time ( right click ) it only fires once. Which is what should be happening on a tap as well.

Video of issue: UE4 Touchscreen Error - YouTube

Attempted Fixes:

  • Turned off / on Click Events in
    PlayerController
  • Turned off / on Touch Events in
    PlayerController
  • Turned off / on Touch Over Events in
    PlayerController
  • Set Touch 1 as a Click Event
  • Turned On / Off 'Use Mouse for Touch"

Please let me know if you have any other ideas!

Hello HaxO,

I was unable to reproduce your issue on our end, I have a couple of questions that will help me narrow down the issue you are experiencing.

  1. Are you able to reproduce your issue in a new project?
  2. If so could you provide a detailed list of steps so I can reproduce your issue on our end?
  3. Could you provide screenshots of your UI that is causing the issue?

Thanks!

I cannot reproduce it in a new project either, guess I messed something up on the way.

Here are the settings of the toggle in the video. Will get more info up here soon.

Could you also post screenshots of your Widget’s event graph & any other blueprints that use these buttons? This would help me investigate your issue further.

Yes, sorry to not be very responsive. Will get to this asap.

Alright, sorry about that. Here is the blueprint that is called when the Secondary_T toggle is pressed:

Maybe it is because the Primary_T and Secondary_T can turn each other off, that is somehow counting as an OnCheckStateChange Event for the touchscreen but not for clicks?

I was still not able to reproduce your issue on our end. To investigate further, I would need to see your project, which you can privately message me on the forums here:

Thanks!

After a couple more days of trying to debug this I settled for just brute forcing it. With this macro the toggle is disabled for 0.2 seconds then re-enabled, solving the issue.

If it’s dumb and it works, it isn’t dumb. Right? right?!>!?!

I’m having this exact same issue. Have you ever figured out a better solution?

No, had to just go with this and move onto other things.