Related
Having written StylusLock I wanted an additional lock/unlock method. Although StylusLock works great, I wanted some extra features:
* to have it possible to lock and unlock "one handed". The StylusLock approach cannot be done "one handed", e.g. on a bike.
* Also some people do not like to operate with the StylusLock (always).
* The combination with this new CapacitiveFingerLock and existing StylusLock will suit more people.
* And sometimes people will use the Stylus, so they will get the right behaviour depended on the usage pattern
* Still the goal is to let it consume almost no CPU and battery and KISS to operate
I discovered with StylusLock that when the TouchPanel and Hardware keys are locked, still the Zoom function works in e.g. Opera.
You can try yourself, using StylusLock:
1. Start Opera
2. Lock the Touch Diamond or Touch Pro with StylusLock
3. TouchPanel and all hardware keys are locked
4. Try to Zoom in/Zoom out in Opera, this still works with the NavWheel
5. Also the Ok button seems to react
I figured out via Scott Seligman and Koushik Dutta how to programmatically access the Capacative Touchpads. You can read also more here: [REF]Capacitive touchpad apps
So this idea is implemented in CapacativeFingerLock. But I am not using the NavWheel idea, but just uses the Capacative hardware area for locking/unlocking. The idea is again simple and clever. When you softly touch the area where the hardware keys are located (so do not press the keys, just gently touch them), the up/down and position area can be detected. I programmed that when the same area is touched gently 3 times within a second (without touching another area), the lock status is toggled.
I made a proof of concept program (just copy the exe inside the zip file attachment to your phone and just execute it), which shows how it is going to work. Just play around with softly touching the hardware panel, to see what happens.
If am working on integrating CapacativeFingerLock with StylusLock, to have a working "real locking" application. The Proof of Concept program just shows that it is possible.
Reserved for future use
Another one for future use.
very nice concept....now i noticed you posted a link of this thread in the wheel to unlock thread...would there be a way to possibly implement a config tool that lets you choose say, touch 3 times softly, or run your finger around the circle?
Malik05 said:
very nice concept....now i noticed you posted a link of this thread in the wheel to unlock thread...would there be a way to possibly implement a config tool that lets you choose say, touch 3 times softly, or run your finger around the circle?
Click to expand...
Click to collapse
In principle this can be done. But because the NavWheel is also used for other purposes (Zoom In/Out), I have chosen not to use the NavWheel, but the 3 times gently touching. In this way there is no interference with other existing applications.
I'll try that, it seems like no one cares aboyt the capacitive touch pad, it seems like an amazing thing that we've got that is so neglected. I hope to give some positive feedback later, but first I have some rom flashing to play with!
Thanks for the work, there must be so many possible implementations for this, I hope this is just the beginning of something much bigger.
How about a simple tap to launch app?
i went ahead and installed it, and it works very well...Will there be a (pretty) GUI to show that it was unlocked?
Also the diamond does have multi touch on that pad area, which enables a "trace" of the movement of your touch
http://www.youtube.com/watch?v=f3Owgcos_KY
Since the nav sensor wont be so ideal, how about sliding your finger from the top of the pad to the bottom (lets say, place your finger on the back button, and gently moving it down to initiate unlock, with a GUI on the screen following your movement, as you go closer to the bottom, the color changes from lets say, red, to green...with incremental color changes in between)
Instead of 3 taps, why not a swipe between the home and back keys, which seems much more natural.
Surur
surur said:
Instead of 3 taps, why not a swipe between the home and back keys, which seems much more natural.
Surur
Click to expand...
Click to collapse
I imagine it is just harder to implement for a proof of concept.
Personally I think there are enough ways to lock the diamond, whether you swipe the screen or 1cm below it is not a revolution, but if swiping the capacitive touch pad could be made to launch desired apps from selected gestures, that would be a revolution, like dynamo3 or hibernate or even standby. I think a lot of people here would want that over another locking solution. Good will intended!
Just tried it.
This is very cool very very cool
Thanks for time invested in such a cool development.
surur said:
Instead of 3 taps, why not a swipe between the home and back keys, which seems much more natural.
Surur
Click to expand...
Click to collapse
Swiping is not so easy one handed. Touching gently 3 times is much easier one handed, holding your Touch Diamond or Touch Pro firmly and touching with your thumb.
However, I can imagine other sort of applications which can use the swiping for other sort of operations. Both are possible with the programming API I made.
uniqueboy said:
I imagine it is just harder to implement for a proof of concept.
Personally I think there are enough ways to lock the diamond, whether you swipe the screen or 1cm below it is not a revolution, but if swiping the capacitive touch pad could be made to launch desired apps from selected gestures, that would be a revolution, like dynamo3 or hibernate or even standby. I think a lot of people here would want that over another locking solution. Good will intended!
Click to expand...
Click to collapse
I am going to share the source code. I have written it in C#. And others can get ideas and take over some of the source code for their own application. At the end we profit all of it.
ZuinigeRijder said:
I am going to share the source code. I have written it in C#. And others can get ideas and take over some of the source code for their own application. At the end we profit all of it.
Click to expand...
Click to collapse
I like your style, that is the the kind of development attitude that keeps here!
ZuinigeRijder said:
Swiping is not so easy one handed. Touching gently 3 times is much easier one handed, holding your Touch Diamond or Touch Pro firmly and touching with your thumb.
However, I can imagine other sort of applications which can use the swiping for other sort of operations. Both are possible with the programming API I made.
Click to expand...
Click to collapse
If you are open to other ideas, I would love the area from the back to home key to be a scroll bar when the device is in landscape mode. Grabbing the narrow on-screen scroll bar can be tricky, and the Touch Pro lacks the scroll wheel of the HTC Kaiser.
Surur
Have been looking into this myself as well. The only code I found was managed C#. Do you think we can use this in our native C code? Looks promising though!
ZuinigeRijder said:
Having written StylusLock I wanted an additional lock/unlock method. Although StylusLock works great, I wanted some extra features:
* to have it possible to lock and unlock "one handed". The StylusLock approach cannot be done "one handed", e.g. on a bike.
* Also some people do not like to operate with the StylusLock (always).
* The combination with this new CapacitiveFingerLock and existing StylusLock will suit more people.
* And sometimes people will use the Stylus, so they will get the right behaviour depended on the usage pattern
* Still the goal is to let it consume almost no CPU and battery and KISS to operate
I discovered with StylusLock that when the TouchPanel and Hardware keys are locked, still the Zoom function works in e.g. Opera.
You can try yourself, using StylusLock:
1. Start Opera
2. Lock the Touch Diamond or Touch Pro with StylusLock
3. TouchPanel and all hardware keys are locked
4. Try to Zoom in/Zoom out in Opera, this still works with the NavWheel
5. Also the Ok button seems to react
I figured out via Scott Seligman and Koushik Dutta how to programmatically access the Capacative Touchpads. You can read also more here: [REF]Capacitive touchpad apps
So this idea is implemented in CapacativeFingerLock. But I am not using the NavWheel idea, but just uses the Capacative hardware area for locking/unlocking. The idea is again simple and clever. When you softly touch the area where the hardware keys are located (so do not press the keys, just gently touch them), the up/down and position area can be detected. I programmed that when the same area is touched gently 3 times within a second (without touching another area), the lock status is toggled.
I made a proof of concept program (just copy the exe inside the zip file attachment to your phone and just execute it), which shows how it is going to work. Just play around with softly touching the hardware panel, to see what happens.
If am working on integrating CapacativeFingerLock with StylusLock, to have a working "real locking" application. The Proof of Concept program just shows that it is possible.
Click to expand...
Click to collapse
A while ago I posted about the Windows Messages received by the form for capacitive touch events. Is that what you ended up using to figure out where on panel is being touched? Mind posting some code so I can add it to the Sensors assembly?
Great idea. Defienetly it will be my way of locking device. StylusLock works nice but can't be operated by one hand so its useless for me. SensorLock uses battery and i've drop my phone already unlocking it.
surur said:
If you are open to other ideas, I would love the area from the back to home key to be a scroll bar when the device is in landscape mode. Grabbing the narrow on-screen scroll bar can be tricky, and the Touch Pro lacks the scroll wheel of the HTC Kaiser.
Surur
Click to expand...
Click to collapse
This can be surely done, programmatically. But I do not know if you can control the scrolling of other applications. The latter seems to me difficult?
Anyway, when a lot of applications are going to use gestures using the capacative areas, there will be going conflicts (different programs reacting differently on different gestures).
For the locking application I want to made, I see also some different gestures possibilities:
- 3 taps for locking/unlocking
- swipe left to right for Power off
- swipe right to left for starting a configured application
And I am sure I can come up with other gestures and actions....
drvdijk said:
Have been looking into this myself as well. The only code I found was managed C#. Do you think we can use this in our native C code? Looks promising though!
Click to expand...
Click to collapse
Actually I started with C++ and had also a working Proof Of Concept. However, because I am new to Windows Mobile Programming, I also wanted to use C# as next project. I have developed programs in a lot of languages (also in C++ and C#), but I like C# more. And I wanted to do this now for Windows Mobile, to get experience with this. Note that the C# sample is using only .NET 2.0, so you do not need .NET 3.5.
You can find a C++ sensortest program, which was available on Scott's weblog:
http://scottandmichelle.net/scott/cestuff/sensortest.zip
ZuinigeRijder said:
This can be surely done, programmatically. But I do not know if you can control the scrolling of other applications. The latter seems to me difficult?
Click to expand...
Click to collapse
I dont know if you can manipulate the scroll bar of another application directly (though this would be ideal) but at the least maybe a page down keystroke could be sent to the active window.
Surur
I have an idea that I think is unique; I can't seem to find anything related to it on xda or google, so forgive me if this already exists and is just too obvious for me to find it. Also I’m not sure if this is posted in the appropriate place since I’m not actually offering anything other than a simple idea. I am not a programmer and would have not way of testing or implementing this concept.
I often find myself repeatedly hitting little check boxes and links on my Windows phone. Even on a perfectly calibrated screen, it can be difficult for my fat finger to find the right spot. I particularly have problems with X/OK button and the Start menu at the top corners of the screen. I’m assuming that soft-buttons, text fields, etc in windows mobile have a defined border that accepts touch input. If the screen detects your touch outside of this box, it will not register. I propose a software solution to this.
I’ve included a simple illustration that hopefully makes this clearer. Also, anyone feel free to tell me this won’t work, that it’s already been done, etc. Rather than having a single box that is awaiting a single touch input, imagine if there were dozens of boxes surrounding the soft-key, each with an assigned value. As the boxes radiate out, the values would decrease. Input happens when the values add up to a predefined amount, which equals a touch. This way, if you click close to the box, but not quite, the screen will register where you are actually touching and make a decision (by adding up the values) of where you were actually trying to touch.
Hopefully the picture helps. I mentioned my lack of programming ability, and that applies to graphic design as well
All feedback is appreciated, and if anyone has the skills and knowledge to do this, let me know if you’re interested. I’d love to see the results.
That's pretty smart, actually; sort of like making our resistive touchscreens emulate capacitive ones.
I am another person who feels this is rather clever.
Sadly i am too a bit naff at programming :/
Thanks for the encouragement guys. I've made a better mock up now that I'm at home and have access to something besides MS Paint. I'm hoping to run across someone with the know-how, willingness, and energy to work up a proof-of-concept.
As a clearer example, in the new image, the red circles could equal 50, the green squares 25, and the blue squares 10. An equation taking sensitivity into account would be better (hard touch equals higher value with a multiplier for the closer circles). Say 100 was the thresh-hold for the screen to register a click on the box. Two reds, one red and two greens, and so on, anything that adds up to 100, would register. There could also be multiple boxes close together, each with their own set of concentric circles.
Another useful way of thinking about this is the elementary difference between accuracy and precision
http://en.wikipedia.org/wiki/Accuracy_and_precision
Screen calibration takes care of precision; I think this would provide accuracy.
Edit: I also wanted to add I was thinking of probability clouds when I came up with this. What can I say, I have a boring job.
Wow. Great idea, but I' not the one to program it! I'm surely someone will be up to the task though.
anything that makes hitting the stupid ok button easier is great in my book!
This won't work. There are no "boxes" like you speak of. The touch screen gives the OS the POINT where it was pressed. The OS converts that into pixels sees what is under the pushed pixel and selects that. Very similar to how a desktop works. The mouse only clicks one pixel and those interactive touch screen things you see at stores where you can see the moues move to where you pressed further illustrate it.
Multi Touch screens report that area that was pressed instead of just one point, but no WinMo phones have multi touch.
petard said:
This won't work. There are no "boxes" like you speak of. The touch screen gives the OS the POINT where it was pressed. The OS converts that into pixels sees what is under the pushed pixel and selects that. Very similar to how a desktop works. The mouse only clicks one pixel and those interactive touch screen things you see at stores where you can see the moues move to where you pressed further illustrate it.
Multi Touch screens report that area that was pressed instead of just one point, but no WinMo phones have multi touch.
Click to expand...
Click to collapse
That is helpful; thanks for the insight. I tried to find info on exactly how resistive touch screens worked, but it tended to be technical specs rather than how the OS used them. If it is narrowing it down to a pixel, then I see what you're saying: it won't work. If the point of contact was read as a larger, single area (as opposed to one pixel), it would be possible. Couldn't a GUI simply draw a circle around that single point? Then the area contained in that circle could be used to predict the button/icon you're trying to press using the values of the "boxes" or circles underneath.
Again, I was bored at work and was thinking about how hard it is to hit the OK button sometimes. Oh well, it killed about 2 hours
Yesterday I purchased a HD2 also called Leo, running original WWE ROM from HTC
I have installed several apps including Sloved dictionaries, Lingosoft dictionaries.
Some are in "touch mode" version, some are not. Those apps who are NOT in touch mode, are virtually impossible to operate, due to the new screen. Small Icons and scroll down menu are almost impossible to "touch" they never give the correct results.
Leo seems NOT very compatible. The reason, I guess, is the new screen type: it it different, it is similar to iPhone. They call it resistive screen.
Both iPhone and HD2 you cannot use stylus or pen (simply the screen does not react). Both cannot use the nail of the finger (it does not react).
The thumb and the finger tip areas (which is the only area which can input into the device) are too gross and wide to be precise....
You need to use the soft part of the finger (I guess in English it is called finger tip, or end of the finger), below the nail, in order to have the screen react to your inputs.
I have tried many times: in my software the small icons on top bars, and all scroll down menus ARE TOO SMALL to be tipped with finger tip or thumb tip.
They cannot accessed, or they give wrong results or you need tens of attempts to get it right. Most of the time inputs are not responsive, sometimes they are, with unpredictable or wrong results (for example you open phone ring scroll down menu and click on a ring type "A" and the phone interpret as ring type "C")
This is terrible...altough I admit the 4.3" screen is awesome and superb...What can be done?
1. is there an application which restore or adjust the screen sensibility so that it can be used with NON-TOUCH softwwares?
2. or are all developers going to release new touch-friendly version of their software...suitable to this type of screens?
Thanks a lot
Saulo
saulo866 said:
1. is there an application which restore or adjust the screen sensibility so that it can be used with NON-TOUCH softwwares?
Click to expand...
Click to collapse
You can try pinch zooming.
saulo866 said:
2. or are all developers going to release new touch-friendly version of their software...suitable to this type of screens?
Click to expand...
Click to collapse
They will, but it may take some time and won't happen overnight. They will have to do it to stay alive because of WM7 compatibility requirements.
It may be a (huge) inconvenience for some users like you, but it's a trend that won't be reversed.
Congrats on the new handset.
saulo866 said:
Leo seems NOT very compatible. The reason, I guess, is the new screen type: it it different, it is similar to iPhone. They call it resistive screen.
Click to expand...
Click to collapse
The screen on the HD2 and the iPhone is capacitive, not resistive.
saulo866 said:
Both iPhone and HD2 you cannot use stylus or pen (simply the screen does not react). Both cannot use the nail of the finger (it does not react).
Click to expand...
Click to collapse
You can use a special kind of stylus, I believe some people have bought one for the iPhone on ebay. Also, HTC has patented a magnet tipped stylus which will work on capacitive touchscreens. As the HD2 is built with a 4.3 inch screen I don't think there will be much problems.
I can use my X1 without a stylus just fine.
Is it totally impossible to manage tiny acreen elements?
Is a conductive (metal) "stylus" possible?
Thanks
zolom said:
Is it totally impossible to manage tiny acreen elements?
Is a conductive (metal) "stylus" possible?
Thanks
Click to expand...
Click to collapse
A conductive stylus should be possible. Apparently, you get conductive plastics, which are used to package up ICs (integrated circuits), something like could work. But would would need to find a way to make it into a rod somehow. Would be expensive I imagine.
The are capacitive styluses on eBay. They are also quite cheap. However, their tips are quite large compared to a resistive stylus.
I'm going to experiment a little bit when I get my HD2 (hopefully on Friday).
But to be honest, I can use my finger for almost everything on my X1. And that was a tiny screen compared to the HD2. So I don't see the problem. Seems like a lot of people are making a fuss over nothing.
I tried to use morph gear on mine and NONE of the buttons work at all.
I guess the use of capacitive screen is only advantageous if and only if the OS and applications are designed for it. Window mobile would not be able to enjoy this benefit now. I hope WM7 would change that.
madindehead said:
A conductive stylus should be possible. Apparently, you get conductive plastics, which are used to package up ICs (integrated circuits), something like could work. But would would need to find a way to make it into a rod somehow. Would be expensive I imagine.
Click to expand...
Click to collapse
HTC have licenced one already...
DinoZ1 said:
HTC have licenced one already...
Click to expand...
Click to collapse
They have filed a patent yes. They haven't made it yet tho. Certainly not to the general consumer.
That's B.S
If you use softwares from 1996 then sure, it won't be finger friendly.
Almost all software from recent year are finger compatible.
I just went through all the software installed on my touch HD, from about 30 software installed zero are not finger friendly. The only thing I have non finger friendly is some of the WM6.1 screens.
madindehead said:
A conductive stylus should be possible. Apparently, you get conductive plastics, which are used to package up ICs (integrated circuits), something like could work. But would would need to find a way to make it into a rod somehow. Would be expensive I imagine.
The are capacitive styluses on eBay. They are also quite cheap. However, their tips are quite large compared to a resistive stylus.
I'm going to experiment a little bit when I get my HD2 (hopefully on Friday).
But to be honest, I can use my finger for almost everything on my X1. And that was a tiny screen compared to the HD2. So I don't see the problem. Seems like a lot of people are making a fuss over nothing.
Click to expand...
Click to collapse
No, no one is making a fuss. I hate the stupid posts of "visible dot matrix in the screen, HD2 is slower than other phones, HD2 has no video out and so on". But I quite get the feel of problems the poster is trying to address. You didn't get the point here, X1 is with the typical resistive screen, it is entirely different when you operate on a capacitive screen, and it is not about the size of the screen. I now start to worry about the 3rd party apps as I've been relying on many apps with my Touch HD. I really hope somehow the software developers will come out with apps exclusively support HD2 capacitive screen!
I don't understand .. sure, it's harder to press small elements. But even now a lot of software is finger friendly, and the trend will only get stronger. Actually I use only fingers with my current X1, I use stylus like once per week, since some parts of WM 6,1 can't be used well with fingers.
Is there some other problem ? What do you mean by exclusive HD2 support ?
newuser888 said:
I guess the use of capacitive screen is only advantageous if and only if the OS and applications are designed for it.
Click to expand...
Click to collapse
For me personally, and, I believe, for many others, the major advantage of a capacitive screen is the glass screen surface and no need to use those stupid screen protectors anymore. I don't use outdated apps with tiny elements though, so it's not a big deal for me. If you are tied to them for some reason then it's a different story I guess...
well it doesnt need to be exclusiveto the hd2... just finger friendly would do the trick... I use my stylus only on some drop-down menus...
Exemple of applications which are NOT working??
I got mine few minutes ago, I am using it, and I dont have ANY problem with tiny elements, maybe sometimes you need to click 2 times but nothing. 0 problems for me.
This device is fracking awesome.
precsmo said:
No, no one is making a fuss. I hate the stupid posts of "visible dot matrix in the screen, HD2 is slower than other phones, HD2 has no video out and so on". But I quite get the feel of problems the poster is trying to address. You didn't get the point here, X1 is with the typical resistive screen, it is entirely different when you operate on a capacitive screen, and it is not about the size of the screen. I now start to worry about the 3rd party apps as I've been relying on many apps with my Touch HD. I really hope somehow the software developers will come out with apps exclusively support HD2 capacitive screen!
Click to expand...
Click to collapse
I did get the point. He said small menus are hard to press without a stylus.
I am asking why he finds this, as with a bigger screen (same resolution) the menus are now bigger. If I can use a small menu with my finger on the X1, the SIZE of the icon will be bigger on the HD2 (given the increase in screen size).
I wasn't saying that capacitive and resistive react the same way to a finger press. All the apps need, is to become finger friendly.
They won't react any differently on the HD2. Unless you have a drawing application you use, in which case that will be different.
But my original point still stands. The icons shouldn't be any harder to press on the HD2 as they will be bigger than on an X1 (I have smallish hands, but quite chunky fingers. I have press icons on the X1 fine, so I'm not worried about them on the HD2).
Even with big fingers, it's just a matter of skill. The phone detects center of pressed area and it always sends single point to the application. It does not mean that you can't press very small element with big finger, it just may be harder to hit.
I recommend simply trusting the device, not trying to do anything special ..
let me clarify what I said: let me make some more examples to make you understand what huge discomfort this "otherwise awesome screen" is giving to me:
try for example, (on any HD2) to do the following:
settings > input > options > try to change default zoom level from 200% to 100% (you need to access zoom scroll down menu)...I have tried for 20 times and I failed...sometimes I get 300% sometimes I get 75%...no way you can select the right level.
No way you can use your nails (since the settings are in a small area)
any other settings in which you need to select a choice from a scroll down menu results in a pain and several attempts...
In this condition even the internal settings on wm 6.5 are hard to accomplish...better to shift back to HD1 or to iphone, whose software is simplified enough to make the use of thumbs finger possible
saulo866 said:
let me clarify what I said: let me make some more examples to make you understand what huge discomfort this "otherwise awesome screen" is giving to me:
try for example, (on any HD2) to do the following:
settings > input > options > try to change default zoom level from 200% to 100% (you need to access zoom scroll down menu)...I have tried for 20 times and I failed...sometimes I get 300% sometimes I get 75%...no way you can select the right level.
No way you can use your nails (since the settings are in a small area)
any other settings in which you need to select a choice from a scroll down menu results in a pain and several attempts...
In this condition even the internal settings on wm 6.5 are hard to accomplish...better to shift back to HD1 or to iphone, whose software is simplified enough to make the use of thumbs finger possible
Click to expand...
Click to collapse
Just carry a laptop round with you that has MyPhone installed on it and use that. Simple!
We all know that multitouch is capable on the popular G1 and myTouch. Now I was wondering if adding such a feature onto the virtual keyboard is a can-do. All for the sake of exponentially increasing text insertion speed.
I don't see a reason to use multitouch for text input. What should happen if you enter 2 keys at the same time?
MarcLandis said:
I don't see a reason to use multitouch for text input. What should happen if you enter 2 keys at the same time?
Click to expand...
Click to collapse
the point of multi-touch on the vk is to increase the speed of texting meaning u can press a key directly after another without fear of the keys not registering. it really helps when holding the phone sideways because when text i start texting too fast and keys dont register correctly. thats y im still partial to the hard keyboard.
MarcLandis said:
I don't see a reason to use multitouch for text input. What should happen if you enter 2 keys at the same time?
Click to expand...
Click to collapse
The reason for multi-touch is simple... take a look at the iPhone, if you hit one key and then before releasing it hit another it registers both hits. So that way you can type much quicker! Try this on the android/htc/better keyboards and you'll see that if you hit two keys at the same time, it will register a key that is almost always half-way in between the two.
However, I think Google is having a hard-time coding for not simultaneous taps but for timing. Meaning that if you hit both the 'K' and the 'N' keys at the same time while trying to type the word 'KNOW', the software not only has to recognize that 2 keys were hit; but has to resolve which one was hit first or was likely meant to be hit first. So that way, it can say
"hey, he hit the 'K' and the 'N' at virtually the same time; BUT, because he hit the 'K' .00002 seconds before the 'N' I'll put register and display the 'K' before the 'N'"
Multi-touch in the browser is probably not easy to code for but it certainly is much easier than the keyboard because pinching only requires the software to recognize that two fingers are on the screen, not that one was there before the other.
But, I think Google needs to work on the usability of the keyboard first. The screen-size on the magic and keyboard might restrict them somewhat but damn the virtual keyboard layout is verry bad... I always hit the "M" key when trying to hit the "DELETE" key.. And why not auto-popup the keyboard when you enter messaging? and why is there the "smiley" key in messaging? WASTE OF SPACE?!?
I thought the HTC keyboard sorta-of had multi-touch support, no?
How does one "sorta" have multi-touch support?
I would love to see this. My biggest problem is not registering a space in between words because I hit it too quickly and then the autocorrect can't fix the issue. Maybe a 3rd party keyboard developer would be interested in incorporating this into their app?
I believe better keyboard has multi touch.
exile20 said:
I believe better keyboard has multi touch.
Click to expand...
Click to collapse
It does not, unfortunately.
TonyDeez said:
How does one "sorta" have multi-touch support?
Click to expand...
Click to collapse
I think I only got it working with the bottom row of keys.
I can't fathom how one would get the Dream/Magic (G1/myTouch3G) to have a fully functional multitouch keyboard. The multitouch capacity of these devices is hackish to say the least; if the horizontal or vertical coordinates of the touched points coincide to within a rather wide range (comparatively speaking) then the device is incapable of registering more than one touch -- and it wouldn't necessarily be /either/ of the points originally touched.
That would seem to me to be a game-breaker.
Unless I misunderstand? Perhaps the Droid or Cliq are different.
IConrad01 said:
The multitouch capacity of these devices is hackish to say the least; if the horizontal or vertical coordinates of the touched points coincide to within a rather wide range (comparatively speaking) then the device is incapable of registering more than one touch -- and it wouldn't necessarily be /either/ of the points originally touched.
Click to expand...
Click to collapse
Reading this got me curious so I went back to Luke Hutchison's blog posts on the matter and played around with his multitouch demo apps here and it looks like there are indeed problems. I then found this post which explains his observations on the matter.
Even with these limitations, though, it's hard to say if there would be much of an issue. I think this "rather wide range" you speak of is small enough. The QWERTY keyboard layout was designed to spread out keys to minimize "jams" of neighboring keys. This works in our favor, making the distance between possible close-to-simultaneous keypresses rather large on average. If I play with the virtual keyboard a little bit, I notice that if my fingers are hitting neighboring keys I don't have problems with simultaneous presses because I have to move my first finger out of the way to make room for the second. I do have unusually large fingers, but give it a try yourself.
Who knows though...it may indeed be too inaccurate.
Also, it looks like there's a similar thread to this one over here.
The trouble, as I understand it, is that you could not touch two points on the same horizontal "read" line of the device, at the same time. You could probably do top row and bottom row as multitouch, but not middle row and anything else. (Assuming three rows total.)
It's not just about touching two keys simultaneously but that if the same capacitors are triggered horizontally, then the device will read this as one -- confused -- input. And if the same capacitors are triggered horizontally, the same will occur.
It is my understanding that the Motorola Milestone's Eclair keyboard is multi-touch. Can anyone confirm that?
i can conform that there is a multi-touch keyboard. Ive actually tested it out. They rebuild the keyboard and made capable of it. I think its called HTC VK keyboard. And yes i can press 2 keys at the same time too.
I have a t mobile Touch pro 2, love the keyboard but i would rather go back to android. Its almost new if anyone is interested let me know in a pm. thanks.
If I'm not mistaken, the HTC Keyboard on the hero has multitouch.
ajones7279 said:
If I'm not mistaken, the HTC Keyboard on the hero has multitouch.
Click to expand...
Click to collapse
sorry but you are mistaken. the hero does not even have real multitouch in the driver. one finger gives a small dot, while a second finger would increase the dot size that is reported from the driver, the bigger the distance between fingers the bigger the dot size. this way the pinch-to-zoom works, but it does not actually detect a second touch.
you can see this with various application that show the touch graphically, for example cracked screen or steamy window.
Then I stand corrected. Just relaying something I heard. But doesn't mulititouch have to be written into the program? Like how Picsay had multitouch on the Droid whereas other apps didn't? Just throwing things out there.
kendong2 said:
sorry but you are mistaken. the hero does not even have real multitouch in the driver. one finger gives a small dot, while a second finger would increase the dot size that is reported from the driver, the bigger the distance between fingers the bigger the dot size. this way the pinch-to-zoom works, but it does not actually detect a second touch.
you can see this with various application that show the touch graphically, for example cracked screen or steamy window.
Click to expand...
Click to collapse
Dunno about the Hero, but the Eris definitely does have it.
Also- multitouch DOES have to be coded into the application. The driver isn't important at all if the application itself only supports one input.
Interesting new tweet by cyanogen:
@paracycle multitouch is built into keyboardview on eclair. i've backported this for the next CM-4.2 release.
Click to expand...
Click to collapse
The touch input in this device is so bad i have to use my stylus pen to browse webs(i can never touch the back page button on google chrome instead it touches the forward page button instead),close programs(touch the top of the screen and pulling it down never works), opening the charm bar(swiping my finger from the right of the screen to the left never works too).
I tried calibrating it by searching calibrate on the charm bar's search feature but they doesn't work as well.
Any way to fix this? Its getting so annoying because i can't use the touch screen feature at all because its not precise.
thekiller99 said:
The touch input in this device is so bad i have to use my stylus pen to browse webs(i can never touch the back page button on google chrome instead it touches the forward page button instead),close programs(touch the top of the screen and pulling it down never works), opening the charm bar(swiping my finger from the right of the screen to the left never works too).
I tried calibrating it by searching calibrate on the charm bar's search feature but they doesn't work as well.
Any way to fix this? Its getting so annoying because i can't use the touch screen feature at all because its not precise.
Click to expand...
Click to collapse
Dont have one myself, but I played with one at Frys, and I gotta say I didnt see any of these issues at all! Maybe you got a bad one???
thekiller99 said:
The touch input in this device is so bad i have to use my stylus pen to browse webs(i can never touch the back page button on google chrome instead it touches the forward page button instead),close programs(touch the top of the screen and pulling it down never works), opening the charm bar(swiping my finger from the right of the screen to the left never works too).
I tried calibrating it by searching calibrate on the charm bar's search feature but they doesn't work as well.
Any way to fix this? Its getting so annoying because i can't use the touch screen feature at all because its not precise.
Click to expand...
Click to collapse
Make sure your navigation gestures start from the black bezel of the Vaio then onto the touchscreen. You can use the calibration tool, change pen and touch settings, and change double clicking of objects to single tap to make the experience better. I'm not sure if the registry change to make touch more responsive for surface rt applies to your Intel tablet.
I'm with @vinscuzzy on this one... generally speaking I detest Sony products, but this sounds like a defective unit more than anything else. I'm not sure what you mean by "calibration doesn't work as well" (grammar, people: it conveys meaning). but if you can't fix this yourself, I would definitely suggest you take it back to wherever you got it.
When i use the calibration settings whenever i try to touch the cross it shows the input to be slightly on the right. i can't even close apps or use the multitasking. Closing tabs is hard or even clicking on links on google isn't accurate at all.
I bought this machine overseas and it isn't even out in my country so replacing it is too much of a hassle.
I almost considered it. But found there is a problem with the drivers, especially with Photoshop supposedly MS and Sony are using a specific driver but its not compatible with certain apps that use a different format of driver like Photoshop for touch.
The driver developers as far as I'm aware via googling don't seem interested in fixing this issue due to cost and/or it being niche market. Maybe try other software, I hope you don't have faulty system
Sent from my GT-I9100 using XDA Premium HD app