From: Tuomo Valkonen <[EMAIL PROTECTED]> Subject: Re: kpress_wait() not working? Date: Wed, 4 May 2005 17:08:21 +0000 (UTC)
> Yes, that's how it should work and works over here.
So there must be something wrong with my setup. I'm using the latest debian
packaged ion3 (20050502).
This is what I have in cfg_bindings.lua:
defbindings("WMPlex", {
bdoc("Close current object."),
kpress_wait(MOD1.."C", "WRegion.rqclose_propagate(_, _sub)"),
[...]
})
which is the default AFAIK.
Yet, the behaviour of MOD1.."C" is not the advertised. This is what I got
in .xsession-errors while pressing MOD1.."C" continuously on xev's frame:
/usr/bin/ion3: Client does not support the WM_DELETE protocol.
/usr/bin/ion3: Stack trace:
0 [C]: in 'rqclose_propagate'
1 [string "return function(_, _sub) WRegion.rqclose_pr..."]:1
[Skipping unnamed C functions.]
/usr/bin/ion3: Client does not support the WM_DELETE protocol.
/usr/bin/ion3: Stack trace:
0 [C]: in 'rqclose_propagate'
1 [string "return function(_, _sub) WRegion.rqclose_pr..."]:1
[Skipping unnamed C functions.]
/usr/bin/ion3: Client does not support the WM_DELETE protocol.
/usr/bin/ion3: Stack trace:
0 [C]: in 'rqclose_propagate'
1 [string "return function(_, _sub) WRegion.rqclose_pr..."]:1
[Skipping unnamed C functions.]
[... and so on, you get the picture]
If the behaviour was correct then only one of those events should be
reported, right?
Rui
pgpllqsNhKjq3.pgp
Description: PGP signature
