search

victronenergy / gui-v2

Other
30 stars 10 forks source link

Consider configuring Qt VKB UI options #206

Open blammit opened 2 years ago

blammit commented 2 years ago

We might need to configure the Qt VKB. In our default version, for example, the i18n key shows a default list of language options including American English, Spanish etc. but we should only show the supported languages.

chriadam commented 1 year ago

This is important for the WebAssembly case, especially on mobile device (iPhone/Android) browsers, assuming that we want to disable the native virtual keyboard (due to https://bugreports.qt.io/browse/QTBUG-88803 etc).

The alternative (to rely on the native virtual keyboard, rather than Qt's VKB) would be better but seems like it is riddled with upstream issues at the moment...

chriadam commented 9 months ago

We want to enable the Qt VKB on CerboGX, but we want to disable it for WebAssembly (since the user should be using the native iOS / Android VKB on those platforms, and the hardware keyboard on the desktop platform). This is already done properly in our code, so there should be nothing left for us to do.

chriadam commented 9 months ago

Basically, we just need to check (after translations support has been properly included) that the Qt VKB on CerboGX is switching properly when the language changes. It should already work, we just need to confirm.

No changes should be needed from us.

blammit commented 9 months ago

Basically, we just need to check (after translations support has been properly included) that the Qt VKB on CerboGX is switching properly when the language changes. It should already work, we just need to confirm.

Note, translation support will be fixed by https://github.com/victronenergy/gui-v2/issues/573