• Avatar
    Alpert

    Hello,

    Can you be more specific on spaces while using hyphen and colon?

    As for the quick reply on lockscreen, we supported it now on latest beta app, but only for Android 5.1+ devices.

     

    Alpert

    1
    Azioni per commenti Permalink
  • Avatar
    Permanently Deleted User

    How cool is that? Quick Reply on the lockscreen? I love it!

    To give you an example in my language:

    I'd like to swipe the word "Google-Tastatur"

    With Gboard it's pretty easy:

    Swipe Google
    Swipe hyphen
    Swipe Tastatur

    With Swiftkey:

    Swipe Google
    Space
    Backspace
    Long press hyphen
    Swipe Tastatur

    It's the same with the colon. I always use the colon immediately after a word. You can find several examples in this post actually.

    4
    Azioni per commenti Permalink
  • Avatar
    Permanently Deleted User

    Another problem concerning the last update: the shift key doesn't change the actual swiped word anymore. So you took away the option to correct the capitalisation immediately. I'd think this goes kinda against the new flow feature. Bug or feature?

    1
    Azioni per commenti Permalink
  • Avatar
    Alpert

    Hi,

    I guess the second post linked to the auto-space feature. You'll need to submit a feature request for it, I suggest.

    The 3rd post, please join here. Because I am not testing the new flow mode so that I don't know what's like.

    Best

    Alpert

    1
    Azioni per commenti Permalink
  • Avatar
    Permanently deleted user

    I'm having major issues with the M and N keys. Whenever I start swiping a word that starts with those letters it puts an M and then a space and starts trying to figure out what what I'm swiping after that. Does anyone else have this problem?
    It happens with other letters but not as much. Also the space bar is way too big. I know that's a preference thing but would it be possible to have a customizable spacebar?

    1
    Azioni per commenti Permalink
  • Avatar
    Permanently deleted user

    Jean-Philippe I have have a similar issue. Whenever I type words that start with M using flow it tries to put in the special characters and won't finish typing the word. It happens every time. Did you get a solution to your issue?

    0
    Azioni per commenti Permalink
  • Avatar
    Permanently deleted user

    I agree with Po8 (though I don't understand why he specified space before backspace in the SwiftKey sequence). Coming from Swype, SwiftKey's strange space-adding/deleting behavior is intolerable, and the issue not only affects hyphens and colons but also semicolons and slashes. It occurs when swiping even if you disable the setting that adds a space and provides predictions. That is, even though there will be no space before the cursor after swiping 'Google' in the OP's example, typing any of the aforementioned symbols will add a space before the symbol, though none of these symbols should typically be preceded by a space. This is really dumb and confusing. With the setting off, at least the added space acts as a reminder to hit backspace (even though this is unnecessary with commas, periods, etc.) And if you're typing normally (not swiping) and enter a word without tapping a predicted word (so that the cursor appears without a space before it), typing one of these symbols does NOT add a space before it. So for those who use both swiping (with the space/prediction setting disabled) and regular typing, SwiftKey's behavior is ridiculously confusing and inconsistent.

    Note that with the odd exception of the slash, SwiftKey also adds a space after the symbol, so to correct the mistake, the user needs to hit backspace 3 times before trying again. Unbelievably inefficient.

    I use compound or otherwise hyphenated words all the time. I also regularly separate multiple words with slashes. Doing these things with SwiftKey really sucks! I actually tried Gboard before SwiftKey but gave up on it because there's no key with a slash as a dedicated secondary character. I was very happy to see that this wasn't the case with SwiftKey, but the spacing bizarreness is just as bad and affects other characters as well. I'm seriously considering going back to Gboard.

    Seems to me the real issue is that SwiftKey, unlike any other keyboard I've used, generally adds a space after a word and then has inconsistent rules about deleting this space when the user adds punctuation or other non-alphanumeric characters. The better option is to never add a space after a word *except* when the user enters another word. I think we can all agree that two words should be separated by a space, but apparently there's disagreement about certain symbols. Therefore, add the space automatically between two words but leave it up to the user whether to add a space between a word and any of the characters in question. This is how both Swype and Gboard work and is much more intuitive (though I acknowledge that some long-time SwiftKey users might disagree). I still think it's weird that adding a period, comma, etc deletes the preceding space, so I'm tempted to delete it manually. The solution is to do away with the automatic space before the cursor. Just add a space before the next word. This all seems so obvious. I really don't know what SwiftKey is thinking.

    1
    Azioni per commenti Permalink
  • Avatar
    Permanently deleted user

    The space before and after the hyphen is making me crazy! Why can't we customize this? Or Swype should just test the hype like any letter! It's leading me to consider other apps.

    1
    Azioni per commenti Permalink