03-18-2010, 05:24 PM
My mouse script (and a couple other mice scripts) only attach themselves to the INPUT module and don't interfere with the use of a Joypad. So rather than just have RMXP (or vx) work with just the keyboard and controller, you get keyboard, controller and mouse.
So I got a question. Why hasn't anyone just 'aliased' the press and trigger statements in the INPUT module? Every dang INPUT script out there just rewrites the sucker and kicks the Joypad outta there. Why not just add the new button codes to press? and trigger?
Oh, and I don't mean to replace "Input.trigger?(Input::C)" that controls the [space/enter] key, but use "Input.trigger?(Keys::C)" for the letter [C] and "Input.trigger?(Input::C)" as the default.
Hell yeah... I'm gonna look into this...
So I got a question. Why hasn't anyone just 'aliased' the press and trigger statements in the INPUT module? Every dang INPUT script out there just rewrites the sucker and kicks the Joypad outta there. Why not just add the new button codes to press? and trigger?
Oh, and I don't mean to replace "Input.trigger?(Input::C)" that controls the [space/enter] key, but use "Input.trigger?(Keys::C)" for the letter [C] and "Input.trigger?(Input::C)" as the default.
Hell yeah... I'm gonna look into this...