N810 Multitouch F-F-F-Fun

I'm back from vacation, summer went fast as always! Tried to stay away from computers, spending the time with family & friends and enjoying the weather while it lasts... But I did have little coding fun also, testing how well "multitouch" would work in N810 ;-)

Here comes video:



Update: Like all respected magicians, I'll show how this trick works for the ones who didn't already know the behavior of (resistive, single-touch) touchscreens under multiple touches. As thp first commented, it is "using the 'merged' blob position that you get with the single touch screen and interpreting it as the middle of two or more equal-pressure points".

Now here is a video showing the same demo in PC, with "cheat mode" turned on:


So it's mostly useless... but somewhat f-f-f-fun :)

Comments

thp said…
I suppose this is just using the "merged" blob position that you get with the single touch screen and interpreting it as the middle of two or more equal-pressure points, or is there more to this?
July 27, 2009 at 4:00 PM
Kaitsu @ QUIt Coding said…
thp: Yes, only tricky part is building "touch grid" so that it actually feels like working all the time, here with 3 touch points. Usable enough for some specific games etc. but waiting for real multitouch devices(s) and support in Qt!

http://labs.trolltech.com/blogs/2009/04/20/multi-touch-support-in-qt/
July 27, 2009 at 5:44 PM
Martin Grimme said…
Multitouch "simulation" on a resistive touch screen is not very precise as the amount of pressure on each pressure point has an impact on the reported position.

But watching your video gives me the idea that this technique would still be useful for bringing joypad controls on screen. Great work!
July 27, 2009 at 7:21 PM
turn.self.off said…
hmm, joypad controls.

if that really worked, those emulators would be a whole lot more interesting.
July 27, 2009 at 10:48 PM
Anonymous said…
that looks really good.
there has already been multitouch available on n810 for a long time.
http://www.youtube.com/watch?v=dJWvvn_cePM
July 27, 2009 at 11:35 PM
Kaitsu @ QUIt Coding said…
These joypad discussions remind me about "analogpad" http://kgronholm.blogspot.com/2008/12/happy-new-year.html

Not sure how usable that would be with real (action) games, but should be doable anyways =)
July 27, 2009 at 11:47 PM
Kaitsu @ QUIt Coding said…
Anonymous: Ah I have missed that, thanks for the link! Damn liquid/lcuk, he makes us average hackers look so... average ;-)
July 27, 2009 at 11:57 PM
lcuk said…
Kaitsu, you are anything but average, i like seeing the stuff you are playing with in qt :)

I'm guessing for now if you press in the centre of all the dots they light up

your analogpad is already multitouch friendly isnt it? i mean, it can do diagonal presses like a real gamepad and pressing left+right together would cancel themselves out.

btw anonymous, that video does not do justice with what i want multitouch for ;)

happy hacking!

gary
July 28, 2009 at 12:56 AM
Anonymous said…
This looks pretty neat, but I imagine (as lcuk pointed out) that this demo worked as well as it did due to the geometry of the touch-points? Even so, pretty cool.
@liquid/lcuk "that video does not do justice with what i want multitouch for ;)":
Are you teasing us, or did you mention something about that elsewhere already? Your liqbase demos are enough to make me drool, but concrete information is lacking...
July 28, 2009 at 7:37 AM
Kaitsu @ QUIt Coding said…
liquid & ffejery: Thanks! Yes, that's the way demo works, updated post now to show video with "cheat mode" on. So liquid, what's the status with liqbase, haven't seen you blogging about it lately...? =)
July 28, 2009 at 9:28 AM
Tim Samoff said…
Far from average (as Gary says)... This is so cool to see. The possibilities are endless -- even with the input being less than accurate. Exciting! :)
July 28, 2009 at 2:47 PM
lcuk said…
Heh,
I've been busy with a few little things.
you just haven't been looking in the right places :P


couple of snapshots, not ready just yet and there is much more besides.

quite happy with my coding, making use of things I have developed.

http://liqbase.net/liqbase_net_preview.png
http://liqbase.net/liq.20090728_013953.liqbase_net.scr.png

the graffiti wall is now completely merged and has the ability to view sketches/photos/calendar entries (and other things) in the nice wall.

the database I created (over 100mb on device) contains every single sketch/photo/screenshot ever taken and includes full tagging and grouping capabilities. its being hammered into proper shape atm and proper sync is coming (its one way at the moment)

all in all its goin well :)
July 28, 2009 at 7:12 PM
Kaitsu @ QUIt Coding said…
Tim Samoff: Thanks! I'll wait for real multitouch support into Qt and suitable device(s), then provide r-e-a-l-l-y cool UI's utilizing them. Promise ;-)

liquid: Sounds (and looks) nice! Didn't know you have browser backend in there also, cool! =)
July 28, 2009 at 8:48 PM
Post a Comment

Popular posts from this blog

Qt 5.10 QML Shape testing

Image
When implementing component into QtQuick UI which needs something more than rectangles, images and texts, pure declarative QML hasn't been enough. Popular choices to use for items with some sort of vector drawing are QML Canvas , QQuickPaintedItem  or QNanoPainter . But with Qt 5.10 there will be supports for new Shape  element with paths that contain lines, quads, arcs etc. so I decided to install Qt 5.10 beta3 and implement all tests of "qnanopainter_vs_qpainter_demo" with also QML + Shape elements. ( This kinda makes it "qnanopainter_vs_qpainter_vs_qmlshape_demo" but not renaming now ). So here is in all glory the same UI implemented with QNanoPainter (left), QQuickPaintedItem (center), and QML+Shape (right): Hard to spot the differences right? If only there would be a way to prove this, some way to x-ray into these UIs... like QSG_VISUALIZE=overdraw  to visualize what Qt Quick Scene Graph Renderer sees? Here you can see that scene graph sees QNan
Read more

Introducing QNanoPainter

Qt World Summit is just about to start! I’m not participating this time, but wanted to contribute one-more-thing to discuss in UI groups at the heart of Berlin ;) During the past about six months we at QUIt Coding have had a side-side-project called QNanoPainter. This library is designed for implementing custom QQuickItems into Qt5 scene graph. Currently if you want to implement custom Qt Quick item, options are at least: QQuickItem : Offers best performance due to Qt5 scene graph integration. But QSG* classes are relatively low-level with vertices, indices & materials. Painting more complicated things requires quite an expert and even then productivity is not very high. QQuickFramebufferObject : This is a good option if you want to draw with OpenGL into QQuickItem. But as we all know, OpenGL is also quite low-level API so no productivity wins here. QQuickPaintedItem : This means painting with good old QPainter C++ API. Weakness of QPainter with modern graphics accelerated
Read more

Qt 5.10 Rendering Benchmarks

Image
Qt 5.10.0 RC packages are available now and actual release is happening pretty soon. So this seems to be a good time to run some rendering benchmarks with 5.10, including new QML Shape element, QQuickPaintedItem and QNanoPainter . After my previous blog post , some initial comments mentioned how QML Shape didn't reach their performance expectations. But I think that might be more of a "use the right tool for the job" -kind of thing. This demo application is very much designed to test the limits of how much heavily animated graphics can be drawn while keeping performance high and while having its own strengths, QML Shape likely isn't the tool for that. To prove this point, there is a new ' flower ' test case in QNanoPainter demo app which renders a nice flower path, animating gradient color & rotation (but not path). Combining it with new setting to render multiple items (not just multiple renders per item) and the outcome looks like this with 1 and 1
Read more