This is odd, on startup, I am getting a SDL_TEXTEDITING event and SDL_StartTextInput() isn’t even called yet, since I didn’t make a routine that calls SDL_StartTextInput() yet.
So, why is this event being fired?
This is with SDL git head at 2287c7b03 from the git mirror https://github.com/spurious/SDL-mirror.git
Code:
event {type=770 common={type=770 timestamp=332 } window={type=770 timestamp=332 windowID=1 ...} ...} SDL_Event
type 770 unsigned int
This is odd, on startup, I am getting a SDL_TEXTEDITING event and SDL_StartTextInput() isn’t even called yet, since I didn’t make a routine that calls SDL_StartTextInput() yet.
That seems correct on desktop OS with a fixed keyboard.
StartTextInput is only for touch screens, to popup the keyboard
to tap on.
[It might also do something to enable input of complex
foreign code points such as Chinese, using some specialised
input method, even on a desktop]On 27/02/2015, at 3:56 PM, Sparks wrote:
Text input is enabled by default on desktop OS’.> On Feb 27, 2015, at 12:56 AM, Sparks wrote:
This is odd, on startup, I am getting a SDL_TEXTEDITING event and SDL_StartTextInput() isn’t even called yet, since I didn’t make a routine that calls SDL_StartTextInput() yet.
So, why is this event being fired?
This is with SDL git head at 2287c7b03 from the git mirror https://github.com/spurious/SDL-mirror.githttps://github.com/spurious/SDL-mirror.git
Code:
event {type=770 common={type=770 timestamp=332 } window={type=770 timestamp=332 windowID=1 ...} ...} SDL_Event
type 770 unsigned int
[It might also do something to enable input of complex
foreign code points such as Chinese, using some specialised
input method, even on a desktop]
Yep, IME input doesn’t work at all when text input isn’t enabled (and
handling this properly is important, because when it’s enabled then
you won’t get keypress events for the letters since they’re being
captured by the IME!).