On Mon, 2002-07-22 at 19:50, Philip Blundell wrote:
> Ah, I suppose you're launching it from gpe-appmgr? I use monolaunch -k,
Of course :P
> which does indeed close the xkbd when you click on the icon a second
> time. I'm kind of inclined to say that if you want to launch it from
> the appmgr, you just ought to use a theme that provides a close icon on
> toolbar windows. However, this does pose a bit of a trap for the
> unwary.
Definately! (Though I would hardly call myself unwary ;-)
> There's actually another problem with launching gpe-kbd from the appmgr,
> which is that it won't come up at all if you have gpe-login running in
> autolock mode. What seems to happen is that appmgr's single-instance
> code notices gpe-login's child xkbd process and tries to raise that
> window, which has no effect because its parent isn't mapped at the time.
> I'm not sure exactly what to do about this either.
Remove gpe-kbd from the appmgr, leave in gpe-kbd-setup. Setup can have
show/hide kbd buttons which do "The Right Thing". This also avoids
having two icons for a keyboard. Hell, we could even fold gpe-kbd into a
generic gpe-setup tool, and use only the dock for launching xkbd.
> p.
mibus
-- Robert Mibus <mibus@bigpond.com> Windows 2000 solution for Y2K: While(system.year < 2000) system.year=system.year + 100;Received on Mon Jul 22 10:25:05 2002
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:41:28 EDT