On 23/05/06, Tuomo Valkonen <[EMAIL PROTECTED]> wrote:
On 2006-05-23, Jarrod Lowe <[EMAIL PROTECTED]> wrote:
> However, when it is enabled (i.e dopath()'d), if I use keyboard resize
> mode, ion appears to lock up. I can't exit resize mode, resize, or do
> any other ion functions. killall -USR1 ion3 and killall -HUP ion3 have
> no effect. I was wondering if anyone here has any ideas of what I
> might be doing wrong?
You should _not_ use io.popen from Ion. It's probably not causing the
problem unless your program tries to access X and opaque_resize is off,
Well, the program itself is not accessing X, but it is opening a
socket to a program which is (reading idle from
XScreenSaverQueryInfo). And opaque_resize is off.
but popen is a costly and potentially blocking (NFS...) operation that
should not be used from the main thread/process of an interactive
application. ion-statusd is there for that.
I had some trouble getting it to work with statusd (completely not
knowing what I was doing didn't help) but I'll give it another go.
I can't decide if blocking when the NFS server goes down is a good
thing or not. Everyone here using KDE or Gnome, etc, have their
systems completly lock up, and so they can't do any work, and take a
long lunch. Hmmm.... :)
Does the setting opaque_resize have any effect?
It certainly does. Fixed it right up, thanks.
--
Tuomo
Again, thanks for your help. Ion is great!
--
Jarrod Lowe
