• Avatar
    Permanently Deleted User

    Hi, why don't just add a space after each word regardless what ? 

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Lim Tock Yen
    Check the new update. It's available as an option under the "typing" settings.

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Wparks82

    Thanks!! But to get the update ? I am using Redmi Note 4

     

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Lim Tock Yen

    You need to make sure you have the latest version of SwiftKey on your phone (6.5.8). Here are the instructions listed by Ryan P a few days ago:

     

    Today we rolled out SwiftKey 6.5.8. With this new release we have added a setting that allows you to alter how auto-space after flow works. 

    You can have it auto space or not - depending on your preference. 

    Here's how to adjust your setting:

    • Go into SK Settings
    • Typing
    • Typing & Autocorrect
    • The toggle is at the bottom of the list

     

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Nice

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @ Wparks82

     

    Thanks!! I got it! 

     

     

    0
    Acciones de comentarios Permalink
  • Avatar
    Greg Aloe

    Many thanks for bringing back this feature as an option as we requested almost two months ago.  However, I still have an issue I want to describe here because I'm curious if others have had the same experience.  I will submit this as a feature request as well.

    In the 6.5.4.21 version, when using flow, I noticed that my flowed word would show up in the center of the predictions/corrections bar for a fraction of a second, allowing me to just glance up at that one spot while I flow word after word.  But with this new release of the predictions-after-flow option, the word disappears almost instantly.  I could credit that to a performance improvement of the app, but the side effect is that now I don't know whether I flowed the right word without looking back into the text field I'm writing in.  So my eyes are jumping from the keyboard to the app.  I'm getting used to it, but it would be really cool if I could configure the time delay between (a) seeing the flowed word in the bar and (b) when the predictions show up.

    Thanks again for listening to your community.  Hopefully this was a huge learning experience for SwiftKey.

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Shout out to the SwiftKey team for bringing the best of both worlds with the new option! Thanks for listening to the community and adding customization and flexibility, this is what SwiftKey stands for!

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Greg Aloe: I noticed that. In terms of programming, it looks like the option is just automatically adding a space right after the end of the flow, so you still see the predictions for the word you flowed for a fraction of second. The feature of showing predictions/corrections for the word you just flowed is still here, so it blinks rapidly when the option is turned on.

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I hate this keyboard. It automatically adds misspelled words. It's extremely annoying. Galaxy has yet to top the GS5 in that regard. Thanks for making the phone more frustrating in order to appease those too lazy to press "add word to dictionary". I know pressing it was a heavy burden.

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Hello, coming from Windows Mobile and was wondering if there is a way to show more than three possible word options?  Other than that great keyboard, Thanks

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User
    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Thank you very much for adding the option to add a space automatically!

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Hi,

    There are some agglutinative languages with postfix inflection which would be very complex to serve by algorithms because of the context related inflection. It's not a big issue if user has an option in the settings for the following behaviour: after flow prediction, the next single character selection (not flow!) will be concatenated to the offered and accepted word instead of starting a new word. Next flow adds space. Trivially, space will separate words. Punctuation adds space. Non plus ultra, this feature could be enabled automatically based on the offered language: https://en.m.wikipedia.org/wiki/Inflection
    Same issue if I want to use : or ; punctuation stuck to the word (now, I get an unnecessary space), although it's not language related...

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    PLEASE let me turn off auto-spacing after tapping a prediction. This is insane. Why would you change something without giving your users options? I don't want to have to go back to Swype

    0
    Acciones de comentarios Permalink
  • Avatar
    Hritwik Jadhav

    Hello Ian,
    If you have been out of the updates on entire debate over the respected feature in SwiftKey, I recommend you to check your SwiftKey settings.

    'typing' > 'typing and autocorrect' > *at the bottom of the screen. Swipe down* 'show predictions after flow' should be on.

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Sorry I missed it when it happened, but THANK YOU guys for listening and making predictions available again. I'm so glad I can update the app again. I restored my 5 star review too, because this way I truly think this app belongs to the nr1 spot.

    top work!

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Greg Aloe, I agree with you. I'm happy to have autospace back with the update, but the problem you are describing is still super annoying.

    I want the recognised word to be displayed in the bar for a second or so before it disappears.

    When I flow, often I'm trying to write one of three words that SwiftKey recognises. For example just before I wanted to write "flow", but SwiftKey wrote "follow". In previous versions, both of these words would have appeared in the bar allowing me to select the correct one.

    Now the wrong one is simply inserted.

    The issue seems to be that SwiftKey developers have become too confident in their algorithm. There simply are some words that are too similar to distinguish. And in these instances, SwiftKey should present a choice in the bar, like it used to, rather than selecting one that is probably wrong.

    I hope this gets fixed. I used to love SwiftKey, but with the current version I either am super slow because I keep having to correct flows, or I end up not flowing at all because it's too annoying.

    1
    Acciones de comentarios Permalink
  • Avatar
    Greg Aloe

    @David Meier, I'm not sure you're describing what I'm experiencing.  Yes, there's now a smaller (almost unnoticeable) delay between when I flow the word and when the next predictions show up.  

    However, SwiftKey did not previously give you an option to choose a word to correct what you just flowed.  That's actually the new feature that a lot of people in this thread didn't like.  So it sounds like you actually prefer the new default feature to show corrections without guessing for you.  However, it sounds like you want the auto-space along with that set of corrections.  But I don't see how that kind of feature would be much of an improvement if you always plan to select the correction, which then inserts the space.  I played around with the new default a little, and without going into a lot of detail, it seemed that an auto-space might help you type a single-letter word following a flow that you didn't need to correct.  But if that's the case, then that's something SwiftKey could probably improve even without auto-space.

    I hope this helps, and I'm sorry if I"m not being clear or if I've misinterpreted what you're describing.  It's pretty crazy how confusing it can be to describe these keyboard behaviors!

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Greg Aloe -- thanks for picking up on this. Here's where I'm coming from: I really do not like the new feature with autospace turned off. When I turn autospace back on I still really do not like it, and I notice that my use of SwiftKey is much more annoying than it used to be!

    But you're right, I had misremembered a little how the old version behaved. So I've tried it on my old phone (and it's really an old version -- I tried 5.2.2.124). It turns out my problem is precisely the one you describe. In my normal use of SwiftKey, when a flowed word was wrongly recognized, the word would briefly be displayed in the bar. Just long enough to comfortably check it, which I would do automatically. If it wasn't the correct one, I'd hit the back button and select one of the other ones on offer. (I had forgotten the back button bit in my description -- but as it turns out, I don't mind hitting the back button once to get the other suggestions!)

    The problem with the current version is that the display time is so short that I have to be super focused to take the recognized word in while typing. It's just too fast. This means that I usually have to look at the field where I'm typing (which may be on a far away part of the screen). Most of the time I just keep typing and end up realising the problems only later (since I don't want to keep checking every word...). Then I have to move back several words and fiddle around with what's there. 

    Anyway... We seem to be on the same page after all. Thanks for making me clarify this.

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently deleted user

    Hello. I've enveloped using SwiftKey on Android and was glad to see it done available for my iOS devices. However, the iOS version does something very strange compared to Android. On Android, the spaces come before each word unless the word follows a carriage return. On iOS, the slaves come after, creating very strange results with punctuation. It usually works like this:

    Apple :pale,son!belly.film,cheese #cell /dodge ;poodle 

    As you can see, punctuation often follows a space, which must be removed manually, then a manual space must be added following it. Only the comma and period automatically remove the space, but none add the space after. 

    In most cases, you want the space to precede the next word, not follow the previous. Can you correct that issue?

    If it is supposed to work that way, I may have a bug in the version I am currently using. 

    Thanks!

    0
    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.