Andii

Member
  • Content count

    1
  • Joined

  • Last visited

Community Reputation

106 Neutral

About Andii

  • Rank
    Newbie
  1. The question is what is reported by the framework, not what does a keyboard have. A keyboard has physical keys, the framework reports key pressed/released state by so called raw keys via the Murl::Input::IRawKeyboardDevice interface. You are right, the RawKey enumeration is missing on the Web-Site (we are still in open beta phase), but the enumeration can be found in the corresponding header file which is typically used during development. On the other side every operating system does some kind of mapping a physical key to a localized character. Such a mapped character can be called vanilla key. The Murl::Input::IKeyboardDevice interface reports these characters and yes of course, these characters are UTF8 encoded, think about e.g. a korean keyboard. The framework do not report raw keys for non-physical keyboards e.g. touch screen keyboards on mobile devices.    The methods are documented and the keyboard support does work on all supported platforms.   In the order the keys are reported by the operating system (probably the order the keys are pressed). The strings are defined by the corresponding pressed key.   The framework simply provides exactly the same information on all supported platforms. Configuring arbitrary keys and other features are not supported by the framework. A sample code for using the IKeyboardDevice is available in the Tutorial section in Chapter02 Tutorial01.   Joystick support is currently not implemented in the framework's platform code. n the current stage the framework is focused on mobile platforms which do not support joysticks by default. The joystick interface is unfinished and prepared for supporting gaming consoles and pc in the future (the current interface is based on a N64 controller).