David Reveman wrote:
getScreenData, getWindowData, getWindowList and such methods will return
a lot of data that is currently available as X properties on client
windows and the root window and part of the EWMH spec. I don't know to
what extents that data is available in existing scripting
On Wed, 2007-01-03 at 01:58 +, Mike Dransfield wrote:
Travis Watkins wrote:
On 1/2/07, David Reveman [EMAIL PROTECTED] wrote:
I've fixed the problem with an error being generated when setting an
option to the existing value. Dbus plugin is not sending any reply
messages so it's
Travis Watkins wrote:
On 1/2/07, David Reveman [EMAIL PROTECTED] wrote:
I've fixed the problem with an error being generated when setting an
option to the existing value. Dbus plugin is not sending any reply
messages so it's supposed to time out unless a error is generated.
You mean the
On Tue, 2007-01-02 at 19:12 -0600, Travis Watkins wrote:
On 1/2/07, David Reveman [EMAIL PROTECTED] wrote:
I've fixed the problem with an error being generated when setting an
option to the existing value. Dbus plugin is not sending any reply
messages so it's supposed to time out unless a
The bindings work in a dbus-send friendly manner
but for language bindings we need the more
complex datatypes.
Sorry, I forgot to mention that more importantly
the method signatures need to be consistent.
When it comes to introspection the signatures
are hard coded so they cannot vary.
