Disregard 'Always show number row' if the layout already has a number row

[herrbrixter]

Is your feature request related to a problem? Please describe. When the 'Always show number row' is enabled, the app shows it even if the keyboard layout already has a number row. It is redundant and makes the keyboard smaller.

Describe the solution you'd like Make an exception for Always show number row. I think only PC layouts have a number row included. No need to display an additional number row.

Use case PC layouts already have number rows.

Describe alternatives you've considered (if any) None.

[Symbiomatrix]

I think that might be difficult to detect - there are layout flags but "number rows" aren't exactly standard issue. You're not looking to optionally disable the number row on the pc keyboard which is doable (since it also has - and =), but for the number row to check whether the current layout has 0-9 anywhere, in essence. Easier to handle on the user end - setup a custom pc keyboard on all languages you use and disable the numbers row globally (as well as its appearance in popups). I've created a spreadsheet over on #1039 which I think should make building simple key + popup custom keyboards like that fairly straightforward.

[herrbrixter]

I'm not tech savy to customize my keyboard layout.

I use 2 layouts: English Qwerty and English PC. Unfortunately, the Always show number row setting applies globally. I'd like it to apply to my English Qwerty layout only.

[Symbiomatrix]

I'm not tech savy to customize my keyboard layout.

It's not too complicated, I think I can guide you step by step on how to do that given a layout file, if you can handle basic navigation on android. Question: Why do you switch between PC and qwerty layout? Is it because pc is too bloated for regular use? Is there a single custom layout which would fit both of their purposes for you (eg adding some keys to qwerty)? Can you describe or draw it?

If you still need 2, then I can show you how to add a permanent number row to qwerty which would obviate the need for the setting. But I think customisation is more convenient than swapping keyboards. And as stated in the other issue, arrow keys at least would be great to have on the layout.

[Helium314]

makes the keyboard smaller.

Though this is only the case for keyboards with more than 3 rows.

I think that might be difficult to detect

Detection would be too much work, but actually there is a hardcoded list of layouts with numbers that could be used here. But such automatic removal of the number row would change height of the keyboard when changing language or switching to symbols. In the past there were a bunch of issues because users did not like such change, so this needs to be optional.

[herrbrixter]

I agree. The simplest way is just to identify which layouts have a number row included, then exclude them.

I'm fine if it's optional. It just looks weird to me to have 2 sets of numbers.