The T9 Write CJK integration added a new internal function
T9WriteInputMethodPrivate::setContext() used for updating T9 Write
session settings for different layout scenarios (e.g. full screen
mode vs regular layout).

However, this function calls finishRecognition() so it breaks the
input when switching between full screen mode and regular layout.

Fix this regression by preserving input between context changes.

Change-Id: I3ac269247466d34729c9b49c43425af069af69ea
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

[ChangeLog] Added Estonian keyboard layout.

Change-Id: Iadb39df14980e36a15f61f4e4f346f8aeee63b91
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

[ChangeLog] Added Dutch keyboard layout.

Change-Id: I91d853fe2e74c68492caf9afac85df2c4b64548d
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

 Conflicts:
	.qmake.conf
	tests/auto/inputpanel/BLACKLIST

Change-Id: Iab123586edb652a8ce14d89736aa13dc3c6203e6

If a plugin is used, the qmldir file must be located next to
the plugin in the file system. By it being included in the .qrc
file it was deployed twice, once in the file system and once
in the virtual resource file system. A recent change in declarative
ended up doing an implicit import on that virtual directory and
thus uncovered this bug of the qmldir file being present in a (virtual)
directory where it doesn't belong.

qml_module.prf takes care of deploying the qmldir.

Task-number: QTBUG-62138
Change-Id: I7693b5656cb593454e2d777fe179e6f889d6dbdf
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

QStringLiteral is broken in MSVC2015 onwards when used with \uXXXX
encoded character literals. This was the reason Japanese tests were
failing - the OpenWNN engine was actually broken and producing
garbage.

Not only this change eliminates QStringLiteral from openwnn, but also
reduces runtime memory usage by replacing QMap<QString, QString>.

The new solution is based on simple binary lookup table WnnLookupTable.
WnnLookupTable data was converted from existing QMap structures using
WnnLookupTable::create() method, which was left there for future
reference.

This change also removes the unnecessary QObjectPrivate definitions
from Romkan* classes.

[ChangeLog][OpenWNN] Fixed and optimized OpenWNN engine (as a workaround
for QStringLiteral breakage)

Task-number: QTBUG-62133
Change-Id: I50c9e2f5c363e1314f47d7023685da543ec9a7eb
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
(cherry picked from commit 0bf1c6ad)

Reduces allocations.

This is the result of running the (experimental) clang-tidy check
   qt-modernize-qsharedpointer-create

Discarded changes: none.

Change-Id: I9ef1ccd46315f1bb8f3cc30a652f17c18b46232c
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

The tests for boot2qt were disabled with commit
96c9211b

. The tests can
be enabled since qtdeclarative now fallbacks to software
renderer if OpenGL is not supported.

Also blacklisted a test failing because of QTBUG-61279

Change-Id: I56bd5041b1ffbb150cdaab1f76638fd79041af06
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

This change adds handwriting support for Japanese.

Change-Id: Ifc8f0e32c8b3211c13aee8be5cb2e05fae09d3b7
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

This change adds handwriting support for Korean.

Change-Id: I77eb322020c39259d9609051100c40b271a62c04
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

This change adds handwriting support for Traditional Chinese.

Change-Id: Ic358bf81795a3c88234b5e9c85635223ebf1c0d7
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

This change adds support for handwriting in Simplified Chinese.

The integration is based on T9 Write CJK SDK v7.8.1.

[ChangeLog] Added support for CJK (Chinese/Japanese/Korean) handwriting
via T9 Write.

Change-Id: I18481cfd897987ecb471c49ecfcac62ea0c3489c
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Liang Qi <liang.qi@qt.io>

QStringLiteral is broken in MSVC2015 onwards when used with \uXXXX
encoded character literals. This was the reason Japanese tests were
failing - the OpenWNN engine was actually broken and producing
garbage.

Not only this change eliminates QStringLiteral from openwnn, but also
reduces runtime memory usage by replacing QMap<QString, QString>.

The new solution is based on simple binary lookup table WnnLookupTable.
WnnLookupTable data was converted from existing QMap structures using
WnnLookupTable::create() method, which was left there for future
reference.

This change also removes the unnecessary QObjectPrivate definitions
from Romkan* classes.

[ChangeLog][OpenWNN] Fixed and optimized OpenWNN engine (as a workaround
for QStringLiteral breakage)

Change-Id: I50c9e2f5c363e1314f47d7023685da543ec9a7eb
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Change-Id: Id387390ae533debf39b008b456a94f4c427993b4

Change-Id: I72da022872d814fe1e21d111b77748d7e98fbb7a

Change-Id: Id3bdf678c9aff44fc636d1f1880e57e740a8ef8e
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Some handwriting.qml files were using the old commercial
license headers. Also updated the copyright year.

Change-Id: Id603976bc6343797fd993e8041065d6afb2dc7a9
Reviewed-by: Konstantin Tokarev <annulen@yandex.ru>
Reviewed-by: Jarkko Koivikko <jarkko.koivikko@code-q.fi>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

UWP is not a supported target platform for virtual keyboard.

Change-Id: I00ccbfeb4f77e07b1d46dd5d54f50b55e3b778d8
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
Reviewed-by: Gordan Markus <gordan.markus@pelagicore.com>

Conflicts:
	.qmake.conf
	src/virtualkeyboard/virtualkeyboard.pro

Change-Id: Idf7682b63379b94a1d444d3528472afea77133bc

test_languagePopupListActiveLocales test will fail with
unhandled exception if only Korean (for example) is configured.

In this case the language button is not found, and calling
virtualKeyClick() function with null parameter causes an
unhandled exception.

Change-Id: Idc5d57fe56423d7a49947f6c02e75d28b7e4ec90
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Change-Id: Ib358606c36a668f4d8a0c03db756f894dac0b872
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Change-Id: Ied53fe56a6b9c9a71b5bbe9ed85270fb89ad8c5c

Change-Id: Ie3f0ad96842910ddd71a32d06bb80a5035e7f82c
Reviewed-by: Jarkko Koivikko <jarkko.koivikko@code-q.fi>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Toggles between available input modes.

[ChangeLog] Added new component (InputModeKey) for input mode switch.

Change-Id: Ie7c53b177264e8c8f8004bb953da9e8568631fab
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

The inputModes property was not notified properly when updated.

This change adds value cache and update function for the property.

Currently this property is not tracked by anything, so the bug
was not noticed.

Change-Id: Ic9e562c6e6c8f508e56f115981a52314bef05535
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

The recorded traces are stored in Unipen format and used mainly for
automated testing.

Change-Id: I9247cc461df2fb74ef824221a4905ded90333cc5
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

LipiInputMethod supports simple swipe gesture recognition.

This can also be used in other input methods, so move it to simple class.

Change-Id: Ib5328e0570346d534c71787fcb79a6c7e4c3d0a7
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Originally the emulated HWR input was centered on the input window
because it look better. However, it seems this will confuse T9 Write
HWR engine and cause some tests to fail.

Change-Id: I72e5c1a5db2b5aded2db2e5a8f6f79f5f414d5aa
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

HunspellInputMethod must update selection list status immediately
after dictionary starts load.

This issue should not cause issues in normal use, but it will cause
automatic tests to fail with lipi-toolkit. This is because LipiInputMethod
uses HunspellInputMethod for spell correction and suggestions.

The automated tests rely on selection list status when deciding if
spell correction is available or not.

The failing tests was test_hwrWordReselection_data.

Also, fix incorrect debug stating dictionary could not be found.

Change-Id: Ic6c3526a494fb60dde234c000ed9bd0d70f53335
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

If the virtual keyboard is configured to exclude english layout and
the configured language does not contain the special number layouts
(dialpad, digits and numbers), we must include the special number
layouts from en_GB locale as fallback.

Change-Id: Ieda43511c5edb71aa36256934a7b42f7312709cc
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Gordan Markus <gordan.markus@pelagicore.com>

Change-Id: Ica0fcdd8f2ee9c467f7119a8fa249fe2c60e5a9d

Use multi-arg overload instead of chained QString::arg() calls.

Change-Id: Idd279664e66655dfbc4f3f31bbf705ee6e387724
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Change-Id: I705129c56e968a72cf3d4de5b37b092cee93965c
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Use emit instead of calling a signal as a regular function.

Change-Id: Id27031447ebd65c463f4bab5d074f2dbd7b6284a
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Change-Id: I12400fab4eaef25fcfff5245d61c184958df506e
Reviewed-by: Jarkko Koivikko <jarkko.koivikko@code-q.fi>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Listing important changes and bug-fixes.

Change-Id: Ib9ac4fff8076ed2ccaea696441a81eaa511568b2
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

We might run an event loop after destroying qApp and additional events
may be generated from that. Therefore we should not access qApp
unchecked from event handlers. In most places we did already check qApp
for null. Now we do it everywhere.

Task-number: QTBUG-60000
Change-Id: Id72bbf133989e4f8127d85ee63cba64f915d3649
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Currently boot2qt is tested with QEMU and some tests fail. Disabling
them for now to make it possible to enable qt5 tests for Coin.

Task-number: QTBUG-60266
Change-Id: I1c520d276bcb606d8d9fa5c7055688defb763867
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Without this patch the module is not bundled in static builds correctly
causing 'module "<QtModule>" is not installed' errors in during runtime.

As reference: this happens, because 'QQmlMetaType::isAnyModule(importUri)'
at 'qtdeclarative/src/qml/qml/qqmltypeloader.cpp:1422:' returns 'false',
which indicates that the module was not registered.

Task-number: QTBUG-59559
Change-Id: I2856ceaf8148ccbe2c930ec5fdd878c084107ea3
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
Reviewed-by: Andy Shaw <andy.shaw@qt.io>

This fixes a problem reported by Intel Inspector 2016 which indicated
that multiple threads could access the abort variable at the same time.
So by making it atomic we avoid any problems in this regard.

Task-number: QTBUG-60037
Change-Id: I79d293916f5105e8a36c41d3bc89cd1cb93e5109
Reviewed-by: Jarkko Koivikko <jarkko.koivikko@code-q.fi>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>