[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: which program can show X/Y position of mouse pointer



On Mon 09 May 2022 at 19:20:25 (-0400), lou wrote:
> 
> On 5/9/22 9:21 AM, Dan Ritter wrote:
> > No, I've never used twm. fvwm, sawmill/sawfish, and xfwm can all
> > do that. Probably most others.
> > 
> 
> Thanks! i have success with icewm, not with fvwm
> 
> xeyes knows mouse movement, it's too bad it doesn't show X/Y coordinates

It works just fine in fvwm. I ran this script in an xterm:

while /bin/true
do
    printf '%s ' "$(date +%H:%M:%S)" >> /tmp/mousey-pos
    xdotool getmouselocation >> /tmp/mousey-pos
    sleep 1
done

I ran this command in another xterm:

$ tail -f /tmp/mousey-pos

I then moved the mouse around the corners of the screen, and then
the corners of the xterm window on the screen. I shifted to another
viewport¹ and repeated (screen, then xterm). Then I switched back
to the original viewport to interrupt the script. The mousey-pos
output is attached.

The coordinates are always for the screen that you are staring at,
not the entire virtual desktop. When you move viewports, the window
numbers naturally all change (except for the clocks/pager/xconsole),
but the X/Y values don't.

There's no need to keep any xterm in view while it's running, if
you're recording the output in a file.

If it really doesn't work for you, there may be some dependency on
the way you start fvwm in .xsession which affects the parent-child
relationships, but that's just a guess.

I also tested using it from a bound keystroke, borrowing the
contortionist's keystroke for re-execing my xinput configuration,
Shift-Ctrl-Alt-/, thus:

#Key    slash           A       CMS     Exec exec xinput-xsession quiet
Key     slash           A       CMS     Exec exec xdotool getmouselocation

$ tail -f .xsession-fvwm-0-log

confirmed that this works too:

[fvwm][Echo]: Reading /home/david/.fvwm/main-menu-pre.hook Last edited 2003 July 21
[fvwm][Echo]: Reading /home/david/.fvwm/post.hook Last edited 2022-04-02
[fvwm][Echo]: Reading /home/david/.fvwm/last-post.hook-axis-0 Last edited 2020-04-04
[fvwm][Echo]: Reading /home/david/.fvwm/kbd-base.hook Last edited 2021-11-27
[fvwm][Echo]: Reading /home/david/.fvwm/kbd-axis.hook Last edited 2021-06-18
x:740 y:461 screen:0 window:16777248
x:118 y:83 screen:0 window:16777248
x:1385 y:739 screen:0 window:65011750

I must bind it to a better key. It's a much more controllable
output than xev, John, but I can see virtues in both.

¹ viewport: I have a desktop that's five times wider and four times
higher than the screen, and I switch between these twenty viewports
with clicks in the pager window, or with WindowsKey-arrows or with
Ctrl-Alt-arrows.

A few of the window numbers: root is 1707, …561 and …409 are
swissclocks for two timezones, …761 is the pager, …750 the xconsole,
and all of these are the same in every viewport. …248 is where I ran
the program, started and finished (obviously), and drew the (2nd)
outline round. …400 is an identical xterm on the viewport "next door"
for the 4th outline to go round.

Cheers,
David.
20:26:48 x:787 y:466 screen:0 window:16777248
20:26:49 x:772 y:456 screen:0 window:16777248
20:26:50 x:87 y:110 screen:0 window:16777248
20:26:51 x:13 y:42 screen:0 window:16777248
20:26:52 x:29 y:46 screen:0 window:16777248
20:26:53 x:689 y:78 screen:0 window:16777248
20:26:54 x:1239 y:44 screen:0 window:1707
20:26:55 x:1563 y:28 screen:0 window:62914561
20:26:56 x:1573 y:33 screen:0 window:62914561
20:26:57 x:1569 y:114 screen:0 window:60817409
20:26:58 x:1581 y:478 screen:0 window:1707
20:26:59 x:1573 y:759 screen:0 window:10485761
20:27:00 x:1551 y:820 screen:0 window:10485761
20:27:01 x:1548 y:819 screen:0 window:10485761
20:27:02 x:1249 y:825 screen:0 window:65011750
20:27:03 x:463 y:853 screen:0 window:1707
20:27:04 x:93 y:881 screen:0 window:1707
20:27:05 x:42 y:872 screen:0 window:1707
20:27:06 x:49 y:786 screen:0 window:16777248
20:27:07 x:31 y:208 screen:0 window:16777248
20:27:08 x:26 y:38 screen:0 window:16777248
20:27:09 x:383 y:52 screen:0 window:16777248
20:27:10 x:1023 y:20 screen:0 window:16777248
20:27:11 x:1075 y:34 screen:0 window:16777248
20:27:12 x:1165 y:748 screen:0 window:65011750
20:27:13 x:1093 y:775 screen:0 window:16777248
20:27:14 x:720 y:779 screen:0 window:16777248
20:27:15 x:58 y:740 screen:0 window:16777248
20:27:16 x:37 y:750 screen:0 window:16777248
20:27:17 x:62 y:751 screen:0 window:16777248
20:27:18 x:62 y:751 screen:0 window:18874400
20:27:19 x:62 y:751 screen:0 window:18874400
20:27:20 x:54 y:741 screen:0 window:18874400
20:27:21 x:28 y:430 screen:0 window:18874400
20:27:22 x:38 y:84 screen:0 window:18874400
20:27:23 x:38 y:85 screen:0 window:18874400
20:27:24 x:488 y:53 screen:0 window:18874400
20:27:25 x:1336 y:38 screen:0 window:1707
20:27:26 x:1563 y:33 screen:0 window:62914561
20:27:27 x:1568 y:208 screen:0 window:1707
20:27:28 x:1566 y:727 screen:0 window:65011750
20:27:29 x:1556 y:825 screen:0 window:10485761
20:27:30 x:1288 y:834 screen:0 window:65011750
20:27:31 x:667 y:829 screen:0 window:1707
20:27:32 x:120 y:843 screen:0 window:1707
20:27:34 x:48 y:821 screen:0 window:1707
20:27:35 x:42 y:296 screen:0 window:18874400
20:27:36 x:25 y:50 screen:0 window:18874400
20:27:37 x:36 y:50 screen:0 window:18874400
20:27:38 x:666 y:29 screen:0 window:18874400
20:27:39 x:1075 y:29 screen:0 window:18874400
20:27:40 x:1087 y:62 screen:0 window:18874400
20:27:41 x:1096 y:502 screen:0 window:18874400
20:27:42 x:1077 y:751 screen:0 window:18874400
20:27:43 x:1009 y:764 screen:0 window:18874400
20:27:44 x:484 y:738 screen:0 window:18874400
20:27:45 x:162 y:751 screen:0 window:18874400
20:27:46 x:53 y:757 screen:0 window:18874400
20:27:47 x:421 y:600 screen:0 window:18874400
20:27:48 x:811 y:420 screen:0 window:18874400
20:27:49 x:811 y:420 screen:0 window:18874400
20:27:50 x:811 y:420 screen:0 window:16777248

Reply to: