Sessions (screen.h)

A window is used to display different types of content.

Input sessions allow applications to control how raw events are processed into higher level events.

Logical input events are encapsulated by input sessions. An example of such input is text entry in a text field. A session is created upon getting input focus in a text field and is destroyed when input focus is lost. Even though some sessions can be created once and last for the lifetime of the application, Screen API considers the sessions active until they are destroyed.

Sessions are created with a specific session type by calling the screen_create_session_type() function. Valid session types are:
  • SCREEN_EVENT_KEYBOARD
  • SCREEN_EVENT_POINTER
  • SCREEN_EVENT_JOYSTICK
  • SCREEN_EVENT_GAMEPAD
  • SCREEN_EVENT_MTOUCH_TOUCH
  • SCREEN_EVENT_JOG

Last modified: 2014-05-14



Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus