It's basically do whatever you want, all there is is convention and personal preference. Lua itself doesn't care where you define your functions or your classes.T-Bone wrote:Perhaps a tutorial on proper usage of multiple .lua files would be nice. All my knowledge comes from trial and error, and asking people on the forums here, and every once in a while I notice large gaps in my knowledge
Code: Select all
joystick = class:new()
function joystick:init()
self.pressed = {}
self.password = 1
end
function joystick:update(dt)
self.password = (self.password % 2) + 1 -- change the password each update, for use in cleaning
for j=0, love.joystick.getNumJoysticks() do
for h=0, love.joystick.getNumHats(j) do
local direction = love.joystick.getHat(j, h)
if direction ~= "" and direction ~= "c" then
local key = "j"..j.."_h"..h.."_d"..direction
self:check(key)
end
end
for a=0, love.joystick.getNumAxes(j) do
local direction = love.joystick.getAxis(j, a)
if direction > .5 or direction < -.5 then
direction = round(direction) -- to keep it even between sticks and buttons
local key = "j"..j.."_a"..a.."_d"..direction
self:check(key)
end
end
end
for key, value in pairs(self.pressed) do -- clean out hats that aren't being pressed any more
if self.pressed[key] ~= self.password then
self.pressed[key] = nil
end
end
end
function joystick:check(key)
if self.pressed[key] == nil then
scene:keypressed(key)
end
self.pressed[key] = self.password
end
Imho if you want to handle Input correctly, then you should keep it more abstract, ie. handle keyboard, mouse and gamepad input in one separate class which can be accessed independently from you main loop/input function. Something like if InputManager:isActionButtonPressed() then and so on.tentus wrote:It pains me to post such inelegant code. Does anyone have some good code that they could put up as examples on the wiki?
Input is handled based on which scene (gamestate) you're in. For example, the character select screen has a very different set of bindings than the main game, which is very different from the nogame screen. Within the scenes some of the input is passed on to specific objects based on relevance (for example, if a key or joystick is bound to a player control, the input is passed onto that player object).XQYZ wrote:Imho if you want to handle Input correctly, then you should keep it more abstract, ie. handle keyboard, mouse and gamepad input in one separate class which can be accessed independently from you main loop/input function. Something like if InputManager:isActionButtonPressed() then and so on.tentus wrote:It pains me to post such inelegant code. Does anyone have some good code that they could put up as examples on the wiki?