Henrik Sandklef writes:
> Sorry, more work for you :(
No problem at all
> Can you take the recorded file (xnee_debian_touchpad.xns) and replace
> (device number) 16 with 7. Typically;
>
> cat xnee_debian_touchpad.xns | sed 's/,16,/,7,/g' >
> xnee_debian_touchpad-mod.xns
Hmmm. That file has
Sorry, more work for you :(
Can you take the recorded file (xnee_debian_touchpad.xns) and replace
(device number) 16 with 7. Typically;
cat xnee_debian_touchpad.xns | sed 's/,16,/,7,/g' >
xnee_debian_touchpad-mod.xns
and replay the same way:
* Use the debian xnee
* Use the touchpad
* Repl
Great...I think, but I am confused (well, I guess I've always been).
Can you send over a log when running a replay session.
* Use the debian xnee
* Use the touchpad
* Replay (something) like this:
cnee --replay --file xnee_debian_touchpad.xns --verbose -e touchpadd.err
the important thind
OK. Thanks a lot.
I will try to resolve it. Probably boils down to me - think there's a bug when
replaying an enumerated device recorded with a different device number..
Cant remember how I decided to solve it. Woops :(
Dima Kogan wrote:
>Henrik Sandklef writes:
>
>> Can you run the same
Henrik Sandklef writes:
> Can you run the same command you had problem with:
>
> cnee --record --mouse -o /tmp/xnee.xns --first-last --smp
>
> and use a mouse instead of the Touchpad. This is really not likely the
> cause, but I would like to make sure.
That's it!
Currently my laptop is on a
Can you run the same command you had problem with:
cnee --record --mouse -o /tmp/xnee.xns --first-last --smp
and use a mouse instead of the Touchpad. This is really not likely the
cause, but I would like to make sure.
/h
On Thu, Nov 06, 2014 at 01:27:58PM -0800, Dima Kogan wrote:
> Henrik
Henrik Sandklef writes:
> How about your input devices, can you list them?
> You can use xinput (with no args).
Hi. I'm attaching a recorded file that has some mouse motion. I start in
one corner, then move to the middle and trace out a star. You can see
the path with this:
awk -F, '$2==6 {p
Thanks, that was quick. Hmmm, same X as here.
How about your input devices, can you list them?
You can use xinput (with no args).
Also I would like to check your recorded Xnee file,
Cut paste from this command: cnee --record --events-to-record 10 --mouse
--keyboard
Move your mouse a bi
I am currently not on my Debian laptop, but I can say that it works
fine on my Ubuntu 14.10.
Can you give me your xserver version?
... typically do: xdpyinfo | head -10
/h
My X server is:
version number:11.0
vendor string:The X.Org Foundation
vendor release number:1160
X.
Henrik Sandklef writes:
> I am currently not on my Debian laptop, but I can say that it works
> fine on my Ubuntu 14.10.
>
> Can you give me your xserver version?
> ... typically do: xdpyinfo | head -10
dima@shorty:~$ xdpyinfo| head -n 10
name of display::0.0
version number:11.0
vendo
I found a workaround: record normally, but replay with
--force-core-replay. I haven't looked deeply into why this works. The
recorded file has events from the 'Virtual core pointer' and from the
'Synaptics Touchpad'. Removing one or the other doesn't fix it, but
passing that option does.
--
To U
Hi. I have the same issue. Alex, do you have any more insight into
getting this working? I can see that the mouse motions are indeed
represented in a reasonable way in the file (I can plot the paths, and
they look right), but the playback just goes to the origin and stays
there, like you say
--
12 matches
Mail list logo
