Disable key repeat?

[Tjakka5]

Sounds like a problems with your code, not with the limitations of the callbacks.
Working around your problems will only cause more problems in the long run, so I'd suggest you fix them.

Having multiple actions bound to one key is possible, but you must establish a priority.
That is, if you press up your priority is to enter a room. If that's not possible, you can jump.

Code: Select all

function player.keypressed(key)
  if key == "up" then
    if not player.tryEnterRoom() then
      if not player.tryJump() then
        -- If we aren't allowed to jump for whatever reason we may want to try a different action
      end
    end
  end
end

Besides that, you should not base your game's behavior around keypressed repeating. The delay between repeats can differ from os to os, and may even be customized in some environments.
If you want your player to be able to be constantly jumping while holding the up key, you should instead be using love.keyboard.isDown.

Last but not least, to fix your "defining multiple callbacks" problem, you want to propagate events if they are not satisfied.
For example, when you click on screen you first want to tell your UI code there was a keypress.
It will return true if it "used" it, or false if it didn't click on anything.
If it returns false you can then propagate it to the next system, and the next and the next.

Code: Select all

function love.mousepressed(...)
  if not menu.mousepressed(...) then
    if not player.mousepressed(...) then
      -- Etc
    end
  end
end

Again you're dealing with priorities here.


Hope that helps!

[raidho36]

My input library (see signature) supports "wasDown" function which returns "true" or "false" if the key was depressed or released on the previous frame.

[grump]

I can't have two love.keypressed functions at the same as one cancels out the other.

In my app framework, I'm using a multiplexing event dispatcher. There is only one place that receives all LÖVE events, as usual. Client code can subscribe to events, and the dispatcher notifies the subscribers of an event in the order they were registered. Each subscriber decides if it wants to consume the event or let it propagate further. Once it was consumed, propagation stops. There can be an unlimited number of subscribers for any kind of event.

It's an implementation of the so-called observer pattern.

[hasen]

It's extremely strange to only have love.keyboard.isDown...where's isUp?? It's like having a boolean with only false as a choice.

[zorg]

It's extremely strange to only have love.keyboard.isDown...where's isUp?? It's like having a boolean with only false as a choice.

Yes, because you can't do something like

Code: Select all

if not love.keyboard.isDown(key) then end

right?

Boolean logic functions don't need unnecessary complement functions, although feel free to implement it yourself if your needs are so paramount

Code: Select all

function love.keyboard.isUp(...)
    return not love.keyboard.isDown(...)
end

[hasen]

By isUp I obviously meant key released. Detecting if the keyboard is not down would detect what happens the entire game apart from when the key is down...

I was just remarking that the other languages I used they all had several stage IF checks for the keyboard presses. So I found it strange that love2d was missing all that. It's like boolean only having false ie incomplete...not that it's literally like boolean.

[raidho36]

LÖVE mainly handles input via events, the "isDown" is for quick and dirty hacks mid-development and you shouldn't rely on it.

[zorg]

By isUp I obviously meant key released. Detecting if the keyboard is not down would detect what happens the entire game apart from when the key is down...

I was just remarking that the other languages I used they all had several stage IF checks for the keyboard presses. So I found it strange that love2d was missing all that. It's like boolean only having false ie incomplete...not that it's literally like boolean.

Yeah, you use keypressed and keyreleased for that, as was stated before. Or you whip up your own solution, as was also stated before.

[hasen]

Yeah, you use keypressed and keyreleased for that, as was stated before. Or you whip up your own solution, as was also stated before.

Yes you have to use a function which grabs all at once since there are no IF checks for anything other than for keyisdown. Or you can make it yourself like you say or use someone else's library. That's the great thing, you can always make up for stuff that's missing.

[hasen]

LÖVE mainly handles input via events, the "isDown" is for quick and dirty hacks mid-development and you shouldn't rely on it.

I don't know, I see that the most in other people's finished source code. It's even used in Mari0 the most well known Love2d game.