Author Topic: Button spamming.  (Read 1750 times)

Offline hortino

  • byte
  • *
  • Posts: 42
    • View Profile
Button spamming.
« on: March 06, 2012, 10:50:56 PM »
Sorry, i dont mean to spam the boards, but I just experienced a quite frustrating issue. Playing Mario party 3 Minigames sometimes requires you to repeatedly press a button in usual to gain momentum or speed, but I've noticed that only so many touches are  recognized in a given amount of time. Is this simply the nature of a touch screen, or is it an issue with the app only recognizing inputs that are at least "t seconds" apart? I suspect it's not  app but the lack of physical buttons. But in the case it is the app i feel like this would be good to know.

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Button spamming.
« Reply #1 on: March 07, 2012, 02:16:16 PM »
In a way it is the app's fault.  By pegging the CPU to run the processor-hungry emulator, threads that handle input often find themselves sleeping longer than usual, which limits the number of events that can be registered in a given amount of time.  As the emulator is better optimized, it won't be as CPU-intensive, and this problem should improve over time.  Additionally, I am adding a "turbo" feature to buttons at some point in the near future, which could be used in cases where rapid button-pressing is necessary.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted