I have written a simple program which will report key press and release events for a particular window. In my case, it is mostly the terminal since I invoke the program from the terminal. I am able to get the key press and release events taking place in the terminal window (I have used XSelectInput() with KeyPressMask and KeyReleaseMask on the terminal) but the same is not working with ButtonPress and ButtonRelease. Not just these, but any events related to the mouse are not being reported. Any idea why this is happening?
hey,
Im new to the linux world. Lately, I have tried to create a glx window with xlib, making it a popup window(fullscreen) so I set override_redirect to true. Im happy with the removed borders, but apparantly, the application doesnt show up in the left bar in ubuntu, neither when I press alt... (4 Replies)
1. If there's some better place where xlib experts hang out, please tell me. Despite an assiduous search, I could not find an xlib reflector.
2. My actual question:
In an xterm, I want to grab and process all keyboard events in a program running inside the xterm. For example, with my program... (5 Replies)
Hi,
I am handling user issues in my team. Users have their Unix session running on Citrix MFU.
Recently, I was suppose to address a user issue which is as below:
Gets the below error when tries to open nedit:
Xlib: connection to ":165.0" refused by server
Xlib: Client is not... (1 Reply)
Hello!
Im running tight VNC on Red Hat Enterprise Linux 4.0.
How can I increase the number of X clients that I can run
in a VNC session?I need to run aproximately 500 programs in one VNC session,
but at this time I can only 236 -> i've tryed to launch 250 xclock's in background
and when it... (3 Replies)
Hi, I'm using rxvt in Cygwin and I'm wondering how to change my mouse bindings from the middle button for pasting to the right button. The main reason why I want to do this is because my laptop doesn't have a middle mouse button. Thanks for any help! (2 Replies)
Hello all,
I'm hoping to get a little insight from some of the wily veterans amongst you.
I've written a script to check for new outgoing files to our vendors located on our ssl server. It seems to be working ok, but the final question here, will be one of logic, and/or a better way to... (4 Replies)
grab(3) User Contributed Perl Documentation grab(3)NAME
grab - Confine pointer and keyboard events to a window sub-tree
SYNOPSIS
$widget->grab
$widget->grabOption
DESCRIPTION
This set of methods implement simple pointer and keyboard grabs for Tk. Tk's grabs are different than the grabs described in the Xlib
documentation. When a grab is set for a particular window, Tk restricts all pointer events to the grab window and its descendants in Tk's
window hierarchy. Whenever the pointer is within the grab window's subtree, the pointer will behave exactly the same as if there had been
no grab at all and all events will be reported in the normal fashion. When the pointer is outside $widget's tree, button presses and
releases and mouse motion events are reported to $widget, and window entry and window exit events are ignored. The grab subtree ``owns''
the pointer: windows outside the grab subtree will be visible on the screen but they will be insensitive until the grab is released. The
tree of windows underneath the grab window can include top-level windows, in which case all of those top-level windows and their
descendants will continue to receive mouse events during the grab.
Two forms of grabs are possible: local and global. A local grab affects only the grabbing application: events will be reported to other
applications as if the grab had never occurred. Grabs are local by default. A global grab locks out all applications on the screen, so
that only the given subtree of the grabbing application will be sensitive to pointer events (mouse button presses, mouse button releases,
pointer motions, window entries, and window exits). During global grabs the window manager will not receive pointer events either.
During local grabs, keyboard events (key presses and key releases) are delivered as usual: the window manager controls which application
receives keyboard events, and if they are sent to any window in the grabbing application then they are redirected to the focus window.
During a global grab Tk grabs the keyboard so that all keyboard events are always sent to the grabbing application. The focus method is
still used to determine which window in the application receives the keyboard events. The keyboard grab is released when the grab is
released.
Grabs apply to particular displays. If an application has windows on multiple displays then it can establish a separate grab on each
display. The grab on a particular display affects only the windows on that display. It is possible for different applications on a single
display to have simultaneous local grabs, but only one application can have a global grab on a given display at once.
The grab methods take any of the following forms:
$widget->grabCurrent
Returns the current grab window in this application for $widget's display, or an empty string if there is no such window.
$widget->grabs
Returns a list whose elements are all of the windows grabbed by this application for all displays, or an empty string if the
application has no grabs.
Not implemented yet!
$widget->grabRelease
Releases the grab on $widget if there is one, otherwise does nothing. Returns an empty string.
$widget->grab
Sets a local grab on $widget. If a grab was already in effect for this application on $widget's display then it is automatically
released. If there is already a local grab on $widget, then the command does nothing. Returns an empty string.
$widget->grabGlobal
Sets a global grab on $widget. If a grab was already in effect for this application on $widget's display then it is automatically
released. If there is already a global grab on $widget, then the command does nothing. Returns an empty string.
$widget->grabStatus
Returns none if no grab is currently set on $widget, local if a local grab is set on $widget, and global if a global grab is set.
BUGS
It took an incredibly complex and gross implementation to produce the simple grab effect described above. Given the current
implementation, it isn't safe for applications to use the Xlib grab facilities at all except through the Tk grab procedures. If
applications try to manipulate X's grab mechanisms directly, things will probably break.
If a single process is managing several different Tk applications, only one of those applications can have a local grab for a given display
at any given time. If the applications are in different processes, this restriction doesn't exist.
KEYWORDS
grab, keyboard events, pointer events, window
perl v5.12.1 2007-05-05 grab(3)