This commit brings partial keyboard support to the library.
It exposes new events to the API
CHIAKI_EVENT_KEYBOARD_OPEN, indicates that the console opened the keyboard. It includes the current text buffer.
CHIAKI_EVENT_KEYBOARD_TEXT_CHANGE, indicates that the console changed the text or the text was confirmed.
CHIAKI_EVENT_KEYBOARD_REMOTE_CLOSE, indicates a console keyboard close event. So far happened when the keyboard was opened and the Home button was pressed (sent via API).
The keyboard feature must be enabled by sending a couple of packets. These packets are not fully identified yet and this PR does not add a setting to Chiaki API yet to make this really optional as it should be.
To implement this API in GUI the following steps are required:
Use new events (open, text change, remote close) to track current Keyboard state in GUI.
Use chiaki_session_keyboard_set_text to change text.
Use chiaki_session_keyboard_accept to confirm keyboard editing. (enter)
Use chiaki_session_keyboard_reject to cancel keyboard editing. (escape)
This commit brings partial keyboard support to the library.
It exposes new events to the API
CHIAKI_EVENT_KEYBOARD_OPEN, indicates that the console opened the keyboard. It includes the current text buffer.CHIAKI_EVENT_KEYBOARD_TEXT_CHANGE, indicates that the console changed the text or the text was confirmed.CHIAKI_EVENT_KEYBOARD_REMOTE_CLOSE, indicates a console keyboard close event. So far happened when the keyboard was opened and the Home button was pressed (sent via API).The keyboard feature must be enabled by sending a couple of packets. These packets are not fully identified yet and this PR does not add a setting to Chiaki API yet to make this really optional as it should be.
To implement this API in GUI the following steps are required:
chiaki_session_keyboard_set_textto change text.chiaki_session_keyboard_acceptto confirm keyboard editing. (enter)chiaki_session_keyboard_rejectto cancel keyboard editing. (escape)