Attaching two versions, one with instant gesture and one with click and
hold. These are both done with the touch screen and button 1, since
those are the gestures I'm most worried about getting working. (Single
finger swipe to scroll / flip pages, that kind of thing.)
They're both showing motion
** Attachment added: easystroke_v_click_and_hold_record_action_x220.txt
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/788980/+attachment/2155176/+files/easystroke_v_click_and_hold_record_action_x220.txt
--
You received this bug notification because you are a member of
Pretty much the same behavior with the touchpad. Instant stroke is
identical. Click and hold lets me complete the gesture recording this
time, but then warns me that I bound the gesture to just a single button
click, and asks if I'm sure. It doesn't seem to have the problem
terminating the
** Attachment added:
easystroke_v_click_and_hold_touchpad_record_action_x220.txt
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/788980/+attachment/2155182/+files/easystroke_v_click_and_hold_touchpad_record_action_x220.txt
--
You received this bug notification because you
I should add that by default the touchscreen and stylus weren't being
recognized by the wacom driver and thus weren't behaving properly. I had
to upgrade to the newest version of xserver-xorg-input-wacom (not in the
standard repositories) and fiddle with xorg.conf.d/50-wacom.conf to get
it to pick
Thanks for the info. So instant gestures and click and hold both
deal only with the button, and actual gestures need to use timeout.
That does seem to work correctly with my touchscreen.
I should have been more observant. When you mentioned documenting
above I started looking around, because
** Changed in: easystroke (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788980
Title:
Easystroke doesn't detect movement from any device
--
ubuntu-bugs
I think if you added up all the man-hours wasted by people trying to
figure out why the timeout parameter had no effect you'd have enough to
just develop a new distro from scratch. And that's not even counting the
additional hours spent by those who got as far as this bug, found the
answer, and
I'm not asking for an option to change the daemon, I'm asking for an
option to change the behavior of the existing daemon. Changing the
daemon has more side effects than just fixing this one issue - it
changes the look of the bubbles. If the goal is to get everyone using
this new daemon, forcing
I can confirm I'm still seeing this on a fresh install of Natty. I've
got the ThinkPad x220 and the additional slice battery. At the moment
the primary battery is fully charged and the secondary is discharging.
cat /proc/acpi/battery/BAT0/state:
present: yes
capacity state:
Public bug reported:
Binary package hint: easystroke
Running a fresh install of Natty on a ThinkPad X220 tablet. I've tried
creating gestures with the touchpad, trackpoint, touch screen and pen.
All are valid, active input devices that work fine for standard mouse
control and show up as active
Ok, I've read through this whole thread and I've got to side with the
pro-custom-timeout people. This is friggin ridiculous. Here's another
use case at the opposite end of the spectrum from most of the above:
I have a perfectly good script built around notify-send I was using on
Gentoo. It worked
Surprisingly there's no way to go back and edit these comments after
posting (that I can find, anyway) and my questions won't help me much if
they're hidden behind a click-through, so here they are again:
Does anyone know if:
- there's something I can manually edit to remove this dependency so I
13 matches
Mail list logo
