Comment 1 Valério Valério (reporter) 2009-06-12 01:05:36 UTC

Date: 2008-10-29 20:27
Sender: No Name

To try a quick hack at my proposed mouse mode I tried this:

--- orig.py     2008-10-29 20:06:13.636361238 +0100
+++ bluemaemo   2008-10-29 21:17:52.270361339 +0100
@@ -675,8 +675,9 @@
         self.mouse_down = False
         self.first_touch = True
         self.button_hold = False
+        self.dragging = False
         self.scroll_pos = 0
-        self.tape_mouse_area = 0
+        self.tape_mouse_area = 0.0
         self.main.bluemaemo_conf.fullscreen


@@ -728,6 +729,8 @@
     def on_mouse_down(self, emission, source):

                 self.mouse_down = True
+                tape_time = time.time() - self.tape_mouse_area
+                self.dragging = tape_time < 0.2
                 self.tape_mouse_area = time.time()


@@ -737,6 +740,7 @@

                 if source == "mouse_area":
                         tape_time = time.time() -
self.tape_mouse_area
+                        self.tape_mouse_area = time.time()

                         if tape_time < 0.2:

@@ -799,7 +803,7 @@
                                 x1,y1 =
mouse_position(self,x,y)


-                                if self.button_hold == True:
+                                if self.button_hold == True
or self.dragging:

                                         mov = "02:01:"
+ str(x1) + ":" + str(y1) + ":000"



-----

Unfortunately it does not work as expected.  I can tap-tap_and_hold
wait and lift_tap_and_hold quickly afterwards.  Then I get a
constant mouse button down effect.
The other way is to make a "quad click" but not release
the last one -- means: tap-tap-tap-tap_and_hold

Here, too I get a mouse drag effect.  Maybe you can find a problem
in my patch?

Comment 2 Valério Valério (reporter) 2009-06-20 17:53:21 UTC

(In reply to comment #0)
> Reported by: No Name (pydera) 
> 
> I tested bluemaemo on a Nokia N810.  It's very cool and I could think of an
> additional toggle button to switch between
> two modes:
> 
> A) - Mouse Mode
> Works as currently, but a tap followed by holding and moving could be
> interpreted as button down and hold.  So you could
> tap-move a window, or have more fun in paintbrush (just kidding ;)).

You can do that, holding the volume buttons, your suggestion might be confusing
for some users, because this is not the normal behavior of a regular touchpad.
> 
> B) - Digitizer Mode
> I don't know how good the N810's touchscreen resolution really is, so I have
> two ideas:
> 
> If resolution is nearly as high as its screen, so this could be an absolute
> position mode like a real digitizer, either
> mapped and scaled to whole target screen, or maybe movable but mapped
> pixelwise.
> 
> I don't know, whether the standard HID BT stack does even support this.  So if
> not (or if the touchscreen resolution
> is not high enough to map onto let's say 1024x...), then digitizer mode could
> work as follows:
> 
> N810's touchscreen is pressure sensitive.  So for pressure sensitive maemo
> devices BUTTON_DOWN could be triggered by
> an adjustable pressure threshold.  For certain application this could be a
> better choice compared to my suggested Mouse
> Mode.

The screen resolution of the tablets is 800x480.
Can you elaborate on this ? I don't see any big advantage here.

Thanks.

> 
> I really would like to use the N810 as an digitizer replacement I could always
> carry along. :-)
> 
> 
> 
> 
> OTHER COMMENTS:
> 
> User-Agent:       Mozilla/5.0 (X11; U; Linux i686; pt-PT; rv:1.9.0.5)
> Gecko/2008121621 Ubuntu/8.04 (hardy) Firefox/3.0.5
>