Active Topics
-
Nokia FW servers dead (127)
to MeeGo / Harmattan by tvandorffy - 57 mins ago -
How to force MMS to use cellular network for data? (2)
to SailfishOS by taixzo - 14 hrs, 4 mins ago -
Crash/poweroff after entering SIM PIN (6)
to Nokia N9 / N950 by nonsuch - 1 day, 23 hrs ago -
Phone Camera Competition May 2021: "spring is here" (3)
to General by robthebold - 2 days, 8 hrs ago -
Not clickbait "NOKIA STILL MAKING PHONES, BUT FOR INDUSTRIAL USES" (3)
to Competitors by biketool - 3 days, 13 hrs ago -
Phone Camera Competition April 2021: "Funny & Foolish" (38)
to General by peterleinchen - 3 days, 23 hrs ago -
A Palm OS thread ... and a thank you to the community (24)
to Alternatives by meemorph - 4 days, 18 hrs ago -
MeeGo v1.2.0.1x for Netbook (0)
to MeeGo / Harmattan by teroyk - 4 days, 18 hrs ago - more...
 |
|
2010-07-12
, 14:29
|
|
Posts: 4,384 |
Thanked: 5,524 times |
Joined on Jul 2007
@ ˙ǝɹǝɥʍou
|
#12
|
Ok, combining what ossi and paul said; I guess if we can elegantly convey to the user that they shouldn't move point A, we can have a pretty neat 'multitouch'-looking solution that works for variable zooming and rotation.
edit: Hmmm... but there's really no point in doing this. All you're getting is the gimmicky 'gestures' without any added input variable unlike true multitouch. You can just make an interface that does 'Tap A then manipulate point B' without neededing the 2 points anyway.
Another advantage of 'true' multitouch is that it can be (visually) UI-less and that it can be applied anywhere on screen. I can't think of how this pseudo-multitouch can be implemented while retaining those two elements.
Last edited by ysss; 2010-07-12 at 14:41.
edit: Hmmm... but there's really no point in doing this. All you're getting is the gimmicky 'gestures' without any added input variable unlike true multitouch. You can just make an interface that does 'Tap A then manipulate point B' without neededing the 2 points anyway.
Another advantage of 'true' multitouch is that it can be (visually) UI-less and that it can be applied anywhere on screen. I can't think of how this pseudo-multitouch can be implemented while retaining those two elements.
__________________
Class .. : Power User
Humor .. : [#####-----] | Alignment: Pragmatist
Patience : [###-------] | Weapon(s): Galaxy Note + BB Bold Touch 9900
Agro ... : [###-------] | Relic(s) : iPhone 4S, Atrix, Milestone, N900, N800, N95, HTC G1, Treos, Zauri, BB 9000, BB 9700, etc
Class .. : Power User
Humor .. : [#####-----] | Alignment: Pragmatist
Patience : [###-------] | Weapon(s): Galaxy Note + BB Bold Touch 9900
Agro ... : [###-------] | Relic(s) : iPhone 4S, Atrix, Milestone, N900, N800, N95, HTC G1, Treos, Zauri, BB 9000, BB 9700, etc
Follow the MeeGo Coding Competition!
Last edited by ysss; 2010-07-12 at 14:41.
 |
|
2010-07-12
, 14:58
|
|
Posts: 663 |
Thanked: 282 times |
Joined on Nov 2009
@ London, UK
|
#13
|
Agreed with ysss - what is the objective of this?
Multitouch is never going to work well on the N900. Trying to emulate (for example) the iPhone's operation could in theory be done in a limited way - but what would be better is to make more efficient and clever use of the hardware as it stands rather than trying to copy the function of a different technology.
Multitouch is never going to work well on the N900. Trying to emulate (for example) the iPhone's operation could in theory be done in a limited way - but what would be better is to make more efficient and clever use of the hardware as it stands rather than trying to copy the function of a different technology.
__________________
Nokia are a business and have chosen a path of using the OSS community phenomenon to reduce their overheads specifically after sales support and development. Unlike Apple who do the opposite and make a killing from their Applications store.
Nokia are a business and have chosen a path of using the OSS community phenomenon to reduce their overheads specifically after sales support and development. Unlike Apple who do the opposite and make a killing from their Applications store.
|
|
2010-07-12
, 16:04
|
|
Posts: 312 |
Thanked: 51 times |
Joined on Mar 2010
@ dubai
|
#14
|
Originally Posted by Wichall
i found the app of a site.
Yes I remember seeing this too, someone wrote some sort of software/driver that could detect (on normal resistive screens) when there where 2 fingers on the screen, and instead of interpret it as the middle point, guess where the two fingers were and interpret it as 2 presses.
Unless some community devs are looking to get deeply involved in (I'm assuming) lots of reverse engineering, we're not going to see this on the N900, definitely not from Nokia.
its a .sis file that when u install it a flash file will appear on your memory card!
enjoy!
wait and its called spacedancer
http://www.2shared.com/file/u_PSl_8Y/spacedancer.html
|
|
2010-07-12
, 18:30
|
|
Posts: 219 |
Thanked: 21 times |
Joined on May 2010
|
#15
|
Originally Posted by cashclientel
the reason for this is because its much better to use multitouch than the spiral implementation on our webbrowsers and we can implement it on other stuff as well.
Agreed with ysss - what is the objective of this?
Multitouch is never going to work well on the N900. Trying to emulate (for example) the iPhone's operation could in theory be done in a limited way - but what would be better is to make more efficient and clever use of the hardware as it stands rather than trying to copy the function of a different technology.
and we ARE making clever use of the hardware as it is..multitouch would just be an added advantage. better to have it than not. if it really doesnt fly, relax, we can get back to our usual spiral single touch technology.
|
|
2010-07-12
, 19:36
|
|
Posts: 71 |
Thanked: 5 times |
Joined on May 2010
|
#16
|
I would love to see this :P
|
|
2010-07-12
, 19:38
|
|
Posts: 219 |
Thanked: 21 times |
Joined on May 2010
|
#17
|
me too..all we need is a little more enthusiasm.
and alot of smart developers :P
and alot of smart developers :P
|
|
2010-07-12
, 20:11
|
|
Posts: 4,384 |
Thanked: 5,524 times |
Joined on Jul 2007
@ ˙ǝɹǝɥʍou
|
#18
|
How do you propose the detail of the interaction?
Based on the limitations discussed above, there would be quite a few conventions that the user has to understand and follow...
1. You can't tap the screen together with both fingers. There has to be a clear leading finger (A), followed by the other point (C).
2. You can't move the leading finger while doing the gestures.
3. After the following the restrictions, you're only getting variable zoom.
4. Rotation is possible, as long as you move (C) a litlte before doing the rotating motion. Which in itself is a weird and bothersome rule. And after that it still wouldn't be intuitive because the axis of your rotation will always be (A), which is most likely the user's thumb and positioned off-center from the intended axis.
The scheme is too complex and convoluted, I'm not seeing anything worthwhile out of it.
Based on the limitations discussed above, there would be quite a few conventions that the user has to understand and follow...
1. You can't tap the screen together with both fingers. There has to be a clear leading finger (A), followed by the other point (C).
2. You can't move the leading finger while doing the gestures.
3. After the following the restrictions, you're only getting variable zoom.
4. Rotation is possible, as long as you move (C) a litlte before doing the rotating motion. Which in itself is a weird and bothersome rule. And after that it still wouldn't be intuitive because the axis of your rotation will always be (A), which is most likely the user's thumb and positioned off-center from the intended axis.
The scheme is too complex and convoluted, I'm not seeing anything worthwhile out of it.
__________________
Class .. : Power User
Humor .. : [#####-----] | Alignment: Pragmatist
Patience : [###-------] | Weapon(s): Galaxy Note + BB Bold Touch 9900
Agro ... : [###-------] | Relic(s) : iPhone 4S, Atrix, Milestone, N900, N800, N95, HTC G1, Treos, Zauri, BB 9000, BB 9700, etc
Class .. : Power User
Humor .. : [#####-----] | Alignment: Pragmatist
Patience : [###-------] | Weapon(s): Galaxy Note + BB Bold Touch 9900
Agro ... : [###-------] | Relic(s) : iPhone 4S, Atrix, Milestone, N900, N800, N95, HTC G1, Treos, Zauri, BB 9000, BB 9700, etc
Follow the MeeGo Coding Competition!
|
|
2010-07-12
, 20:18
|
|
Posts: 203 |
Thanked: 152 times |
Joined on May 2009
@ Austria
|
#19
|
I have seen this fake multitouch on n900 in a youtube video a few months ago but cant find it anymore. maybe i will write a reference implementation in qt and use it in my app.
 |
|
2010-07-12
, 20:25
|
|
Posts: 909 |
Thanked: 216 times |
Joined on Nov 2009
@ Bremen, Germany
|
#20
|
there are several videos of resistive multitouch-screens on youtube for example. it does exist, but obviously hasnt been used before in any mainstream-device.
i wonder why?!
i wonder why?!
i dont remember poking three fingers into my screen ever :P
jokes apart, very good observation. (AND IM VERY HAPPY THAT YOUVE UNDERSTOOD MY HORRIBLE EXPLANATION!!)
and my answer to that is, once a multitouch has been made,i.e as long as there is contact of the two fingers on the screen, you can disable the rest of the screen.btw, you can always make (A) a moving variable..i e the value of (A) could change..and you can make (B) a non changeable value. atleast we can start off with a small multitouch function. it would be quite a nice script.it COULD be slow, but atleast we have multitouch, and we can improve on it later.
if only i knew the developer language...(comeon, SOMEONE SAY.."OH WELL I DO
(i would LOVE to see tap tap revenge on my n900
Last edited by mangal_sk8erboy; 2010-07-12 at 14:21.