Moderators: seebs, franciscotufro
...
[ 11 ] = { x = 95, y = -305, char = "q" },
[ 12 ] = { x = 175, y = -305, char = "w" },
[ 13 ] = { x = 255, y = -305, char = "e" },
[ 14 ] = { x = 335, y = -305, char = "r" },
[ 15 ] = { x = 415, y = -305, char = "t" },
[ 16 ] = { x = 495, y = -305, char = "y" },
[ 17 ] = { x = 575, y = -305, char = "u" },
[ 18 ] = { x = 655, y = -305, char = "i" },
[ 19 ] = { x = 735, y = -305, char = "o" },
[ 20 ] = { x = 815, y = -305, char = "p" },
...
patrick wrote:Not yet. Soon(tm).
patrick wrote:
@Souledge Will aim to support native software keyboard within a month.
-
- function oniOSKeyInput ( start, length, text )
- print ( start, length, text )
- user_entered_text = MOAIKeyboardIOS.getText ()
- print ( user_entered_text )
- end
-
- function oniOSKeyReturn ()
- user_entered_text = MOAIKeyboardIOS.getText ()
- print ( user_entered_text )
- end
-
- if MOAIKeyboardIOS then
- MOAIKeyboardIOS.setListener ( MOAIKeyboardIOS.EVENT_INPUT, oniOSKeyInput )
- MOAIKeyboardIOS.setListener ( MOAIKeyboardIOS.EVENT_RETURN, oniOSKeyReturn )
- end
-
- -- for development on MacOSX
- if MOAIInputMgr.device.keyboard then
- MOAIInputMgr.device.keyboard:setCallback(onKeyboardEvent)
- end
-
ibisum wrote:I don't get it .. I'm already using MOAIKeyboardIOS.getText() .. is this not what you guys need too?
EDIT: Just noticed that this is only working on iOS, and not Android. Alas, MOAIKeyboardAndroid would be really nice to have as well ..
Users browsing this forum: Google [Bot], Google Feedfetcher and 0 guests