That's weird, I've never had that issue, but now I know how to fix if I do.
That's weird, I've never had that issue, but now I know how to fix if I do.
The issue exists only in the official beta version (5652.) It doesn't happen with an earlier (but still beta) version (5612.)
That's weird, I've never had that issue, but now I know how to fix if I do.
The issue exists only in the official beta version (5652.) It doesn't happen with an earlier (but still beta) version (5612.)
That makes sense, I got version 5612 off of a post on this forum.
I was going to ask what other fixes or enhancements went into the newer beta version, but you've saved me the trouble of tracking down release notes. I think I'll stick with this version to avoid the minor bug. I really do love the software though, it has drastically changed how I text and it's for the better.As far as I know Swype hasn't found a way around the problem. That's the challenge of trying to make one's software be both tightly integrated with a device's o/s implementation and still workable with a broad selection of devices.
What was the Trial Release 0.35.3959. Cause I don't have those problems, nor has it "timed yet" at least as of yet. It could use a little refinement, but tell you what, I would rather use a not as refined version, than live without it.