Database Users

iphone media player?

i have been searching for the iphone touch scroll and media player for the hermes 8525 phone. is there anyone working on this? also is there anyway to make the touch screen to a multi tocuh screen like the iphone.

The multi touch screen is totally different hardware, although it would be cool if there was a way...

delude said:
The multi touch screen is totally different hardware, although it would be cool if there was a way...
Click to expand...
Click to collapse
i thought so but i would think if you hack the dll file maybe there is a way to make it read multi times i dont know i am not an expert on hardware or software hacking.

I thought I heard somewhere that there might be someone working on doing something like that. given hardware constraints, it wouldn't be perfect. It would detect the space between the fingers as being pressed as well (I'm assuming), e.g. if you have fingers on the screen like this:
__........__
|__|.....|__|
it would see this:
_________
|_________|
So it would have to figure out by the shape of it where your fingers really are.
Still, I hope someone does. Multitouch would be very nice...
EDIT: due to the restrictiveness of this forum, just imagine that the periods in my ASCII art above dont exist.

That would be amazing, and something i would definately pay for. Looks like it would be like the drag box on a PC desktop. If you put two fingers on then it could drag things or select the space within.

jackbnymbl said:
I thought I heard somewhere that there might be someone working on doing something like that. given hardware constraints, it wouldn't be perfect. It would detect the space between the fingers as being pressed as well (I'm assuming), e.g. if you have fingers on the screen like this:
__........__
|__|.....|__|
it would see this:
_________
|_________|
So it would have to figure out by the shape of it where your fingers really are.
Still, I hope someone does. Multitouch would be very nice...
EDIT: due to the restrictiveness of this forum, just imagine that the periods in my ASCII art above dont exist.
Click to expand...
Click to collapse
Detecting the space between fingers would only be possible with double touch screens one on top of the other. To simulate it on the present hardware would require low-level programming to continuously scan the screen within milliseconds so that it could detect minute differences of whichever finger came in contact first. It will not detect it if both fingers pressed on the screen at exactly the same time. Theoretically it should be possible to do but that would really slow down the system just to do it that way.

for multi touch, i'm not sure how it would be useful but i was thinking, maybe it somehow "remembers" a first click, then that second click is processed. for example, the iphone zooming feature. a single click, then a second, separate clickanddrag to zoom in and out

Well, many of the features can actually be done without requiring multi touch. For example, as the screen of the phone small enough, you can actually assigning area in the viewing screen to be doing something specific. For example, on my notebook touch pad, I can assign part of the right portion to do a scroll function. Hence, it is possible to implement the dynamic zoom function on a WM (non-multi touch device) by assigning (say) right hand area to do a zooming. It wont be as cool though.

would it still be cooler than a generic scroll bar? i like to think so.

"Slide to Unlock" of a different kind - *Beta Release Available*

Summary:
A method of executing the device lock/unlock features of Windows Mobile by using the gestures available in FTouchFlo v1.4.1.
Here's a sample video of it in action courtesy of kidnamedAlbert: http://www.youtube.com/watch?v=wjPxHroy9VU
Current Status:
I've got the basics working on my device right now, and it works quite well. Beta version is now available, where I offer a choice of install methods. Since many users already have FTouchFlo and some version of the "true" HTC Cube application with my TFloCubeCtrl, then all that is needed for this is an update to version 1.2.0 of TFloControl, and an adjustment to the FTouchFlo config file. I also have a stand-alone cab installer for just FTouchFlo and the "slide 2 lock/unlock" capability. Note: there's no cube involved in this one!
Where is it?!
*NEW* CAB installer for TFloControl + FTouchFlo + config for "Slide to Lock/Unlock" with a left-right gesture now available here: http://rapidshare.com/files/128559842/TFloControl_v1.2.0___FTouchFlo_v1.4.1.cab
Be sure to check the install/usage notes in Post #4
If you've already got FTouchFlo v1.4.1 installed, and an HTC Cube using TFloCubeCtrl, then you can just download the new TFloControl.exe and FTouchFlo.config files from the attachments, and follow the directions in Post #4
What's Next?
Currently, configuration of TFloCubeCtrl is through command-line params fed by FTouchFlo. I think this could be made better, and possibly there should be a configuration app ... since all of my FTouchFlo gestures just map to calling TFloCubeCtrl anymore, which nowadays does so much more than just control the HTC Cube!
I'm currently talking with efrost about the possibility of turning TFloCubeCtrl and it's functionality into a plug-in for the newer FTouchSL application.
I wonder what other sorts of features I could build into it as additional parameters. So far I have:
Lock
{no params} - execute the device lock
home - return to the Today screen and then lock
suspend - lock, and then suspend the device
Unlock
{no params} - unlock the device
<milliseconds> - amount of delay between the simulating the left softkey, and clicking the unlock button. I added this in case different devices needed different amounts of lag time based on processor speed. 50ms seems to work quite well on my Kaiser.
Donations:
If you like what I've done, then please ... feel free to donate to me. It definitely helps in keeping me motivated to add new features and answer questions. However, if you find this function useful, you should also consider a donation to efrost ... because without FTouchFlo v1.4.1, this little project would not exist.
Props:
efrost - for making FTouchFlo!
Matt Armstrong - creator of DeviceLock, where I first saw that the unlock process could be automated
wacky.banana - for pointing out the "bug" that clued me in that unlock was possible via FTouchFlo
kidnamedAlbert - for making a video of it in action

Background
While working on a project to bring full HTC Cube finger control to non-Touch devices, I developed an application to work hand-in-hand with efrost's FTouchFlo application. In addition to being able to control the HTC Cube, I also added a few system control functions that you could map to FTouchFlo gestures. One such system control function was the ability to engage the standard device lock, with additional options for returning the display to the home screen, and also for suspending the device. I soon realized that this was a slick was to lock your device, by just sliding your finger across the screen left-to-right. However, this then still left me with the rather lame way of unlocking the device, pressing the left softkey, and then clicking on a button on the screen. I became further annoyed when attempting to unlock the screen in bright sunlight, where it's next to impossible to find the button on the screen (at least for me!).
Where is this going?
One day, I had a small revelation. Someone had previously reported a "bug" with TFloCubeCtrl, whereby you could open up the cube, even when the device was locked. I subsequently added some code to ensure that all functions were disabled if it detected that the device was locked. But while it was reported as a bug ... the indication here was that TFloCubeCtrl would receive calls from FTouchFlo even when the device was locked. I suddenly realized that this meant that I could also add functionality to TFloCubeCtrl to unlock the device, by automating the unlock procedure.
So, does it work?
In fact ... it works just the way I had hoped. Now, with the device on, but locked with the standard WinMo device lock functionality, I can swipe my finger left-to-right, and the device becomes unlocked. You don't even see the unlock screen (on my Kaiser anyway), as it's dismissed so quickly due to the automated unlock.
And why should I care?
Well, I like it because it works well for me, and solves some of the annoyances I've had in the past. Specifically, I like the HTC Home screen ... as I'm used to it's layout, and it has everything there I need. So I like to be able to lock the device with a quick action, and have it revert to the home screen upon locking. And thanks to FTouchFlo, a left-right swipe anywhere on the screen will work (no trying to hit a specific icon). Then, to unlock, just the same swipe again is all it takes. It's a simple action, and can be done anywhere on the screen as long as it's a complete swipe across the screen ... so you don't even need to look at the screen to unlock the device. And best of all, it all works *with* the standard device lock functionality ... so even if you lock with a different method (device lock on today screen), you can still "slide to unlock". Incoming calls work the same as before ... and PIN code input should also still function normally (initial tests have shown this to be true!)

Here are some thoughts I've come up with on possible features:
Specify an X,Y to simulate a mouse click after the Today screen is shown. (In order to ensure a particular tab is also displayed)
Specify a particular application to be displayed before locking, instead of the Today screen
Vibrate when the device is unlocked (DeviceLock offered this when "easy unlock" was enabled)
Specify a particular application to be displayed after unlocking

Installation / Usage Notes
General Usage Warnings -
This app requires FTouchFlo. As such, installing this will subject your device to known FTouchFlo "issues"
Once FTouchFlo is running, it cannot be stopped without a soft reset
While FTouchFlo is running, the Transcriber SIP and Screen Alignment utility cannot be used
Some programs that are "finger friendly" themselves do not work well with FTouchFlo, and should be added to the Exclusions list in FTouchFlo.config. Some common known apps are already in the list.
After a soft reset, you must manually start FTouchFlo before you can "Slide to Lock/Unlock". Alternatively, you can create a shortcut to FTouchFlo in your StartUp folder.
CAB Install Method -
Install the CAB file on your Windows Mobile device
Be sure to install to the Device (not a storage card)
Run FTouchFlo, found under Start->Programs
Perform a left-right slide gesture to lock the device
Perform the same left-right slide gesture again to unlock the device
Enjoy
File Install Method (Advanced Users Only) -
Use this method if you already have FTouchFlo installed, and/or if you have an HTC Cube install already on your device using TFloCubeCtrl
Copy TFloControl.exe into a \Program Files\TFloControl folder
Update your FTouchFlo.config file to reflect something similar to my sample
TFloControl is the new name for the app, replacing the old TFloCubeCtrl (it does more than control the cube!)

Morning Kona. I see you have decided to go public on this, which is great!
A couple of points from me:
One of the things you are going to have to watch out for , as you develop this tool, is getting the tool to work in a consistent and predictable manner with the inbuilt WM6 pin lock facility.
Because I am security conscious, I have pin lock initialise itself half an hour after locking the device either with device lock or Slide-To-Unlock (S2U2). When using S2U2 I have found that if a call comes in after pin lock is engaged, trying to answer the call can cause unpredictable results ranging from the call being successfully answered, to S2U2 to being presented with the pin lock keyboard to unlock the device before the call can be taken, to the call being dropped altogether.
This behaviour became such a pain that I dropped S2U2 altogether in order to get a consistent method of answering calls when the device is locked in this way, ie with device lock and pin lock in operation. I note this is an area you have not tested yet, hence me advising caution here.
Another point from me: I am assuming that your lock will not work unless a version of Ftouchflo is installed? If yes does that mean that people like me who have given up on Ftouchflo and the Cube will not be able to use your tool?
Final point; early days yet but have you thought of integrating your tool with the organic lock invented by someone on here?
Hope you find these points helpful. More than happy to undertake some testing for you if you let me know what is required, etc.
Cheers
WB

will this be a lot like the unlocking mechanism from wm 7 in which you have to slide a certain way so the device unlocks. A bit confused as far as function though. I am glad you are starting a new project...

I can not say how much i'm interested in such software, even though i dont pin lock my device, but i really like to lock it cause it many times make a call or opens and drains the battery without any need..
any way .. i'm waiting .. and i believe it's gonna be great
cheers

WB,
Thanks for the input. So far ... here's what I can tell you:
wacky.banana said:
One of the things you are going to have to watch out for , as you develop this tool, is getting the tool to work in a consistent and predictable manner with the inbuilt WM6 pin lock facility.
Because I am security conscious, I have pin lock initialise itself half an hour after locking the device either with device lock or Slide-To-Unlock (S2U2). When using S2U2 I have found that if a call comes in after pin lock is engaged, trying to answer the call can cause unpredictable results ranging from the call being successfully answered, to S2U2 to being presented with the pin lock keyboard to unlock the device before the call can be taken, to the call being dropped altogether.
This behavior became such a pain that I dropped S2U2 altogether in order to get a consistent method of answering calls when the device is locked in this way, ie with device lock and pin lock in operation. I note this is an area you have not tested yet, hence me advising caution here.
Click to expand...
Click to collapse
Since what I've done here is devise a way to use gestures as a way to interact with the standard built-in Windows Mobile locking mechanism, we should be OK here. My initial tests are indicating that everything functions predictably when PIN locking is enabled. My unlock gesture works when the PIN is not yet enabled. And once the PIN screen appears, the unlock gesture basically doesn't do much ... and you have to enter the PIN to access the phone. Incoming calls are unaffected, as the standard WinMo "Incoming Call" screen appears, and a SoftKey press will still answer without requiring an unlock. This is where people's desire for functionality is probably going to differ.
wacky.banana said:
Another point from me: I am assuming that your lock will not work unless a version of Ftouchflo is installed? If yes does that mean that people like me who have given up on Ftouchflo and the Cube will not be able to use your tool?
Click to expand...
Click to collapse
Yes ... and no. FTouchFlo is currently required, as this project is intentionally a solution to work with FTouchFlo. However, the cube is not a requirement ... it doesn't even have to be installed.
wacky.banana said:
Final point; early days yet but have you thought of integrating your tool with the organic lock invented by someone on here?
Click to expand...
Click to collapse
I have downloaded Organic Lock, and will test it out. My initial thoughts ... are that it should integrate quite well with what I've done here, since it's designed to work with the built-in WinMo device locking. I'll post my results when I get to test it out.

domineus said:
will this be a lot like the unlocking mechanism from wm 7 in which you have to slide a certain way so the device unlocks. A bit confused as far as function though. I am glad you are starting a new project...
Click to expand...
Click to collapse
Perhaps ... I honestly haven't seen what WM7 is offering. In a nutshell, what I've done here will allow you to use any of FTouchFlo's gestures to lock/unlock your device using the built-in WM6 device lock. Current FTouchFlo gestures are up-down, down-up, left-right, and right-left. You basically sweep your finger across the entire length of the screen in one continuous motion. It takes a bit of getting used to, but I get it to recognize my gestures about 95% of the time these days.

solomhamada said:
I can not say how much i'm interested in such software, even though i dont pin lock my device, but i really like to lock it cause it many times make a call or opens and drains the battery without any need..
any way .. i'm waiting .. and i believe it's gonna be great
cheers
Click to expand...
Click to collapse
I currently don't really use the PIN lock feature myself ... but your scenario of the phone accidentally waking up and doing things unintentionally is a big reason I started using the device lock to lock my phone. But when I got annoyed with the unlock procedure, I wrote the "slide to unlock" part, which is really useful (to me). This is really more of a convenience feature that a real security measure. But it makes the device lock/unlock very easy to use. I just put it on my wife's phone, because her phone kept calling people while it was in her purse!

Slide to Answer
I just had a thought ... and tested it out. You can actually "Slide to Answer" as well, when a phone call comes in.
As is true with unlock, the softkey method still works ... however, if the device is currently locked, and a phone call comes in ... if you perform the unlock gesture, TFloCubeCtrl will try to initiate the unlock by pressing the left softkey, which in turn answers the call! It's really a side-effect in this case ... but it works! Interesting ... but it would probably be more useful if I could disable the on-screen buttons, and require either a hardware keypress, or the slide gesture.

Kona_Mtbkr said:
..... It takes a bit of getting used to, but I get it to recognize my gestures about 95% of the time these days.
Click to expand...
Click to collapse
Hey Kona,
Thanks for the comprehensive response to my points. The tool looks more promising every time I hear from you.
To the point about 95% accuracy this isn't too bad and, from my experience, probably on a par with S2U2. When I was playing with TouchFlo in the early days I found you could increase the consistency of the gestures by changing the sensitivity response or whatever it was called.
When are you expecting to have a beta version of the tool out for testing then?
Cheers
WB

wacky.banana said:
Hey Kona,
Thanks for the comprehensive response to my points. The tool looks more promising every time I hear from you.
To the point about 95% accuracy this isn't too bad and, from my experience, probably on a par with S2U2. When I was playing with TouchFlo in the early days I found you could increase the consistency of the gestures by changing the sensitivity response or whatever it was called.
When are you expecting to have a beta version of the tool out for testing then?
Cheers
WB
Click to expand...
Click to collapse
Yes ... changing the sensitivity settings was key for really making FTouchFlo useful. It's a balancing act between the pressure sensitivity, and the gesture delay ... which controls how long FTouchFlo waits before deciding that you're not actually doing a gesture, so it forwards the input on to the OS. It makes it a bit trickier to try to use scrollbars or to do other dragging operations (like selecting multiple items) when FTouchFlo is in use. Not sure if FTouchSL has improved on any of these items.
As for release ... we'll see how the weekend goes. It'll be easier for me to post the new app, and a sample config for those who already have FTouchFlo and an HTC Cube install with TFloCubeCtrl. But I know that isn't going to cut it ... so I'll put a "fresh install" cab together as well.

Kona,
Good idea putting an all-in-1 cab together for an easy install otherwise all you will get is a thousand questions on how to install the app and what other linked apps are required. Probably a major distraction if what you really want to know is how the user experience is progresing.
Re the sensitivity compromise, have you had a chat with Efrost as to where his latest version of Ftouchflo is now at, from a technical perspective?
This thread is now on my auto notify list, ready for your next move.
All the best.
WB

im completely interested but does this have a transparent background on the home screen like the original windows unlock screen?
if so, this if EXACTLY what im looking for.
a lock on wakeup feature would be great too.
thanks,

wacky.banana said:
Kona,
Re the sensitivity compromise, have you had a chat with Efrost as to where his latest version of Ftouchflo is now at, from a technical perspective?
Click to expand...
Click to collapse
Well, I have contacted him through PM here ... and asked about the plugin architecture for FTouchSL, to see if he'd let me rebuild my TFloCtrl app as a plugin. He seemed to be receptive to the idea ... but I haven't heard much from him since. I'm pretty sure the free version of FTouchFlo isn't going to progress past v1.4.1 ... as all efforts are now on FTouchSL. It's only like $15, so I'll probably buy a copy at some point. efrost deserves our support! Of course, I was hoping he'd give me a license for developing my plugins against, and then I could buy a copy for my wife!
I need to get a bit more insight into his plugin architecture too, however. I'm not completely sure that everything that I've done so far with TFloCtrl will work in his plugin architecture. We'll have to see.

sounds lije it will be awesome...when developed of course. i am really into being able to lock my device easily and be something i can unlock without much thought or having to look at the keyboard whilst i enter an alpha-numeric code. kinda biometrics like without the fingerprint scanner. thanks for the info and i am waiting for more news.

kidnamedAlbert said:
im completely interested but does this have a transparent background on the home screen like the original windows unlock screen?
Click to expand...
Click to collapse
Yes, in fact, TFloCtrl has no background ... or window at all. It's more of a windowless process, that sets the display to the Today screen, locks the device, and exits. You're left at the Today screen with a locked device. Hmm, that gives me an idea for a feature, bridging between another app I'm working on. An option to also simulate a click on the Today screen, to ensure a particular tab is selected upon locking.
kidnamedAlbert said:
if so, this if EXACTLY what im looking for.
a lock on wakeup feature would be great too.
thanks,
Click to expand...
Click to collapse
Well, to put in a lock on wakeup feature would require a whole separate application. At that point, I'd almost be rebuilding armstrong's DeviceLock. You should take a look at this, as I was running it for a while for just that feature. It should work just fine with my app, because he is also using the normal built-in lock functionality. He also had an "easy unlock" feature that only required the softkey press ... but it was too "easy" for me. The swipe gesture is much less likely to occur accidentally, but still can be completed without even looking at the screen! That's the biggest benefit in my mind.

Daremo_23 said:
sounds lije it will be awesome...when developed of course. i am really into being able to lock my device easily and be something i can unlock without much thought or having to look at the keyboard whilst i enter an alpha-numeric code. kinda biometrics like without the fingerprint scanner. thanks for the info and i am waiting for more news.
Click to expand...
Click to collapse
"biometrics without the scanning" ... that's a pretty good way to describe it
I think it nice, because it offers the protection from accidental button/screen presses of the device lock, but with easier unlocking ... as you said, not having to look at the screen. But in addition, I'm also hoping it'll pair well with Organic Lock, to offer the additional security that people like WB are looking for.
And as far as "developed" goes ... it's already working on my device! I'm just thinking about what features to include for a Beta 1 release ... and also I need to invest the time to put together the installation ... or else the thread will fill with "how to install?" postings. I learned my lesson last time with the TFloCubeCtrl thread.

Just an idea, stolen from the Android platform.
You could make the unlock gesture user-customizable. Maybe there could be an interface in the settings for users to "draw" their unlock gesture and practice on it. Then, if someone wants security without a password, he can use a complex gesture.
edit: That was a horrible explanation, haha, you'll get the point from this video:
http://www.youtube.com/watch?v=arXolJrLVEg

[APP REQUEST] MULTI TOUCH ON DIAMOND's Capacitive sensor {Need Developers}

since diamond/fuze has the Capacitive sensor (i'll call it CAPSEN from now on) ...and a seperate touch screen...
why not combine to have multi touch.....maybe you already heard this from me or someone else..but i thought i bring it up anyway...
just like the "PINCH" from iphone....
but 1 finger on the touch screen...and 1 finger on the CAPSEN....doing the PINCH...should zoom out...and zoom in...
On a Picture....
Browser...
Notes...
any other app that has zoom function
and use it as an APP LAUNCHER....for instance...
TOUCH and HOLD the Centre button with the thumb...and swipe UP on the touch screen...brings up dialer?? app launcher?? Voice command??
maybe not just app...but shortcut for Tools...such as
copy/cut/paste/
back/forward (browser)
next/previoius(media)
this is all i can think of now...cuz i'm sleepy so I will come up with a bigger list when i'm awake and fresh....
peace
SolidKundi

+1
thought about the same just a day ago

Nice idea, I know there has been talk of multi touch on just the screen, but that is very complicated since if you touch two points on the screen it will actually read the midpoint of the two spots.
Your idea would work like holding a shortcut combo ie: Ctrl + C = Cut
But on the phone we could touch the end call button and the screen and as you move it would zoom out......and enless other ideas!
GScroll uses the touch pad on the bottom and you can assign stuff, but not with the screen....I bet that wouldn't be to hard for the programmer to figure out......

noellenchris said:
Nice idea, I know there has been talk of multi touch on just the screen, but that is very complicated since if you touch two points on the screen it will actually read the midpoint of the two spots.
Your idea would work like holding a shortcut combo ie: Ctrl + C = Cut
But on the phone we could touch the end call button and the screen and as you move it would zoom out......and enless other ideas!
GScroll uses the touch pad on the bottom and you can assign stuff, but not with the screen....I bet that wouldn't be to hard for the programmer to figure out......
Click to expand...
Click to collapse
There should be more apps that take advantage of the pad at the bottom just sumthing simple like scroling clockwise and anticlockwise round the ok button to zoom in n out like you can on the txt msg screen would be a gr8 improvement

+1
Was thinking about this too..
What's on my mind was touching the panel to simulate "Shift" and "Ctrl" keys. Hence to be used together with the keyboard to provide functions like "Copy/Cut/Paste" (Ctrl+C/X/V), "Select All" (Ctrl+A), and also to capitalize a letter with the "Shift" function...
If it could be done, i'm sure it will be household program on every Diamond... hmm...

mmm Good Idea!!

!!!!!!!!!
but yah...also i just remembered ..that the CAP sensor is also multitouch.??? ...i remember seeing a youtube vid about that...
if thats the case..we can do so much...like the pinch effect right on the cap sensor....or swipe with two fingers....ahhh the endless features this will give us...every other phone will bow down.....
even touchdiamond2

solidkundi said:
but yah...also i just remembered ..that the CAP sensor is also multitouch.??? ...i remember seeing a youtube vid about that...
if thats the case..we can do so much...like the pinch effect right on the cap sensor....or swipe with two fingers....ahhh the endless features this will give us...every other phone will bow down.....
even touchdiamond2
Click to expand...
Click to collapse
Indeed, just zoom with two fingers at the mulititouch panel! That's great!
It should be possible to make this app, because they have that kind of application on the blackstone too! (they made an application that makes the bottom panel like a zoom bar, just like the topaz)
I'd donate if it someone makes this application!

[ElCondor] said:
Indeed, just zoom with two fingers at the mulititouch panel! That's great!
It should be possible to make this app, because they have that kind of application on the blackstone too! (they made an application that makes the bottom panel like a zoom bar, just like the topaz)
I'd donate if it someone makes this application!
Click to expand...
Click to collapse
I say the same thing..
multitouch for diamond I think is possibile..like this app nobody thought could exist [sorry 4 english]

I was think about it 2 months ago. Not multitouch the captive + screen, But multitouch on captive only (there is video that the captive sensor on diamond was multitouchable ).
I was interested with this idea, but I can't find any sample code for captive sensor (I found some accelerometer sample code), Is there any good reverences/sample code about how to get captive sensor signal/messages with C++?
( I was interested to code it, but not promises to create it )

i wish this actually goess throughhhhh but....we need more support from the rest of the forum users....i guess i have to make this TItle more appealing..hehe

amarullz said:
I was think about it 2 months ago. Not multitouch the captive + screen, But multitouch on captive only (there is video that the captive sensor on diamond was multitouchable ).
I was interested with this idea, but I can't find any sample code for captive sensor (I found some accelerometer sample code), Is there any good reverences/sample code about how to get captive sensor signal/messages with C++?
( I was interested to code it, but not promises to create it )
Click to expand...
Click to collapse
Actually TouchLockPro uses the NavSensor and is written in C++. You can couple commands to capacitive swipes, 8 in total. Also I did make the source code available on sourceforge.

sounds good...I can only do photoshop....i'll try to help anyway i can......
i really would love to have Multitouch on my Diamond.
This will be groundbreaking.....even diamond 2 can't touch this..i think....anyways..
@ZuinigeRijder ---thanx

ZuinigeRijder said:
Actually TouchLockPro uses the NavSensor and is written in C++. You can couple commands to capacitive swipes, 8 in total. Also I did make the source code available on sourceforge.
Click to expand...
Click to collapse
Ok hanks... I will check it...

any (good) news?

I'd love to help
I would love to help but.....
I don't know any programing or any photoshop, can someone teach me something? I really want to help the community but I don't know how

multi touch not really multi touch
I might be wrong but i was thinking that the diamond doesn't actually have multi touch, it's more like having 4 touchpads that all work at the same time. The left part with the home and the dial button, the wheel, the center button, the right section with the back and end call buttons. That may explain why the touch interface is so slow...

[APP IDEA] App Start by tilt plus touch

Hey Everyone!
I'm sure most of you have, like me, spend quite some time on trying different shortcuts for starting your favorite application.
Of course I changed the two softkeys on the start menu and installed an iphone-like launcher (Launchpad) but thats not good for the "heavy-used-apps".
I tested lots of little helpers like
G-Trigger (where you accelerate your device e.g. from left to right to start an app)
or
Butler (which lets you start apps by stroking from one hardware button to another)
or
GScroll (which is my favourite, you can assign different apps for touching the hardware buttons, but which has the problem that you often incidentally start an app)
Now I had an idea for a sounds-great-to-me helper:
To start an app, you touch (not press) the center button and tilt the device at the same time. Like gScroll this would make it possible to start many different programms with combinations like two times left or left and up or ...
while the likelihood of incidentally starting an app is low since you seldom have your finger lying on the center button.
Does anyone of you guys has the knowledge to make a workable program or to edit your already existing program to do this?
Or, am i just stupid and there already is such a great app, and all of you guys are already using it
Well, thank you, and Tschüß from old-germany..
JackWiDu

jackwidu said:
Hey Everyone!
I'm sure most of you have, like me, spend quite some time on trying different shortcuts for starting your favorite application.
Of course I changed the two softkeys on the start menu and installed an iphone-like launcher (Launchpad) but thats not good for the "heavy-used-apps".
I tested lots of little helpers like
G-Trigger (where you accelerate your device e.g. from left to right to start an app)
or
Butler (which lets you start apps by stroking from one hardware button to another)
or
GScroll (which is my favourite, you can assign different apps for touching the hardware buttons, but which has the problem that you often incidentally start an app)
Now I had an idea for a sounds-great-to-me helper:
To start an app, you touch (not press) the center button and tilt the device at the same time. Like gScroll this would make it possible to start many different programms with combinations like two times left or left and up or ...
while the likelihood of incidentally starting an app is low since you seldom have your finger lying on the center button.
Does anyone of you guys has the knowledge to make a workable program or to edit your already existing program to do this?
Or, am i just stupid and there already is such a great app, and all of you guys are already using it
Well, thank you, and Tschüß from old-germany..
JackWiDu
Click to expand...
Click to collapse
Not exactly what you asked for. With TouchLockPro you can couple 8 commands to NavSensor moves and 4 commands to Gsensor orientation moves. But of course, in the first place it is a locking application.

Leo NOT compatible with most applications, due to iPhone-like screen

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!