X11 status Capture for an arbitary application

Jasper St. Pierre jstpierre at mecheye.net
Fri May 17 09:15:46 PDT 2013


The window-specific attributes? You can look at the X window properties,
using a tool like xprop, but that may not be what you want.

Events are delivered over a socket. It's up to the client to determine what
to do with the data retrieved from it. The client may leave unhandled
events as raw data waiting in the socket's buffer, or it may parse them and
put them on its own event queue. Knowing this requires knowing how the
internal application was developed, which you have no knowledge of without
the application's source code.

I'm not sure how knowing "menu lists" (which, as Alan said, has no native
support in the X protocol) would help you build a resource monitor. What's
the use case you have?


On Fri, May 17, 2013 at 11:53 AM, Dibyayan Chakraborty <
dib.coolguy at gmail.com> wrote:

> Ok. Thank you for the reply.
> Then is it possible to query the window specific attributes of an
> application from another program?
> And can you please elaborate this "debugger or remote introspection" ?
>
> On Fri, 2013-05-17 at 08:42 -0700, Alan Coopersmith wrote:
> > On 05/17/13 08:37 AM, Dibyayan Chakraborty wrote:
> > > Hi,
> > > I think i should be more clear on the specific terms that i previously
> used.
> > >   By "menu list" i meant to say the menus which are often present in
> the
> > > applications(e.g File, Edit, View, Insert) and by "event queue" i
> referred the
> > > event queue of the application where the key Events and Mouse Events
> are
> > > buffered prior to its processing.
> >
> > X11 has no concept of menus - those are implemented in toolkits
> (usually) or
> > applications (in some rare cases).   Similarly once the events are
> delivered
> > to the client, you'd need some form of debugger or remote introspection
> to
> > find out if the client has processed them or still has them in a queue to
> > handle later - there is no X11 API to query event queue state from
> another
> > program.
> >
>
>
> _______________________________________________
> xorg-devel at lists.x.org: X.Org development
> Archives: http://lists.x.org/archives/xorg-devel
> Info: http://lists.x.org/mailman/listinfo/xorg-devel
>



-- 
  Jasper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20130517/70772bd9/attachment.html>


More information about the xorg-devel mailing list