Skip to content

Thomas Schewe

My feedback

2 results found

  1. 35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    What you are saying makes sense, and would not be hard to implement. However the trick is to keep the configuration simple for the user. It starts to feel clunky when you are having to select layout and language separately.

    One idea might be to have an “freeze layout” switch which if unset (the default) leaves behavior as now. If it IS set, that layout stays unchanged, and only the language changes when selecting by the regular mechanism (either quick-switch or from list in settings).

    Thomas Schewe supported this idea  · 
    An error occurred while saving the comment
    Thomas Schewe commented  · 

    I have the same Problem here. I write in German and English and I don't want to switch the layout, cause I slows me down.

    It somehow works with the Apple virtual keyboards (I am now writing with the German layout (the one QWERTZ w/o äöü, and don't ask me again, why I want to use PadKeys). I don't switch the language and autocorrection still works for *both* languages.

    I have no idea, how you can implement it in an elegant way.

    Your proposal sounds somehow good, but how will the language-switching work? A second entry in the list of keyboard? Or will it be necessary to "slide" to the PadKey settings and change it there? This would be pita.

  2. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We are still considering this. For Typefinity 2.0 we almost removed the two punctuation keys on the right of rows 2 and 3 (and did remove one on row 1) which would have given extra width to the letters (without actually removing umlauted keys), however we were a bit hesitant to "rock the boat", as the keyboard is widely used in Germany. Instead we may add a second German layout with this removal.

    An error occurred while saving the comment
    Thomas Schewe commented  · 

    I don't need PadKeys for the äöü, cause one of the Apple Layouts includes them.

    So the question reduces to "Why to use PadKey in general?"

    I thought it would be clear: The keys to move the cursor. The permanent row with the numbers.

    Thomas Schewe shared this idea  · 

Feedback and Knowledge Base