1. 24 Aug, 2017 - 2 commits
    • Jarkko Koivikko's avatar
      Add Hebrew keyboard layout · fe6c501c
      Jarkko Koivikko authored
      
      [ChangeLog] Added Hebrew keyboard layout.
      
      Change-Id: I7779db4e5ac3c5a99937a0d7b7e572db65f0d811
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      fe6c501c
    • Jarkko Koivikko's avatar
      Clear toggle shift timer when appropriate · dc4e962f
      Jarkko Koivikko authored
      
      The timer in the ShiftHandler is used for detecting double
      click events for shift key. A double click event will trigger
      caps lock if the initial shift state is lower case.
      
      However, the implementation did not handle a case where
      the keyboard layout changes between the first and second
      press. This can be done with multitouch.
      
      The second problem was with the automatic test cases, where
      the test code toggles the shift to see if there is a secondary
      layout triggered by the shift key, e.g. in Arabic and Farsi.
      However, if the keyboard layout does not contain secondary
      layout, rapid shift state change will trigger caps lock
      instead. This issue was identified with certain test case for
      Hebrew layout.
      
      This change fixes the issue by clearing the shift toggle timer
      when the layout changes and in the automatic tests while
      checking for the secondary layout with the shift key.
      
      Also, update test code so that the shift press is simulated
      with mouse. This will ensure the key exists in the layout
      and that the key is enabled.
      
      Change-Id: I2a528f1b82c30e8b8d9746d380b32ee370b38004
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      dc4e962f
  2. 08 Jul, 2017 - 3 commits
  3. 05 May, 2017 - 1 commit
  4. 19 Dec, 2016 - 1 commit
  5. 25 Nov, 2016 - 1 commit
  6. 14 Oct, 2016 - 1 commit
  7. 13 Oct, 2016 - 1 commit
  8. 27 Sep, 2016 - 1 commit
    • Bramastyo Harimukti's avatar
      Implemented proper double click behavior of shift handler · e8b7dcea
      Bramastyo Harimukti authored
      
      Previously, there is nothing to separate whether the button
      command is a single click or a double click. Every time we
      click the shift button, it always look for the second click
      and always activate the caps lock. There is no time limit to
      specify if there will be a second click and always recognized
      the upcoming click to activate the caps lock. The correct be-
      havior of a shift button is that a single click is used to
      enable the upper-case and automatically turned into lower case
      when the next letter is typed. Another case, within a specific
      time, if a second click comes, the caps-lock is activated and
      keep the upper-case mode, otherwise the upcoming click is used
      to abort the upper-case and change the keyboard mode back to
      lower-case.
      
      Unit test is also updated.
      
      [ChangeLog] Changed behavior of shift handler to only activate
      caps lock if the shift key is double-clicked.
      
      Change-Id: Ia04a61ca6df5407f37eb73b9de65c6ccd0128547
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@qt.io>
      e8b7dcea
  9. 26 Apr, 2016 - 1 commit
  10. 12 Jan, 2016 - 1 commit
  11. 27 Nov, 2015 - 1 commit
  12. 28 Oct, 2015 - 1 commit
    • Jarkko Koivikko's avatar
      Refactor class names · 03e2a103
      Jarkko Koivikko authored
      
      Since the virtual keyboard C++ interface is wrapped inside a
      namespace, it is possible to get rid of "Declarative" name
      in the class names, that would otherwise conflict with the
      QML namespace in the documentation.
      
      - Rename DeclarativeSettings to VirtualKeyboardSettings
      - Remove "Declarative" from class names
      
      The rationale for this change is that the name Declarative
      refers to now obsolete QtQuick1 module. Also, the class names
      are now the same in C++ and QML name spaces.
      
      Change-Id: Ide050d47110443d894d95d35dddf0df5891587be
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@theqtcompany.com>
      03e2a103
  13. 27 Oct, 2015 - 2 commits
  14. 26 Oct, 2015 - 1 commit
  15. 15 Sep, 2015 - 1 commit
  16. 25 Feb, 2015 - 1 commit
    • Jarkko Koivikko's avatar
      Add OpenWnn implementation of JapaneseInputMethod · 506d877b
      Jarkko Koivikko authored
      
      This change implements Japanese input method. It supports
      Hiragana, Katakana and Kanjie.
      
      The OpenWnn library is imported from Google AOSP project.
      The wnnEngine library is ported from the Java sources. It
      provides full implementation of the engine, excluding
      learning and user dictionary capabilities.
      
      To activate the Japanese input method add CONFIG+=openwnn to
      qmake command line.
      
      Brief user guide:
      =================
      - The default input mode is Hiragana
      - To switch between Hiragana, Katakana, Latin and FullwidthLatin
        input modes, press the input mode toggle button in place of the
        left shift key.
      - Space key activates Hiragana to Kanjie conversion mode
      - Subsequent press on the space key cycles between the candidates
      - To select candidate, press return key, or any other input key
        to auto commit the result and to start with the new composition
      - To cancel the Kanjie conversion mode, press backspace key
      - The left and right arrow keys are used for exact matching mode
      - In exact matching mode, the arrow keys can modify the selection
        within the composing text, it is also possible to modify any part
        of the composing text in exact match mode
      - Pressing the space during the exact match mode starts Kanjie
        conversion for current selection
      
      Change-Id: I08d2496dba3506ba752f3537f9cf6939c803df6c
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@theqtcompany.com>
      506d877b
  17. 10 Feb, 2015 - 2 commits
    • Jarkko Koivikko's avatar
      Add HangulInputMethod for Korean language · 58c999d7
      Jarkko Koivikko authored
      
      This change adds support for Korean language. The keyboard layout
      is based on the standard Dubeolsik keyboard layout. The keyboard
      layout uses the Hangul Compatibility Jamo 3130-318F as the input
      characters.
      
      The Hangul composition and decomposition is implemented in the
      Hangul support class, and has the following key features:
       - Automatic detection of initial, medial and final Jamos
         based on the current syllable
       - Handles any Unicode input sequences, not just Hangul
       - Splitting and joining of double medial and double final Jamos
       - Splitting of double final consonant and joining with following
         vowel
      
      Added test cases that should cover most of the special cases
      in Hangul input.
      
      Change-Id: I5a6870407097bd1ce79bd2d00f81a30bd35a2f91
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@theqtcompany.com>
      58c999d7
    • Jarkko Koivikko's avatar
      Update shift state when the surrounding text changes · d2fad29c
      Jarkko Koivikko authored
      
      This change is needed by the Hangul input method.
      
      Without this change the shift state does not update when the
      certain characters (double final consonants from the second page
      of the Hangul keyboard) are entered.
      
      Change-Id: I116ff13b4a9a4a99990744eafdef9b60a5736e88
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@theqtcompany.com>
      d2fad29c
  18. 12 Jan, 2015 - 1 commit
  19. 06 Oct, 2014 - 1 commit
  20. 13 Aug, 2014 - 1 commit
    • Jarkko Koivikko's avatar
      Changes to shift state handling for certain languages · a3e56451
      Jarkko Koivikko authored
      
      Moved all shift handling logic into DeclarativeShiftHandler. The
      purpose of this change is to allow language specific exceptions to
      the shift handling logic.
      
      With certain languages (currently including Arabic, Persian and
      Hindi), the automatic shift handling is disabled. Also, the shift
      state can be toggled even if current input method hints does
      not allow it.
      
      This change frees the shift key state for other purposes, such as
      binding to an alternative layout.
      
      Change-Id: I1cd6f8684b461ca3eecb484ae307c7bc7c2d0d81
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@digia.com>
      a3e56451
  21. 23 Jun, 2014 - 1 commit
  22. 05 May, 2014 - 1 commit
  23. 02 May, 2014 - 1 commit
  24. 03 Feb, 2014 - 1 commit
  25. 28 Jan, 2014 - 2 commits
  26. 17 Dec, 2013 - 1 commit
  27. 16 Dec, 2013 - 1 commit
    • Jarkko Koivikko's avatar
      Add documentation (closes #16) · be81e535
      Jarkko Koivikko authored
      Added documentation covering the QML parts.
      
      Renamed the Introduction document as Technical Guide and
      added new document describing the deployment.
      
      Minor change for the style plugin API; added new common
      type for the SelectionListItem.
      be81e535
  28. 13 Dec, 2013 - 1 commit
  29. 29 Nov, 2013 - 1 commit