1. 02 Jun, 2016 - 1 commit
    • Mitch Curtis's avatar
      Fix path to lipi cfg file · c27fbe28
      Mitch Curtis authored
      
      It was using
      
      qtbase/lipi_toolkit/projects/lipiengine.cfg
      
      but it should be
      
      qtbase/qtvirtualkeyboard/lipi_toolkit/projects/lipiengine.cfg
      
      Change-Id: Ib8a7fe62739c23470e536ac25e16483df499a1a6
      Task-number: QTBUG-53366
      Reviewed-by: default avatarSamuli Piippo <samuli.piippo@qt.io>
      c27fbe28
  2. 26 May, 2016 - 1 commit
  3. 15 May, 2016 - 1 commit
    • Jarkko Koivikko's avatar
      Fix lipi plugin install location · e99680e6
      Jarkko Koivikko authored
      
      Installing plugins into a data path is a very bad idea, even more so
      when the path disagrees with the non-prefix location.
      
      The default LIPI_ROOT contains both the plugins and the projects needed
      at runtime for handwriting recognition. This change adds new environment
      variable LIPI_LIB which points to location for plugins only. This allows
      the separation of the two.
      
      Change-Id: Ie50b6871b6d176b2d06ff068743b40e9daa2c5cb
      Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
      e99680e6
  4. 13 Apr, 2016 - 1 commit
  5. 17 Mar, 2016 - 1 commit
  6. 12 Jan, 2016 - 1 commit
  7. 27 Oct, 2015 - 1 commit
    • Jarkko Koivikko's avatar
      Wrap C++ API into namespace · 751caffc
      Jarkko Koivikko authored
      
      This change wraps the entire C++ API into namespace.
      
      In practice, all the C++ interfaces inside the qtvirtualkeyboard plugin
      are private, except the QPlatformInputContext plugin API. Even the
      AbstractInputMethod and AbstractInputPanel are not really a public in
      the sense that they could be used outside the plugin. At least it does
      not make sense, since there is no way to extend the virtual keyboard
      functionality without recompiling the plugin.
      
      Task-number: QTRD-3628
      Change-Id: I1037ee247abca3219efeaa4e4150baaff7c3d668
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@theqtcompany.com>
      751caffc
  8. 26 Oct, 2015 - 1 commit
  9. 15 Sep, 2015 - 1 commit
  10. 27 Aug, 2015 - 3 commits
    • Rainer Keller's avatar
      Fix useless error message · 1da76c8d
      Rainer Keller authored
      
      The error message
      
      "Error 1: Error code is not set"
      
      has no useful information in this case. LTKLinuxUtil::loadSharedLib does
      only return the values FAILURE or SUCCESS. No useful error text can be
      displayed from that.
      
      Change-Id: Ic1e00ad6a68dd14eddbe7e103a37190643b75270
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@theqtcompany.com>
      Reviewed-by: default avatarJarkko Koivikko <jarkko.koivikko@code-q.fi>
      1da76c8d
    • Rainer Keller's avatar
      Allow LIPI_ROOT to be overridden · 6c0c174b
      Rainer Keller authored
      
      This is needed in order to use HWR from a different path.
      
      Change-Id: If836dda550defd42e7ca7067a788e0d917787dd1
      Reviewed-by: default avatarJarkko Koivikko <jarkko.koivikko@code-q.fi>
      6c0c174b
    • Jarkko Koivikko's avatar
      Run lipi HWR task in parallel with the recognition timer · 2ca10dd4
      Jarkko Koivikko authored
      
      This change improves the user experience by reducing the time
      spent waiting the HWR task to complete.
      
      Previously the recognition was started after the recognition
      timer expired. This caused the total overhead of the recognition
      to be summed on top of the recognition timer, reducing the user
      experience in low performance devices. Now the idle time (during
      the recognition timer) is used for the benefit of HWR task, so that
      in optimal case, the recognition result is available immediately
      after the recognition timer expires. If the HWR task takes longer
      to process than the recognition timer, the results will be provided
      as soon as the HWR task is done.
      
      Ongoing recognition task is cancelled if the user continues drawing
      while the recognition timer is running. If the recognition task is
      already completed, the current result is ignored and the result
      from the next recognition task is used instead.
      
      Change-Id: I9ba797223d8a9b8daf423e500fcf9d5250caaa5a
      Reviewed-by: default avatarMitch Curtis <mitch.curtis@theqtcompany.com>
      2ca10dd4
  11. 17 Jun, 2015 - 1 commit