Announcement

Collapse
No announcement yet.

Suggestion for the next RR version (buffering of button presses)

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Suggestion for the next RR version (buffering of button presses)

    It seems that RoadRunner buffers the button presses. Found that out when I pressed a button to reach another (not preloaded) screen twice. The first button press loads the screen. The second button press isn't discarded, though. Instead the button press is executed on the target screen.

    Don't know how to describe it better. But IMO button presses on a screen shouldn't be carried to the next screen.

  • #2
    Button presses are really like any other command in RR. Generally, pressing a button in a screen is fast enough to where there's not enough time for you to press the same button again, and even if you can, the code in the button will generally execute the same command which will have no effect to load the same screen you're already in. The exception however goes to commands like EXIT/CANCEL/LASTSCR which execute based on the current screen -- in this specific case, there's a possibility for that to happen IF the command on the button pressed takes some time before executing the EXIT/CANCEL/LASTSCR command. Otherwise, you may be actually be clicking a button on THE NEW SCREEN already, which particularly may happen on screens that have the same button layout across different screens (and you can verify that by changing button positions to test). On quick tests I did here with the EXIT button, I was unable to press the same button on the same screen before/while transitioning, but when there was another exit button on the next screen, it could "look like" I was pressing the button on the previous screen, and I was actually pressing the button on the new screen -- and just by pressing on a different spot of the button I was able to confirm that, and was really unable to press the same button on the screen more than once.
    Ride Runner RR's Myspace

    "Being happy is not about having what you want, it's about wanting what you have."
    "The best things in life are always free - but that doesn't mean money can't buy you good things."

    Comment


    • #3
      Maybe he has super fast fiingers, or a really really slow pc..386? Both? :rolf:
      RideRunner...The #1 FE, PERIOD.

      Current Project: DFXVoice [v1.0 Released]
      Next in line: RRMedia v2.0

      DFX 5.1.1 Skin
      Appstore Link

      My RideRunner Plugins
      RRMedia
      RRExtended
      DFXVoice

      "There are no bugs - only undocumented features."

      Comment


      • #4
        ITX 900MHz board with 1GHz RAM.

        I have alot of screens which have buttons in the same positions. When the screen is not in preload, it takes 1-2 seconds to load a screen, though.

        I press a button on a screen two times. Because of the 1-2 seconds delay it takes a moment to load the next screen. RR then executes the second button press on the next screen. Which shouldn't happen IMO. This happens at a simple "LOAD;<whatever>.skin" command.

        I don't think RR should carry button presses to the next screen. Doesn't make sense to me. It should just execute the button presses for the screen you're actually seeing.

        I guess it isn't too difficult to purge the button-press-buffer when a new screen is shown, is it ? Definately makes sense to me, and doesn't do any harm (to anyone with a faster system).

        Originally posted by guino
        you may be actually be clicking a button on THE NEW SCREEN already
        Which would make sense to me if I could already see the next screen. But executing commands on a screen I'm NOT seeing isn't really useful.

        Comment


        • #5
          I think this is a problem with Windows. If I am in a screen and hit the mouse button twice realy fast it will do the same thing. Maybe they cache the mouse events. Don't know.

          Comment


          • #6
            @Konrad: Can you make a debug log and post it ? Just so you know, windows DOES buffer mouse events and keyboard events. Maybe you want to turn on your TouchScreen Beep or add a command to play some kind of sound when clicking the button to avoid clicking buttons twice. There's no effective way of avoid clicking of buttons -- RR just executes what windows sends as clicks -- as soon as it receives it.
            Ride Runner RR's Myspace

            "Being happy is not about having what you want, it's about wanting what you have."
            "The best things in life are always free - but that doesn't mean money can't buy you good things."

            Comment

            Working...
            X