Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Text entry only in capital letters #289

Closed
saemiw opened this issue Jun 6, 2018 · 15 comments
Closed

Text entry only in capital letters #289

saemiw opened this issue Jun 6, 2018 · 15 comments
Labels

Comments

@saemiw
Copy link

saemiw commented Jun 6, 2018

Since at least QField 0.10.12 (also 0.10.13) but not 0.10.9 QField has a problem when entering text. It always turns on the capital function and all text is entered in capital letters. The button to write in small letters can be pushed and one letter be entered correctly. But he following letter will be entered as capital again. This behaviour seems device or android version specific. We can only reproduce it on Samsung Galaxy Tab Active 2 (model number SM-T395, android version 7.1.1) but not on with model number Galaxy Tab Active (SM-T365, android version 5.1.1)

Can anyone reproduce this with other devices/Android versions? Do the developers see a possiblity to solve this?

@VxTedxV
Copy link

VxTedxV commented Jun 6, 2018

+1
on Samsung Galaxy XCover4 - Android 7.0

@ferenc-attila
Copy link

±1
on Galaxy Tab S2, Android 7.0
Only with factory keyboard. Works well with Google keyboard (gboard).

@saemiw
Copy link
Author

saemiw commented Jun 11, 2018

There is a workaround for the problem (in German): In the settings under "Samsung Tastatur" -> "Intelligentes Tippen" -> desactivate "Automatische Grossschreibung"

@fahrwegdienste
Copy link

This issue can be reproduced with

  • Samsung Galaxy Tab Active
  • Samsung Galaxy Tab Active 2,
    using QField 0.10.13, Android 7.

@signedav signedav added the BUG label Jul 11, 2018
@gnerred
Copy link

gnerred commented Aug 29, 2018

Is it planned to fix this bug ? Thanks

@Emic37
Copy link

Emic37 commented Sep 19, 2018

I encount same issue with default samsung keyboard on Samsung Galaxy S7. But no issue if I use Gboard keyboard.
However, when I use Gboard keyboard (my default keyboard), automatic correction seems not work.

@m-kuhn
Copy link
Member

m-kuhn commented Oct 5, 2018

Looks like there's a fixed version of Qt available. Fingers crossed.

https://bugreports.qt.io/browse/QTBUG-69398

@m-kuhn
Copy link
Member

m-kuhn commented Oct 5, 2018

This will only be shipped with Qt 5.11.3. If the rhythm between 5.11.2 and 5.11.3 is also 3 months like between 5.11.1 and 5.11.2, this should be available before January.
This can be tested before, but building Qt ourselves will need some extra effort.

@3nids
Copy link
Member

3nids commented Oct 5, 2018

5.12 is out on 29.11.2018 anyway.

m-kuhn added a commit that referenced this issue Dec 6, 2018
@m-kuhn
Copy link
Member

m-kuhn commented Dec 11, 2018

#405 should solve this. Unfortunately I am not able to reproduce the issue, can someone download the apk here and check? Thank you

@saemiw
Copy link
Author

saemiw commented Dec 11, 2018

Yes I can confirm that the problem disappears with the apk of #405

But (spoiler) instead I have problems saving a second feature. I can enter and save my first feature (a polygon in a geopackage) perfectly. When trying to enter a second feature I miss the buttons to finish the entering process. See printscreen below. If I close and re-open QField I am able to again enter 1 feature.
screenshot_20181211-161253_qfield

@m-kuhn
Copy link
Member

m-kuhn commented Dec 11, 2018

Thanks for the feedback and ouch for the issue.

Can you verify with the apk in #404 too, to see if the issue was introduced by this pull request or another one?

@saemiw
Copy link
Author

saemiw commented Dec 11, 2018

The issue described with the printscreen above also appears with the apk in #404

@m-kuhn
Copy link
Member

m-kuhn commented Dec 11, 2018

Thanks a lot for the feedback and testing @saemiw
The capitalization problem is in master and will be fixed with the next release.

I have opened a new separate issue #407
If you have more information regarding that please post there.

@m-kuhn m-kuhn closed this as completed Dec 11, 2018
@3nids
Copy link
Member

3nids commented Dec 13, 2018

@saemiw this is fixed by #412

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants