Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (5)
to General by teroyk - 3 hrs, 52 mins ago -
Extra softwares in Sailfish using CLI, repositories, etc (118)
to SailfishOS by nieldk - 9 hrs, 5 mins ago -
Paths (0)
to Maemo 7 / Leste by teroyk - 1 day, 6 hrs ago - more...
 |
|
2012-08-16
, 14:36
|
|
Posts: 464 |
Thanked: 338 times |
Joined on Feb 2011
@ UK, Northwest
|
#2
|
Just tried this several times but I can't replicate your problem - my message comes up as typed.
I'm on PR1.3, Northern Europe
I'm on PR1.3, Northern Europe
__________________
N9 black, 16GB, PR1.3
N9 black, 16GB, PR1.3
 |
|
2012-08-16
, 14:40
|
|
Posts: 857 |
Thanked: 1,206 times |
Joined on Dec 2009
@ Chertsey in the Thames, United Kingdom
|
#3
|
oh yes, I get the same. I would just swipe to the standar keyboard when inputting this. It is odd, but I also get odd rpeated words when typing in a google search bar.
__________________
Proud owner of Jolla phone, number 274.
Proud owner of Jolla phone, number 274.
|
|
2012-08-17
, 02:46
|
|
Posts: 24 |
Thanked: 12 times |
Joined on Jan 2012
@ New Zealand
|
#4
|
I can replicate this issue. I probably have never noticed this I think, because there is no need to use the space bar, on the swype keyboard, in this manner. For instance if you attempt to enter another word directly after entering 1024k a space will be added correctly, also if you swipe from either the comma or period to the space bar the cursor behaves as it should.
Interesting find though.
Interesting find though.
 |
|
2012-08-17
, 02:51
|
|
Moderator |
Posts: 3,715 |
Thanked: 7,419 times |
Joined on Dec 2009
@ Bize Her Yer Trabzon
|
#5
|
Yup, I confirm this bug aswell, you should go to the forums of swype and file the critical bug over there. I'm sure they can patch this 
|
|
2012-08-17
, 11:44
|
|
Posts: 5 |
Thanked: 19 times |
Joined on May 2012
@ Pakistan
|
#6
|
I'm getting the same bug. Here's a workaround:
Type 1024 then a space, then backspace, and then k.
Type 1024 then a space, then backspace, and then k.
|
|
2012-08-17
, 13:30
|
|
Posts: 31 |
Thanked: 4 times |
Joined on Jun 2012
@ Philippines
|
#7
|
Tried it, working just fine for me. And I'm pretty sure the swype team will not be updating swype for the N9 anymore, so...
|
|
2012-08-18
, 02:00
|
|
Posts: 64 |
Thanked: 42 times |
Joined on Jun 2009
|
#8
|
Originally Posted by dumpystig
That is the version I'm using (64gb version; not sure that makes any difference).
Just tried this several times but I can't replicate your problem - my message comes up as typed.
I'm on PR1.3, Northern Europe
Are you trying from the Messenger/SMS app, while writing a text message to someone else?
However, I just tried the same while typing a note inside the Notes app. The behavior is the same: after typing "1024k |" (using the default, non-numeric keypad in Swype), it now shows "102k |4k" (again, "|" indicates last cursor position -- so I never actually see what I have put in the first quote above, because adding the space at the end automatically triggers the behavior).
Originally Posted by shanic89
Thanks for that suggestion; I will try doing it that way. There have been situations where Swype has not always inserted a space on its own. If I knew when to expect that behavior, I would probably use the space bar less.
I can replicate this issue. I probably have never noticed this I think, because there is no need to use the space bar, on the swype keyboard, in this manner. For instance if you attempt to enter another word directly after entering 1024k a space will be added correctly, also if you swipe from either the comma or period to the space bar the cursor behaves as it should.
Interesting find though.
 |
|
2012-08-18
, 07:18
|
|
Posts: 308 |
Thanked: 299 times |
Joined on Jul 2012
@ Graveyard
|
#9
|
I was about to post the same bug here
__________________
Previous versions of Harmattan used to not do this (at least 1.1; can't remember about 1.2).